Linux-ide Archive mirror
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Szuying Chen <chensiying21@gmail.com>
Cc: "kernel@wantstofly.org" <kernel@wantstofly.org>,
	"dlemoal@kernel.org" <dlemoal@kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"Jesse1_Chang@asmedia.com.tw" <Jesse1_Chang@asmedia.com.tw>,
	"Richard_Hsu@asmedia.com.tw" <Richard_Hsu@asmedia.com.tw>,
	"Chloe_Chen@asmedia.com.tw" <Chloe_Chen@asmedia.com.tw>
Subject: Re: ASMedia ASM1062 (AHCI) hang after "ahci 0000:28:00.0:Using 64-bit DMA addresses"
Date: Wed, 31 Jan 2024 11:06:42 +0000	[thread overview]
Message-ID: <ZbopwKZJAKQRA4Xv@x1-carbon> (raw)
In-Reply-To: <20240130055757.2573-1-Chloe_Chen@asmedia.com.tw>

On Tue, Jan 30, 2024 at 01:57:57PM +0800, Szuying Chen wrote:
> Signed-off-by: Szuying Chen <Chloe_Chen@asmedia.com.tw>
> ---
> 	
> On 1/29/24 17:53, Niklas Cassel wrote:
> > Hello Szuying,
> > 
> > Please have a look at:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata?id=20730e9b277873deeb6637339edcba64468f3da3
> > 
> > This commit is already in Linus's tree and will thus be included in the
> > upcoming v6.8 release.
> > 
> > 
> > However, this quirk is currently only applied for:
> > PCI device id: 0x0611 and 0x0612
> > see:
> > 
> > $ git grep ASMEDIA origin/master drivers/ata
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0601), board_ahci },   /* ASM1060 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0602), board_ahci },   /* ASM1060 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0611), board_ahci_43bit_dma }, /* ASM1061 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0612), board_ahci_43bit_dma }, /* ASM1061/1062 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0621), board_ahci },   /* ASM1061R */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0622), board_ahci },   /* ASM1062R */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x0624), board_ahci },   /* ASM1062+JMB575 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x1062), board_ahci },   /* ASM1062A */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x1064), board_ahci },   /* ASM1064 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x1164), board_ahci },   /* ASM1164 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x1165), board_ahci },   /* ASM1165 */
> > origin/master:drivers/ata/ahci.c:       { PCI_VDEVICE(ASMEDIA, 0x1166), board_ahci },   /* ASM1166 */
> > 
> > 
> > Could you please supply a complete list of buggy ASMedia SATA controllers?
> > (I.e. all ASMedia SATA controllers that only support 43-bit DMA addresses,
> > yet claiming to have support for 64-bit addressing.)
> > 
> Hello Niklas,
>         
> ASMedia SATA controllers that only support 43-bit DMA addresses are listed 
> below:
> PCI device id: 
>         0x0601  /* ASM1060 */
>         0x0602  /* ASM1060 */
>         0x0611  /* ASM1061 */
>         0x0612  /* ASM1061/1062 */
>         0x0621  /* ASM1061R */
>         0x0622  /* ASM1062R */
>         0x0624  /* ASM1062+JMB575 */
>         
> Thanks,
> Szuying

Hello Szuying,

Thank you for getting back so quickly!


Kind regards,
Niklas

       reply	other threads:[~2024-01-31 11:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240130055757.2573-1-Chloe_Chen@asmedia.com.tw>
2024-01-31 11:06 ` Niklas Cassel [this message]
2024-01-16 12:27 ASMedia ASM1062 (AHCI) hang after "ahci 0000:28:00.0: Using 64-bit DMA addresses" Lennert Buytenhek
2024-01-16 14:20 ` Niklas Cassel
2024-01-17 21:14   ` Lennert Buytenhek
2024-01-17 22:52     ` Niklas Cassel
2024-01-23 21:00       ` Lennert Buytenhek
2024-01-24 10:15         ` Niklas Cassel
2024-01-24 10:41           ` Niklas Cassel
2024-01-24 12:40           ` Lennert Buytenhek
2024-01-24 13:58             ` Lennert Buytenhek
2024-01-24 16:14               ` Robin Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZbopwKZJAKQRA4Xv@x1-carbon \
    --to=niklas.cassel@wdc.com \
    --cc=Chloe_Chen@asmedia.com.tw \
    --cc=Jesse1_Chang@asmedia.com.tw \
    --cc=Richard_Hsu@asmedia.com.tw \
    --cc=chensiying21@gmail.com \
    --cc=dlemoal@kernel.org \
    --cc=kernel@wantstofly.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).