From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alessandro Carminati <alessandro.carminati@gmail.com>
Subject: Re: [PATCH 2/2] Add sata version of the quartz64-a board
Date: Fri, 16 Sep 2022 15:12:10 +0200 [thread overview]
Message-ID: <2385186.jE0xQCEvom@phil> (raw)
In-Reply-To: <YyRxx4zovhMMeQYV@lab.hqhome163.com>
Hi Alessandro,
Am Freitag, 16. September 2022, 14:53:27 CEST schrieb Alessandro Carminati:
> The Quartz64 board is built upon Rockchip RK3566.
> Rockchip RK3566 has two combo phys.
> The first connects USB3 and SATA ctrl1, and the second PCIe lane and SATA
> ctrl2.
> The second combo phy is hardwired to the PCIe slot, where for the first,
> the hardware on the board provides both the USB3 connector and the SATA
> connector.
> This DT allows the users to switch the combo phy to the SATA connector.
>
> Signed-off-by: Alessandro Carminati <alessandro.carminati@gmail.com>
I'm not really sure what the best way to do this is.
For one, this is mainly a configuration thing, so I was more thinking
about a devicetree-overlay as the right thing to use.
On the other hand this is touches essential a device you may want to
boot from. Though an initramfs may be able to solve this.
So I'm really not sure - maybe the dt-maintainers can provide some
direction :-)
Some more general stuff below (and here):
Please always use prefixes in your patch subject matching
the subsystem - can be found by just using "git log" on the directory.
Here it would be "arm64: dts: rockchip: foo"
> ---
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts | 9 +++++++++
> 2 files changed, 10 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
>
> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
> index 97ec6c156346..5c82881a92d3 100644
> --- a/arch/arm64/boot/dts/rockchip/Makefile
> +++ b/arch/arm64/boot/dts/rockchip/Makefile
> @@ -60,6 +60,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399pro-rock-pi-n10.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.1.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.2.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.usb3.dtb
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.sata.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-b.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-roc-pc.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-soquartz-cm4.dtb
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> new file mode 100644
> index 000000000000..8620df7ec01e
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> @@ -0,0 +1,9 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include "rk3566-quartz64-a.dtsi"
> +
> +&sata1 {
> + status = "okay";
> +};
I guess you may want to disable the now unused usb controller?
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alessandro Carminati <alessandro.carminati@gmail.com>
Subject: Re: [PATCH 2/2] Add sata version of the quartz64-a board
Date: Fri, 16 Sep 2022 15:12:10 +0200 [thread overview]
Message-ID: <2385186.jE0xQCEvom@phil> (raw)
In-Reply-To: <YyRxx4zovhMMeQYV@lab.hqhome163.com>
Hi Alessandro,
Am Freitag, 16. September 2022, 14:53:27 CEST schrieb Alessandro Carminati:
> The Quartz64 board is built upon Rockchip RK3566.
> Rockchip RK3566 has two combo phys.
> The first connects USB3 and SATA ctrl1, and the second PCIe lane and SATA
> ctrl2.
> The second combo phy is hardwired to the PCIe slot, where for the first,
> the hardware on the board provides both the USB3 connector and the SATA
> connector.
> This DT allows the users to switch the combo phy to the SATA connector.
>
> Signed-off-by: Alessandro Carminati <alessandro.carminati@gmail.com>
I'm not really sure what the best way to do this is.
For one, this is mainly a configuration thing, so I was more thinking
about a devicetree-overlay as the right thing to use.
On the other hand this is touches essential a device you may want to
boot from. Though an initramfs may be able to solve this.
So I'm really not sure - maybe the dt-maintainers can provide some
direction :-)
Some more general stuff below (and here):
Please always use prefixes in your patch subject matching
the subsystem - can be found by just using "git log" on the directory.
Here it would be "arm64: dts: rockchip: foo"
> ---
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts | 9 +++++++++
> 2 files changed, 10 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
>
> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
> index 97ec6c156346..5c82881a92d3 100644
> --- a/arch/arm64/boot/dts/rockchip/Makefile
> +++ b/arch/arm64/boot/dts/rockchip/Makefile
> @@ -60,6 +60,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399pro-rock-pi-n10.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.1.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.2.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.usb3.dtb
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.sata.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-b.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-roc-pc.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-soquartz-cm4.dtb
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> new file mode 100644
> index 000000000000..8620df7ec01e
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> @@ -0,0 +1,9 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include "rk3566-quartz64-a.dtsi"
> +
> +&sata1 {
> + status = "okay";
> +};
I guess you may want to disable the now unused usb controller?
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alessandro Carminati <alessandro.carminati@gmail.com>
Subject: Re: [PATCH 2/2] Add sata version of the quartz64-a board
Date: Fri, 16 Sep 2022 15:12:10 +0200 [thread overview]
Message-ID: <2385186.jE0xQCEvom@phil> (raw)
In-Reply-To: <YyRxx4zovhMMeQYV@lab.hqhome163.com>
Hi Alessandro,
Am Freitag, 16. September 2022, 14:53:27 CEST schrieb Alessandro Carminati:
> The Quartz64 board is built upon Rockchip RK3566.
> Rockchip RK3566 has two combo phys.
> The first connects USB3 and SATA ctrl1, and the second PCIe lane and SATA
> ctrl2.
> The second combo phy is hardwired to the PCIe slot, where for the first,
> the hardware on the board provides both the USB3 connector and the SATA
> connector.
> This DT allows the users to switch the combo phy to the SATA connector.
>
> Signed-off-by: Alessandro Carminati <alessandro.carminati@gmail.com>
I'm not really sure what the best way to do this is.
For one, this is mainly a configuration thing, so I was more thinking
about a devicetree-overlay as the right thing to use.
On the other hand this is touches essential a device you may want to
boot from. Though an initramfs may be able to solve this.
So I'm really not sure - maybe the dt-maintainers can provide some
direction :-)
Some more general stuff below (and here):
Please always use prefixes in your patch subject matching
the subsystem - can be found by just using "git log" on the directory.
Here it would be "arm64: dts: rockchip: foo"
> ---
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts | 9 +++++++++
> 2 files changed, 10 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
>
> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
> index 97ec6c156346..5c82881a92d3 100644
> --- a/arch/arm64/boot/dts/rockchip/Makefile
> +++ b/arch/arm64/boot/dts/rockchip/Makefile
> @@ -60,6 +60,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399pro-rock-pi-n10.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.1.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.2.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.usb3.dtb
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-a.sata.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-quartz64-b.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-roc-pc.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-soquartz-cm4.dtb
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> new file mode 100644
> index 000000000000..8620df7ec01e
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.sata.dts
> @@ -0,0 +1,9 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include "rk3566-quartz64-a.dtsi"
> +
> +&sata1 {
> + status = "okay";
> +};
I guess you may want to disable the now unused usb controller?
Heiko
next prev parent reply other threads:[~2022-09-16 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 12:53 [PATCH 2/2] Add sata version of the quartz64-a board Alessandro Carminati
2022-09-16 12:53 ` Alessandro Carminati
2022-09-16 12:53 ` Alessandro Carminati
2022-09-16 13:12 ` Heiko Stuebner [this message]
2022-09-16 13:12 ` Heiko Stuebner
2022-09-16 13:12 ` Heiko Stuebner
2022-09-16 13:18 ` Heiko Stuebner
2022-09-16 13:18 ` Heiko Stuebner
2022-09-16 13:18 ` Heiko Stuebner
2022-09-16 15:54 ` Alessandro Carminati
2022-09-16 15:54 ` Alessandro Carminati
2022-09-16 15:54 ` Alessandro Carminati
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=2385186.jE0xQCEvom@phil \
--to=heiko@sntech.de \
--cc=alessandro.carminati@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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.