From: James Hogan <james.hogan@imgtec.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"Magnus Damm" <damm@opensource.se>,
"Simon Horman" <horms@verge.net.au>
Subject: Re: [PATCH v7 0/3] SH pinctrl DT support
Date: Tue, 18 Jun 2013 08:51:59 +0000 [thread overview]
Message-ID: <51C01FAF.8050006@imgtec.com> (raw)
In-Reply-To: <CACRpkdZh709J3pFsfbReQ20LU5W0Q1HacE0ZpssWXofKTJJ6pQ@mail.gmail.com>
On 18/06/13 09:05, Linus Walleij wrote:
> On Mon, Jun 17, 2013 at 8:50 PM, Laurent Pinchart
> <laurent.pinchart+renesas@ideasonboard.com> wrote:
>
>> Hello,
>>
>> Here's the seventh (and hopefully final) version of the SuperH and SH Mobile
>> pin controllers (PFC) DT support patch set.
>>
>> The patches have been rebased on the for-next branch of the pinctrl
>> repository. All ARM-specific patches have been dropped and will be pushed
>> through to ARM SoC tree in v3.12. This series thus only contains DT support
>> for the sh-pfc driver.
>>
>> I've tried merging Simon's latest tag (renesas-next-20130617v3) with these
>> patches and no conflict occurred. Linus, would it finally be possible to get
>> this applied for v3.11 ?
>>
>> Changes since v6:
>>
>> - Added generic pinconf support back
>> - Dropped all ARM-specific patches
>
> Thanks, this looks really nice and I've applied all three.
>
> Heiko, James can you have a look from a generic pinconf
> point of view so we are sure we get this right? (Looks right
> to me atleast.)
The generic pinconf stuff in these patches looks reasonable to me.
Should we be standardizing the pins/groups/function properties too,
since the strings are pretty much passed straight through? The usage
seems pretty similar between the drivers I've seen (except ugly vendor
prefixes), so we could presumably get away with a single implementation
of dt_node_to_map?
Cheers
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"Magnus Damm" <damm@opensource.se>,
"Simon Horman" <horms@verge.net.au>
Subject: Re: [PATCH v7 0/3] SH pinctrl DT support
Date: Tue, 18 Jun 2013 09:51:59 +0100 [thread overview]
Message-ID: <51C01FAF.8050006@imgtec.com> (raw)
In-Reply-To: <CACRpkdZh709J3pFsfbReQ20LU5W0Q1HacE0ZpssWXofKTJJ6pQ@mail.gmail.com>
On 18/06/13 09:05, Linus Walleij wrote:
> On Mon, Jun 17, 2013 at 8:50 PM, Laurent Pinchart
> <laurent.pinchart+renesas@ideasonboard.com> wrote:
>
>> Hello,
>>
>> Here's the seventh (and hopefully final) version of the SuperH and SH Mobile
>> pin controllers (PFC) DT support patch set.
>>
>> The patches have been rebased on the for-next branch of the pinctrl
>> repository. All ARM-specific patches have been dropped and will be pushed
>> through to ARM SoC tree in v3.12. This series thus only contains DT support
>> for the sh-pfc driver.
>>
>> I've tried merging Simon's latest tag (renesas-next-20130617v3) with these
>> patches and no conflict occurred. Linus, would it finally be possible to get
>> this applied for v3.11 ?
>>
>> Changes since v6:
>>
>> - Added generic pinconf support back
>> - Dropped all ARM-specific patches
>
> Thanks, this looks really nice and I've applied all three.
>
> Heiko, James can you have a look from a generic pinconf
> point of view so we are sure we get this right? (Looks right
> to me atleast.)
The generic pinconf stuff in these patches looks reasonable to me.
Should we be standardizing the pins/groups/function properties too,
since the strings are pretty much passed straight through? The usage
seems pretty similar between the drivers I've seen (except ugly vendor
prefixes), so we could presumably get away with a single implementation
of dt_node_to_map?
Cheers
James
next prev parent reply other threads:[~2013-06-18 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 18:50 [PATCH v7 0/3] SH pinctrl DT support Laurent Pinchart
2013-06-17 18:50 ` Laurent Pinchart
2013-06-17 18:50 ` [PATCH v7 1/3] sh-pfc: Remove support for platform data Laurent Pinchart
2013-06-17 18:50 ` Laurent Pinchart
2013-06-17 18:50 ` [PATCH v7 2/3] sh-pfc: Add DT support Laurent Pinchart
2013-06-17 18:50 ` Laurent Pinchart
2013-06-17 18:50 ` [PATCH v7 3/3] sh-pfc: Add pinconf support to DT bindings Laurent Pinchart
2013-06-17 18:50 ` Laurent Pinchart
[not found] ` <1371495003-11185-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2013-06-18 8:05 ` [PATCH v7 0/3] SH pinctrl DT support Linus Walleij
2013-06-18 8:05 ` Linus Walleij
2013-06-18 8:51 ` James Hogan [this message]
2013-06-18 8:51 ` James Hogan
2013-06-18 9:05 ` Linus Walleij
2013-06-18 9:05 ` Linus Walleij
2013-06-20 12:44 ` James Hogan
2013-06-20 12:44 ` James Hogan
2013-06-18 8:53 ` Heiko Stübner
2013-06-18 8:53 ` Heiko Stübner
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=51C01FAF.8050006@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=damm@opensource.se \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=heiko@sntech.de \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-sh@vger.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.