From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Griffin <peter.griffin@linaro.org>,
mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
kishon@kernel.org, alim.akhtar@samsung.com, avri.altman@wdc.com,
bvanassche@acm.org, s.nawrocki@samsung.com,
cw00.choi@samsung.com, jejb@linux.ibm.com,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, ebiggers@kernel.org
Cc: linux-scsi@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tudor.ambarus@linaro.org,
andre.draszik@linaro.org, saravanak@google.com,
willmcvicker@google.com
Subject: Re: [PATCH v2 00/14] HSI2, UFS & UFS phy support for Tensor GS101
Date: Thu, 25 Apr 2024 09:08:31 +0200 [thread overview]
Message-ID: <1c6f5984-7f9f-47e3-98c3-3c3671512675@kernel.org> (raw)
In-Reply-To: <20240423205006.1785138-1-peter.griffin@linaro.org>
On 23/04/2024 22:49, Peter Griffin wrote:
> Hi James, Martin, Alim, Bart, Krzysztof, Vinod, all
>
> Firstly, many thanks to everyone who reviewed and tested v1.
>
> This series adds support for the High Speed Interface (HSI) 2 clock
> management unit, UFS controller and UFS phy calibration/tuning for GS101
> found in Pixel 6.
>
> With this series applied, UFS is now functional on gs101. The SKhynix
> HN8T05BZGKX015 can be enumerated, partitions mounted etc. This allows us to
> move away from the initramfs rootfs we have been using for development so far.
>
> Merge Strategy
> 1) UFS driver/bindings via UFS/SCSI tree (James / Martin / Alim)
> 2) GS101 DTS/DTSI should go via Krzysztofs Exynos SoC tree
> 3) Clock driver/bindings via Clock tree (Krzysztof / Stephen)
> 4) PHY driver/bindings via PHY tree (Vinod)
>
> The v2 series has been rebased on next-20240422, as such all the phy parts
> which were already queued by Vinod have been dropped. Two new phy patches
> are added to address review feedback received after the patches were queued.
>
> The series is broadly split into the following parts:
> 1) dt-bindings documentation updates
> 2) gs101/oriole dts & dtsi updates
> 3) Prepatory patches for ufs-exynos driver
> 4) GS101 ufs-exynos support
> 5) gs101 phy fixes
>
I asked to split, otherwise please explain why PHY and UFS depends on
DTS and clk.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-25 7:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 20:49 [PATCH v2 00/14] HSI2, UFS & UFS phy support for Tensor GS101 Peter Griffin
2024-04-23 20:49 ` [PATCH v2 01/14] dt-bindings: clock: google,gs101-clock: add HSI2 clock management unit Peter Griffin
2024-04-24 19:51 ` Rob Herring
2024-04-25 12:19 ` André Draszik
2024-04-23 20:49 ` [PATCH v2 02/14] dt-bindings: soc: google: exynos-sysreg: add dedicated hsi2 sysreg compatible Peter Griffin
2024-04-23 20:49 ` [PATCH v2 03/14] dt-bindings: ufs: exynos-ufs: Add gs101 compatible Peter Griffin
2024-04-24 19:53 ` Rob Herring
2024-04-25 16:49 ` Peter Griffin
2024-04-23 20:49 ` [PATCH v2 04/14] arm64: dts: exynos: gs101: enable cmu-hsi2 clock controller Peter Griffin
2024-04-25 11:39 ` André Draszik
2024-04-23 20:49 ` [PATCH v2 05/14] arm64: dts: exynos: gs101: Add the hsi2 sysreg node Peter Griffin
2024-04-25 11:50 ` André Draszik
2024-04-23 20:49 ` [PATCH v2 06/14] arm64: dts: exynos: gs101: Add ufs, ufs-phy and ufs regulator dt nodes Peter Griffin
2024-04-25 12:02 ` André Draszik
2024-04-25 16:35 ` Peter Griffin
2024-04-23 20:49 ` [PATCH v2 07/14] clk: samsung: gs101: add support for cmu_hsi2 Peter Griffin
2024-04-23 20:50 ` [PATCH v2 08/14] scsi: ufs: host: ufs-exynos: Add EXYNOS_UFS_OPT_UFSPR_SECURE option Peter Griffin
2024-04-23 20:50 ` [PATCH v2 09/14] scsi: ufs: host: ufs-exynos: add EXYNOS_UFS_OPT_TIMER_TICK_SELECT option Peter Griffin
2024-04-23 20:50 ` [PATCH v2 10/14] scsi: ufs: host: ufs-exynos: allow max frequencies up to 267Mhz Peter Griffin
2024-04-23 20:50 ` [PATCH v2 11/14] scsi: ufs: host: ufs-exynos: add some pa_dbg_ register offsets into drvdata Peter Griffin
2024-04-23 20:50 ` [PATCH v2 12/14] scsi: ufs: host: ufs-exynos: Add support for Tensor gs101 SoC Peter Griffin
2024-04-23 20:50 ` [PATCH v2 13/14] phy: samsung-ufs: ufs: remove superfluous mfd/syscon.h header Peter Griffin
2024-04-23 20:50 ` [PATCH v2 14/14] phy: samsung-ufs: ufs: exit on first reported error Peter Griffin
2024-04-25 7:08 ` Krzysztof Kozlowski [this message]
2024-04-25 10:31 ` [PATCH v2 00/14] HSI2, UFS & UFS phy support for Tensor GS101 Peter Griffin
2024-04-25 10:47 ` Krzysztof Kozlowski
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=1c6f5984-7f9f-47e3-98c3-3c3671512675@kernel.org \
--to=krzk@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--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=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vkoul@kernel.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