From: James Hogan <james.hogan@imgtec.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"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: Thu, 20 Jun 2013 13:44:26 +0100 [thread overview]
Message-ID: <51C2F92A.5050101@imgtec.com> (raw)
In-Reply-To: <CACRpkdbFEKJxQfvT4xR4z1iymHPmbbCYJriVPD95P_L0oCC6Jg@mail.gmail.com>
On 18/06/13 10:05, Linus Walleij wrote:
> On Tue, Jun 18, 2013 at 10:51 AM, James Hogan <james.hogan@imgtec.com> wrote:
>
>> 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?
>
> This is an orthogonal issue I'd say.
agreed.
> Basically this goes back to the quite prolonged discussion about
> device tree bindings and the fact that we added the
> .dt_node_to_map() and .dt_free_map() functions in the
> first place.
>
> I'd be happy to consolidate these mapping functions where
> possible, by moving to the core, basically.
>
> But that would be a separate patch series.... interested? ;-)
Mildly, but I can't guarantee I'll get the time.
Cheers
James
next prev parent reply other threads:[~2013-06-20 12:44 UTC|newest]
Thread overview: 9+ 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 ` [PATCH v7 1/3] sh-pfc: Remove support for platform data Laurent Pinchart
2013-06-17 18:50 ` [PATCH v7 2/3] sh-pfc: Add DT support Laurent Pinchart
2013-06-17 18:50 ` [PATCH v7 3/3] sh-pfc: Add pinconf support to DT bindings 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:51 ` James Hogan
2013-06-18 9:05 ` Linus Walleij
2013-06-20 12:44 ` James Hogan [this message]
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=51C2F92A.5050101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox