From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Milo Kim <woogyom.kim@gmail.com>
Cc: devicetree@vger.kernel.org, linux-pwm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] ARM: dts: sun8i: Add PWM pin in H3
Date: Thu, 1 Sep 2016 21:51:12 +0200 [thread overview]
Message-ID: <20160901195112.GG20462@lukather> (raw)
In-Reply-To: <998fe271-138b-ea4a-99ac-4cd75eefc9c4@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2880 bytes --]
On Thu, Sep 01, 2016 at 10:06:12PM +0900, Milo Kim wrote:
> On 09/01/2016 01:20 AM, Maxime Ripard wrote:
> >Hi Milo,
> >
> >On Wed, Aug 31, 2016 at 05:25:17PM +0900, Milo Kim wrote:
> >>H3 PA5 pin is assigned for single PWM channel.
> >>
> >>Cc: Rob Herring <robh+dt@kernel.org>
> >>Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> >>Cc: Chen-Yu Tsai <wens@csie.org>
> >>Cc: devicetree@vger.kernel.org
> >>Cc: linux-arm-kernel@lists.infradead.org
> >>Cc: linux-kernel@vger.kernel.org
> >>Signed-off-by: Milo Kim <woogyom.kim@gmail.com>
> >>---
> >> arch/arm/boot/dts/sun8i-h3.dtsi | 7 +++++++
> >> 1 file changed, 7 insertions(+)
> >>
> >>diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
> >>index fdf9fdb..05d0c4b 100644
> >>--- a/arch/arm/boot/dts/sun8i-h3.dtsi
> >>+++ b/arch/arm/boot/dts/sun8i-h3.dtsi
> >>@@ -360,6 +360,13 @@
> >> allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
> >> };
> >>
> >>+ pwm0_pin_a: pwm0@0 {
> >>+ allwinner,pins = "PA5";
> >>+ allwinner,function = "pwm0";
> >>+ allwinner,drive = <SUN4I_PINCTRL_10_MA>;
> >>+ allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
> >>+ };
> >>+
> >
> >Is it used on any boards?
> >
> >If not, we have the policy of not merging the pinctrl nodes that are
> >not used by anyone to avoid bloating the DT for no particular reason.
>
> Yes, I have. It's Nano Pi M1 which was derived from Orange Pi PC.
> The board DTS is ready to be sent out, but I'm not sure which is better.
>
> a) Send new board DTS file in other patch thread
>
> [PATCH v3 0/4] Add PWM feature in Allwinner H3
> [PATCH v3 1/4] ARM: dts: sun8i: Add PWM pin in H3
> ..
> [PATCH v3 4/4] pwm: sunxi: Add H3 support
>
> [PATCH] ARM: dts: sun8i: Add Nano Pi M1 support
>
> Or
>
> b) Include the DTS in next patch-set v3
> [PATCH v3 0/4] Add PWM feature in Allwinner H3
> [PATCH v3 1/4] ARM: dts: sun8i: Add PWM pin in H3
> [PATCH v3 2/4] ARM: dts: sun8i: Add PWM controller node in H3
> [PATCH v3 3/4] ARM: dts: sun8i: Add Nano Pi M1 support
> ...
Generally speaking, I'd prefer:
[PATCH v3 1/2] pwm: sunxi: Add H3 support
[PATCH v3 2/2] ARM: dts: sun8i: Add PWM controller node in H3
(It's usually better to add support for something and then add it)
And then
[PATCH v1 1/2] ARM: dts: sun8i: Add PWM pin in H3
[PATCH v1 2/2] ARM: dts: sun8i: Add Nano Pi M1 support
However, judging from the board documentation, that pin is labelled as
PWM1/GPIOA6, which means that they don't enforce any usage on that pin
(as opposed to the pin 3 and 5 for example, which are forced to i2c0).
In such a case, we also don't enforce anything, since any user should
be able to use it for whatever he or she wants.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2016-09-01 19:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:25 [PATCH v2 0/4] Add PWM feature in Allwinner H3 Milo Kim
2016-08-31 8:25 ` [PATCH v2 1/4] ARM: dts: sun8i: Add PWM pin in H3 Milo Kim
2016-08-31 8:33 ` Chen-Yu Tsai
2016-09-01 12:51 ` Milo Kim
2016-08-31 16:20 ` Maxime Ripard
2016-09-01 13:06 ` Milo Kim
2016-09-01 19:51 ` Maxime Ripard [this message]
2016-08-31 8:25 ` [PATCH v2 2/4] ARM: dts: sun8i: Add PWM controller node " Milo Kim
2016-08-31 8:42 ` Chen-Yu Tsai
2016-08-31 16:16 ` Maxime Ripard
2016-08-31 8:25 ` [PATCH v2 3/4] pinctrl: sunxi: Remove unsupported PWM channel pinmux " Milo Kim
2016-08-31 8:35 ` Chen-Yu Tsai
[not found] ` <20160831082520.25962-4-woogyom.kim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-07 19:41 ` Linus Walleij
2016-09-07 19:54 ` Maxime Ripard
2016-09-07 23:09 ` Linus Walleij
2016-08-31 8:25 ` [PATCH v2 4/4] pwm: sunxi: Add H3 support Milo Kim
2016-08-31 8:41 ` Chen-Yu Tsai
2016-09-01 10:39 ` Alexandre Belloni
[not found] ` <20160831082520.25962-5-woogyom.kim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-02 15:18 ` Rob Herring
2016-09-05 10:09 ` Thierry Reding
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=20160901195112.GG20462@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.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-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=wens@csie.org \
--cc=woogyom.kim@gmail.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;
as well as URLs for NNTP newsgroup(s).