Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ye Zhang <ye.zhang@rock-chips.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	 Heiko Stuebner <heiko@sntech.de>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	 Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	 tao.huang@rock-chips.com
Subject: Re: [PATCH v4 1/7] dt-bindings: pinctrl: Add rv1126b pinctrl support
Date: Sun, 28 Dec 2025 11:30:39 +0100	[thread overview]
Message-ID: <20251228-airborne-elated-asp-c8f1fb@quoll> (raw)
In-Reply-To: <20251227114957.3287944-2-ye.zhang@rock-chips.com>

On Sat, Dec 27, 2025 at 07:49:51PM +0800, Ye Zhang wrote:
> The RV1126B is a new SoC that is the successor of the RV1126. It has
> different pinctrl registers and is not compatible with the RV1126.
> Therefore, add a new compatible string for it.
> 
> Signed-off-by: Ye Zhang <ye.zhang@rock-chips.com>
> ---
>  Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml | 1 +
>  1 file changed, 1 insertion(+)

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof



  reply	other threads:[~2025-12-28 10:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27 11:49 [PATCH v4 0/7] pinctrl: rockchip: Add RK3506 and RV1126B pinctrl and RMIO support Ye Zhang
2025-12-27 11:49 ` [PATCH v4 1/7] dt-bindings: pinctrl: Add rv1126b pinctrl support Ye Zhang
2025-12-28 10:30   ` Krzysztof Kozlowski [this message]
2025-12-27 11:49 ` [PATCH v4 2/7] pinctrl: rockchip: " Ye Zhang
2025-12-27 11:49 ` [PATCH v4 3/7] arm64: dts: rockchip: rv1126b: Add pinconf and pinctrl dtsi for rv1126b Ye Zhang
2026-01-04 11:54   ` Linus Walleij
2025-12-27 11:49 ` [PATCH v4 4/7] gpio: rockchip: support new version GPIO Ye Zhang
2025-12-27 11:49 ` [PATCH v4 5/7] dt-bindings: pinctrl: rockchip: Add rk3506 rmio support Ye Zhang
2025-12-28 10:37   ` Krzysztof Kozlowski
2025-12-31 10:12     ` Ye Zhang
2026-01-04 11:48   ` Linus Walleij
2025-12-27 11:49 ` [PATCH v4 6/7] pinctrl: rockchip: Add RK3506 RMIO support Ye Zhang
     [not found] ` <20251227114957.3287944-8-ye.zhang@rock-chips.com>
2025-12-28 10:37   ` [PATCH v4 7/7] ARM: dts: rockchip: rk3506: Add pinctrl and rmio dtsi for rk3506 Krzysztof Kozlowski
     [not found]     ` <AGkAtwAtJy-UDFfi3M2RSaqR.3.1766993111418.Hmail.ye.zhang@rock-chips.com>
2025-12-29  8:47       ` Krzysztof Kozlowski
2025-12-31  8:12     ` Ye Zhang
2026-01-04 12:07       ` Linus Walleij
     [not found]     ` <543e7200-2126-490a-a7a8-4898362a910d@rock-chips.com>
2026-02-08 10:31       ` Krzysztof Kozlowski
2026-01-04 12:00   ` Linus Walleij

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=20251228-airborne-elated-asp-c8f1fb@quoll \
    --to=krzk@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=tao.huang@rock-chips.com \
    --cc=ye.zhang@rock-chips.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