From: Hans de Goede <hdegoede@redhat.com>
To: Roger Quadros <rogerq@ti.com>, axboe@kernel.dk
Cc: vigneshr@ti.com, nsekhar@ti.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ata: ahci_platform: add 32-bit quirk for dwc-ahci
Date: Thu, 6 Feb 2020 12:50:06 +0100 [thread overview]
Message-ID: <d3a80407-a40a-c9e4-830f-138cfe9b163c@redhat.com> (raw)
In-Reply-To: <20200206111728.6703-1-rogerq@ti.com>
Hi,
On 2/6/20 12:17 PM, Roger Quadros wrote:
> On TI Platforms using LPAE, SATA breaks with 64-bit DMA.
> Restrict it to 32-bit.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> drivers/ata/ahci_platform.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
> index 3aab2e3d57f3..b925dc54cfa5 100644
> --- a/drivers/ata/ahci_platform.c
> +++ b/drivers/ata/ahci_platform.c
> @@ -62,6 +62,9 @@ static int ahci_probe(struct platform_device *pdev)
> if (of_device_is_compatible(dev->of_node, "hisilicon,hisi-ahci"))
> hpriv->flags |= AHCI_HFLAG_NO_FBS | AHCI_HFLAG_NO_NCQ;
>
> + if (of_device_is_compatible(dev->of_node, "snps,dwc-ahci"))
> + hpriv->flags |= AHCI_HFLAG_32BIT_ONLY;
> +
The "snps,dwc-ahci" is a generic (non TI specific) compatible which
is e.g. also used on some exynos devices. So using that to key the
setting of the 32 bit flag seems wrong to me.
IMHO it would be better to introduce a TI specific compatible
and use that to match on instead (and also adjust the dts files
accordingly).
Regards,
Hans
> port = acpi_device_get_match_data(dev);
> if (!port)
> port = &ahci_port_info;
>
next prev parent reply other threads:[~2020-02-06 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 11:17 [PATCH] ata: ahci_platform: add 32-bit quirk for dwc-ahci Roger Quadros
2020-02-06 11:50 ` Hans de Goede [this message]
2020-02-06 11:54 ` Roger Quadros
2020-02-12 11:01 ` Roger Quadros
2020-02-12 11:32 ` Hans de Goede
2020-02-12 11:43 ` Robin Murphy
2020-02-12 11:56 ` David Laight
2020-02-12 12:09 ` Robin Murphy
2020-02-13 7:24 ` Roger Quadros
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=d3a80407-a40a-c9e4-830f-138cfe9b163c@redhat.com \
--to=hdegoede@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.com \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.com \
/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 NNTP newsgroup(s).