From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/9] ARM: sunxi: Rename pwm0_pins to match our usual pattern
Date: Mon, 6 Feb 2017 18:46:35 +0100 [thread overview]
Message-ID: <20170206174635.wvl7fnxjhmr6e7zc@lukather> (raw)
In-Reply-To: <CAGb2v64tnnG-CTF1C5yqj=VTmB-J_E9dH6Sit8fvWJD-ddw13A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Mon, Feb 06, 2017 at 03:15:15PM +0800, Chen-Yu Tsai wrote:
> On Mon, Feb 6, 2017 at 2:49 AM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > The pwm0_pins group name is suggesting that this is the only option usable
> > for the PWM0 on the SoCs it's declared on. However, this is not the case
> > and defining a second pwm0 group would be quite weird given the name of the
> > first group.
>
> Can you elaborate on the second pwm0 option? I'm not seeing it in my datasheets.
Hmmmm, I'm not sure why I did that anymore, looks like you're right...
I'll drop this one, and queue the others for 4.12.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-02-06 20:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 18:49 [PATCH 0/9] ARM: sun5i: Cleanup and reorganisation of the DTSI Maxime Ripard
2017-02-05 18:49 ` [PATCH 1/9] ARM: sun5i: A10s: Switch the EMAC pins indices Maxime Ripard
2017-02-06 7:10 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 2/9] ARM: sun5i: a10s: switch simple framebuffer indices Maxime Ripard
2017-02-06 7:11 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 3/9] ARM: sunxi: Rename pwm0_pins to match our usual pattern Maxime Ripard
2017-02-06 7:15 ` Chen-Yu Tsai
2017-02-06 17:46 ` Maxime Ripard [this message]
2017-02-05 18:49 ` [PATCH 4/9] ARM: sun5i: Add UART2 pin group Maxime Ripard
2017-02-06 7:17 ` Chen-Yu Tsai
2017-02-06 17:37 ` Maxime Ripard
2017-02-05 18:49 ` [PATCH 5/9] ARM: sun5i: Rename UART3 flow control pins Maxime Ripard
2017-02-06 7:18 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 6/9] ARM: sun5i: a13: Merge common controllers into the common DTSI Maxime Ripard
2017-02-06 7:18 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 7/9] ARM: sun5i: a10s: " Maxime Ripard
2017-02-06 7:21 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 8/9] ARM: sun5i: r8: " Maxime Ripard
2017-02-06 7:22 ` Chen-Yu Tsai
2017-02-05 18:49 ` [PATCH 9/9] ARM: sun5i: gr8: Use common sun5i DTSI Maxime Ripard
2017-02-06 7:30 ` Chen-Yu Tsai
2017-02-06 17:39 ` Maxime Ripard
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=20170206174635.wvl7fnxjhmr6e7zc@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®