From: Niklas Cassel <cassel@kernel.org>
To: Roland Waltersson <roland.waltersson@netinsight.net>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY
Date: Mon, 7 Sep 2026 10:00:20 +0200 [thread overview]
Message-ID: <ap5vFBMRkoe0NF73@ryzen> (raw)
In-Reply-To: <20260904134310.1465051-2-cassel@kernel.org>
On Fri, Sep 04, 2026 at 03:43:11PM +0200, Niklas Cassel wrote:
> A user reported that commit 105c42566a55 ("ata: ahci: force 32-bit DMA for
> JMicron JMB582/JMB585") made the JMicron JMB585 unusable on his board.
>
> The failure is seen as soon as the ahci driver is probed, and booting with
> iommu=off does not solve the problem.
>
> Looking at the AHCI specification, PxCLBU and PxFBU are both read only '0'
> for HBAs that do not support 64-bit addressing.
>
> For HBAs that do support 64-bit addressing, the registers are read write,
> with a reset value that is Implementation Specific.
>
> When using the AHCI_HFLAG_32BIT_ONLY flag, the HBA does support 64-bit
> addressing, and a 32-bit DMA mask is set by simply clearing HOST_CAP_64.
> Thus, in this case, we need to explicitly clear the registers to 0.
>
> Fixes: 105c42566a55 ("ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585")
> Fixes: c7a42156d99b ("ahci: disable 64bit dma on sb600")
> Cc: stable@vger.kernel.org
> Reported-by: Roland Waltersson <roland.waltersson@netinsight.net>
> Closes: https://lore.kernel.org/linux-ide/IA0PR17MB668730A4ECCD65F7A1DC3EDC9EB62@IA0PR17MB6687.namprd17.prod.outlook.com/
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
Hello Roland,
Any chance to get a Tested-by from you?
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-07 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:43 [PATCH v2] ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY Niklas Cassel
2026-09-05 0:43 ` Damien Le Moal
2026-09-07 8:00 ` Niklas Cassel [this message]
2026-09-09 10:58 ` Niklas Cassel
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=ap5vFBMRkoe0NF73@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=roland.waltersson@netinsight.net \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.