From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
kernel-team@android.com, willmcvicker@google.com,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: exynos: gs101: ufs: add dma-coherent property
Date: Mon, 30 Jun 2025 08:01:04 +0200 [thread overview]
Message-ID: <c6c90a4b-b8d2-45d1-928a-464281ce7b37@kernel.org> (raw)
In-Reply-To: <CADrjBPqdr1NEd+W4ATJ-6Xi36y8Gi_=81LsFNtY_s2-pBPagFA@mail.gmail.com>
On 27/06/2025 18:28, Peter Griffin wrote:
> Hi Krzysztof,
>
> On Fri, 14 Mar 2025 at 15:38, Peter Griffin <peter.griffin@linaro.org> wrote:
>>
>> ufs-exynos driver configures the sysreg shareability as
>> cacheable for gs101 so we need to set the dma-coherent
>> property so the descriptors are also allocated cacheable.
>>
>> This fixes the UFS stability issues we have seen with
>> the upstream UFS driver on gs101.
>>
>> Fixes: 4c65d7054b4c ("arm64: dts: exynos: gs101: Add ufs and ufs-phy dt nodes")
>> Cc: stable@vger.kernel.org
>> Suggested-by: Will McVicker <willmcvicker@google.com>
>> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
>> ---
>
> Friendly ping about this patch :)
Thanks, I dropped it from my queue based on comments on the bindings
patch, but that was too hasty.
I applied it now.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-30 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 15:38 [PATCH 0/2] Add dma-coherent for gs101 UFS dt node Peter Griffin
2025-03-14 15:38 ` [PATCH 1/2] arm64: dts: exynos: gs101: ufs: add dma-coherent property Peter Griffin
2025-03-14 15:56 ` André Draszik
2025-03-14 17:14 ` William McVicker
2025-06-27 16:28 ` Peter Griffin
2025-06-30 6:01 ` Krzysztof Kozlowski [this message]
2025-06-30 6:56 ` (subset) " Krzysztof Kozlowski
2025-03-14 15:38 ` [PATCH 2/2] scsi: ufs: dt-bindings: exynos: add dma-coherent property for gs101 Peter Griffin
2025-03-14 15:59 ` André Draszik
2025-03-17 14:55 ` Peter Griffin
2025-03-17 10:51 ` Krzysztof Kozlowski
2025-03-14 16:00 ` [PATCH 0/2] Add dma-coherent for gs101 UFS dt node Bart Van Assche
2025-03-14 17:16 ` William McVicker
2025-03-17 7:57 ` Peter Griffin
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=c6c90a4b-b8d2-45d1-928a-464281ce7b37@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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