From: "Heiko Stübner" <heiko@sntech.de>
To: thierry.reding@gmail.com, lee.jones@linaro.org
Cc: u.kleine-koenig@pengutronix.de, robh+dt@kernel.org,
cl@rock-chips.com, pgwipeout@gmail.com, xxm@rock-chips.com,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: rockchip: add description for rk3568
Date: Mon, 26 Jul 2021 11:08:29 +0200 [thread overview]
Message-ID: <5607670.PIDvDuAF1L@diego> (raw)
In-Reply-To: <20210726090355.1548483-1-heiko@sntech.de>
Am Montag, 26. Juli 2021, 11:03:54 CEST schrieb Heiko Stuebner:
> From: Liang Chen <cl@rock-chips.com>
>
> add "rockchip,rk3568-pwm", "rockchip,rk3328-pwm" for pwm nodes on
> a rk3568 platform to pwm-rockchip.yaml.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Sorry, forgot to read the slightly longer original reply thread.
The binding is already:
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Acked-by: Rob Herring <robh@kernel.org>
And I guess the pwm maintainers would be responsible for picking
up the binding addition and I will pick the devicetree addition after that.
Heiko
> ---
> The core rk3568 support was mostly applied, leaving out the pwm
> parts. So I've separated the binding and dtsi patch out
> into its owm series, so it can be better reviewed.
>
> Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> index 5596bee70509..81a54a4e8e3e 100644
> --- a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> +++ b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> @@ -29,6 +29,7 @@ properties:
> - enum:
> - rockchip,px30-pwm
> - rockchip,rk3308-pwm
> + - rockchip,rk3568-pwm
> - const: rockchip,rk3328-pwm
>
> reg:
>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: thierry.reding@gmail.com, lee.jones@linaro.org
Cc: u.kleine-koenig@pengutronix.de, robh+dt@kernel.org,
cl@rock-chips.com, pgwipeout@gmail.com, xxm@rock-chips.com,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: rockchip: add description for rk3568
Date: Mon, 26 Jul 2021 11:08:29 +0200 [thread overview]
Message-ID: <5607670.PIDvDuAF1L@diego> (raw)
In-Reply-To: <20210726090355.1548483-1-heiko@sntech.de>
Am Montag, 26. Juli 2021, 11:03:54 CEST schrieb Heiko Stuebner:
> From: Liang Chen <cl@rock-chips.com>
>
> add "rockchip,rk3568-pwm", "rockchip,rk3328-pwm" for pwm nodes on
> a rk3568 platform to pwm-rockchip.yaml.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Sorry, forgot to read the slightly longer original reply thread.
The binding is already:
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Acked-by: Rob Herring <robh@kernel.org>
And I guess the pwm maintainers would be responsible for picking
up the binding addition and I will pick the devicetree addition after that.
Heiko
> ---
> The core rk3568 support was mostly applied, leaving out the pwm
> parts. So I've separated the binding and dtsi patch out
> into its owm series, so it can be better reviewed.
>
> Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> index 5596bee70509..81a54a4e8e3e 100644
> --- a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> +++ b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> @@ -29,6 +29,7 @@ properties:
> - enum:
> - rockchip,px30-pwm
> - rockchip,rk3308-pwm
> + - rockchip,rk3568-pwm
> - const: rockchip,rk3328-pwm
>
> reg:
>
_______________________________________________
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: thierry.reding@gmail.com, lee.jones@linaro.org
Cc: u.kleine-koenig@pengutronix.de, robh+dt@kernel.org,
cl@rock-chips.com, pgwipeout@gmail.com, xxm@rock-chips.com,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: rockchip: add description for rk3568
Date: Mon, 26 Jul 2021 11:08:29 +0200 [thread overview]
Message-ID: <5607670.PIDvDuAF1L@diego> (raw)
In-Reply-To: <20210726090355.1548483-1-heiko@sntech.de>
Am Montag, 26. Juli 2021, 11:03:54 CEST schrieb Heiko Stuebner:
> From: Liang Chen <cl@rock-chips.com>
>
> add "rockchip,rk3568-pwm", "rockchip,rk3328-pwm" for pwm nodes on
> a rk3568 platform to pwm-rockchip.yaml.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Sorry, forgot to read the slightly longer original reply thread.
The binding is already:
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Acked-by: Rob Herring <robh@kernel.org>
And I guess the pwm maintainers would be responsible for picking
up the binding addition and I will pick the devicetree addition after that.
Heiko
> ---
> The core rk3568 support was mostly applied, leaving out the pwm
> parts. So I've separated the binding and dtsi patch out
> into its owm series, so it can be better reviewed.
>
> Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> index 5596bee70509..81a54a4e8e3e 100644
> --- a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> +++ b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
> @@ -29,6 +29,7 @@ properties:
> - enum:
> - rockchip,px30-pwm
> - rockchip,rk3308-pwm
> + - rockchip,rk3568-pwm
> - const: rockchip,rk3328-pwm
>
> reg:
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-26 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 9:03 [PATCH 1/2] dt-bindings: pwm: rockchip: add description for rk3568 Heiko Stuebner
2021-07-26 9:03 ` Heiko Stuebner
2021-07-26 9:03 ` Heiko Stuebner
2021-07-26 9:03 ` [PATCH 2/2] arm64: dts: rockchip: add pwm nodes " Heiko Stuebner
2021-07-26 9:03 ` Heiko Stuebner
2021-07-26 9:03 ` Heiko Stuebner
2021-07-26 9:08 ` Heiko Stübner [this message]
2021-07-26 9:08 ` [PATCH 1/2] dt-bindings: pwm: rockchip: add description " Heiko Stübner
2021-07-26 9:08 ` Heiko Stübner
2021-09-27 21:47 ` (subset) " Heiko Stuebner
2021-09-27 21:47 ` Heiko Stuebner
2021-09-27 21:47 ` 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=5607670.PIDvDuAF1L@diego \
--to=heiko@sntech.de \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=xxm@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 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.