From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Serge Semin <fancer.lancer@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
linux-ide@vger.kernel.org, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
kernel@collabora.com
Subject: [PATCH v2 0/6] Add RK3588 SATA support
Date: Mon, 22 May 2023 19:34:17 +0200 [thread overview]
Message-ID: <20230522173423.64691-1-sebastian.reichel@collabora.com> (raw)
Hi,
This enables SATA support for RK3588.
Changes since PATCHv1:
* https://lore.kernel.org/all/20230413182345.92557-1-sebastian.reichel@collabora.com/
* Rebase to v6.4-rc1
* Collect Acked-by for syscon DT binding update
* Use ASIC clock description suggested by Serge Semin
* Also add RBC clock (not used by RK3588)
* Add extra patch narrowing down the allowed clocks for RK356x and RK3588
-- Sebastian
Sebastian Reichel (6):
dt-bindings: soc: rockchip: add rk3588 pipe-phy syscon
dt-bindings: ata: ahci: add RK3588 AHCI controller
dt-bindings: ata: ahci: dwc: enforce rockchip clocks
dt-bindings: phy: rockchip: rk3588 has two reset lines
arm64: dts: rockchip: rk3588: add combo PHYs
arm64: dts: rockchip: rk3588: add SATA support
.../bindings/ata/snps,dwc-ahci-common.yaml | 8 +-
.../bindings/ata/snps,dwc-ahci.yaml | 40 +++++++--
.../phy/phy-rockchip-naneng-combphy.yaml | 8 +-
.../devicetree/bindings/soc/rockchip/grf.yaml | 1 +
arch/arm64/boot/dts/rockchip/rk3588.dtsi | 44 +++++++++
arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 90 +++++++++++++++++++
6 files changed, 183 insertions(+), 8 deletions(-)
--
2.39.2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2023-05-22 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 17:34 Sebastian Reichel [this message]
2023-05-22 17:34 ` [PATCH v2 1/6] dt-bindings: soc: rockchip: add rk3588 pipe-phy syscon Sebastian Reichel
2023-05-22 17:34 ` [PATCH v2 2/6] dt-bindings: ata: ahci: add RK3588 AHCI controller Sebastian Reichel
2023-05-22 19:33 ` Conor Dooley
2023-06-04 18:58 ` Serge Semin
2023-05-22 17:34 ` [PATCH v2 3/6] dt-bindings: ata: ahci: dwc: enforce rockchip clocks Sebastian Reichel
2023-06-04 19:11 ` Serge Semin
2023-05-22 17:34 ` [PATCH v2 4/6] dt-bindings: phy: rockchip: rk3588 has two reset lines Sebastian Reichel
2023-05-22 19:24 ` Conor Dooley
2023-05-22 17:34 ` [PATCH v2 5/6] arm64: dts: rockchip: rk3588: add combo PHYs Sebastian Reichel
2023-05-22 17:34 ` [PATCH v2 6/6] arm64: dts: rockchip: rk3588: add SATA support Sebastian Reichel
2023-05-31 11:35 ` [PATCH v2 0/6] Add RK3588 " Serge Semin
2023-06-06 17:07 ` (subset) " Heiko Stuebner
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=20230522173423.64691-1-sebastian.reichel@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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