From: "Heiko Stübner" <heiko@sntech.de>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kever Yang <kever.yang@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 5/6] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl
Date: Sun, 18 Sep 2022 11:29:13 +0200 [thread overview]
Message-ID: <2646893.mvXUDI8C0e@diego> (raw)
In-Reply-To: <CA+VMnFwb0bmvsmAqbfEN12BGsTXfxPs2UimjNf9cAvayKBLrbQ@mail.gmail.com>
Am Samstag, 17. September 2022, 16:37:45 CEST schrieb Jagan Teki:
> Hi Heiko,
>
> On Sat, 17 Sept 2022 at 19:56, Heiko Stuebner <heiko@sntech.de> wrote:
> >
> > Hi Jagan,
> >
> > Am Donnerstag, 15. September 2022, 18:39:46 CEST schrieb Jagan Teki:
> > > Add pinctrl definitions for Rockchip RV1126 and the pinctrl
> > > conf's are included it from arm64 rockchip devicetree path.
> >
> > I'm not sure I remember the cause. So could you tell me
> > why they are needed in the arm64-space as well?
>
> From RK3568 on-wards pinctrl configurations are maintained in common
> conf file rockchip-pinconf.dtsi and it is available in arm64 path
> (arch/arm64/boot/dts/rockchip/rockchip-pinconf.dtsi). So even for
> RV1126 this patch uses that common conf file as these are common
> across all rockchip platforms.
>
> Let me know if I'm missing anything?
looking at it closely, _now_ I see the inclusion of the arm64
pinconfig dtsi :-D .
While travelling to and from ELCE I somehow missed seeing that.
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 Stübner" <heiko@sntech.de>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kever Yang <kever.yang@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 5/6] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl
Date: Sun, 18 Sep 2022 11:29:13 +0200 [thread overview]
Message-ID: <2646893.mvXUDI8C0e@diego> (raw)
In-Reply-To: <CA+VMnFwb0bmvsmAqbfEN12BGsTXfxPs2UimjNf9cAvayKBLrbQ@mail.gmail.com>
Am Samstag, 17. September 2022, 16:37:45 CEST schrieb Jagan Teki:
> Hi Heiko,
>
> On Sat, 17 Sept 2022 at 19:56, Heiko Stuebner <heiko@sntech.de> wrote:
> >
> > Hi Jagan,
> >
> > Am Donnerstag, 15. September 2022, 18:39:46 CEST schrieb Jagan Teki:
> > > Add pinctrl definitions for Rockchip RV1126 and the pinctrl
> > > conf's are included it from arm64 rockchip devicetree path.
> >
> > I'm not sure I remember the cause. So could you tell me
> > why they are needed in the arm64-space as well?
>
> From RK3568 on-wards pinctrl configurations are maintained in common
> conf file rockchip-pinconf.dtsi and it is available in arm64 path
> (arch/arm64/boot/dts/rockchip/rockchip-pinconf.dtsi). So even for
> RV1126 this patch uses that common conf file as these are common
> across all rockchip platforms.
>
> Let me know if I'm missing anything?
looking at it closely, _now_ I see the inclusion of the arm64
pinconfig dtsi :-D .
While travelling to and from ELCE I somehow missed seeing that.
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 Stübner" <heiko@sntech.de>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kever Yang <kever.yang@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 5/6] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl
Date: Sun, 18 Sep 2022 11:29:13 +0200 [thread overview]
Message-ID: <2646893.mvXUDI8C0e@diego> (raw)
In-Reply-To: <CA+VMnFwb0bmvsmAqbfEN12BGsTXfxPs2UimjNf9cAvayKBLrbQ@mail.gmail.com>
Am Samstag, 17. September 2022, 16:37:45 CEST schrieb Jagan Teki:
> Hi Heiko,
>
> On Sat, 17 Sept 2022 at 19:56, Heiko Stuebner <heiko@sntech.de> wrote:
> >
> > Hi Jagan,
> >
> > Am Donnerstag, 15. September 2022, 18:39:46 CEST schrieb Jagan Teki:
> > > Add pinctrl definitions for Rockchip RV1126 and the pinctrl
> > > conf's are included it from arm64 rockchip devicetree path.
> >
> > I'm not sure I remember the cause. So could you tell me
> > why they are needed in the arm64-space as well?
>
> From RK3568 on-wards pinctrl configurations are maintained in common
> conf file rockchip-pinconf.dtsi and it is available in arm64 path
> (arch/arm64/boot/dts/rockchip/rockchip-pinconf.dtsi). So even for
> RV1126 this patch uses that common conf file as these are common
> across all rockchip platforms.
>
> Let me know if I'm missing anything?
looking at it closely, _now_ I see the inclusion of the arm64
pinconfig dtsi :-D .
While travelling to and from ELCE I somehow missed seeing that.
Heiko
next prev parent reply other threads:[~2022-09-18 9:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 16:39 [PATCH v5 0/6] ARM: Add Rockchip RV1126 support Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` [PATCH v5 1/6] i2c: rk3x: Add rv1126 support Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-16 19:29 ` Wolfram Sang
2022-09-16 19:29 ` Wolfram Sang
2022-09-16 19:29 ` Wolfram Sang
2022-09-15 16:39 ` [PATCH v5 2/6] clk: rockchip: Add dt-binding header for RV1126 Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` [PATCH v5 3/6] dt-bindings: clock: rockchip: Document RV1126 CRU Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` [PATCH v5 4/6] clk: rockchip: Add clock controller support for RV1126 SoC Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-17 6:55 ` Heiko Stuebner
2022-09-17 6:55 ` Heiko Stuebner
2022-09-17 6:55 ` Heiko Stuebner
2022-09-17 11:58 ` Jagan Teki
2022-09-17 11:58 ` Jagan Teki
2022-09-17 11:58 ` Jagan Teki
2022-09-17 14:25 ` Heiko Stuebner
2022-09-17 14:25 ` Heiko Stuebner
2022-09-17 14:25 ` Heiko Stuebner
2022-09-15 16:39 ` [PATCH v5 5/6] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-17 14:26 ` Heiko Stuebner
2022-09-17 14:26 ` Heiko Stuebner
2022-09-17 14:26 ` Heiko Stuebner
2022-09-17 14:37 ` Jagan Teki
2022-09-17 14:37 ` Jagan Teki
2022-09-17 14:37 ` Jagan Teki
2022-09-18 9:29 ` Heiko Stübner [this message]
2022-09-18 9:29 ` Heiko Stübner
2022-09-18 9:29 ` Heiko Stübner
2022-09-15 16:39 ` [PATCH v5 6/6] ARM: dts: rockchip: Add Rockchip RV1126 SoC Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-15 16:39 ` Jagan Teki
2022-09-23 13:33 ` Heiko Stuebner
2022-09-23 13:33 ` Heiko Stuebner
2022-09-23 13:33 ` Heiko Stuebner
2022-09-23 13:38 ` Jagan Teki
2022-09-23 13:38 ` Jagan Teki
2022-09-23 13:38 ` Jagan Teki
2022-09-18 8:45 ` (subset) [PATCH v5 0/6] ARM: Add Rockchip RV1126 support Heiko Stuebner
2022-09-18 8:45 ` Heiko Stuebner
2022-09-18 8:45 ` 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=2646893.mvXUDI8C0e@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jagan@edgeble.ai \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.