From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Dong Aisheng" <dong.aisheng@linaro.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>
Subject: Re[10]: [PATCH v3] mfd: syscon: Add non-DT support
Date: Wed, 20 Feb 2013 16:47:52 +0400 [thread overview]
Message-ID: <1361364471.967042408@f233.mail.ru> (raw)
In-Reply-To: 201302201114.49304.arnd@arndb.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2264 bytes --]
> On 20 February 2013 19:14, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Wednesday 20 February 2013, Dong Aisheng wrote:
> >> On 20 February 2013 18:06, Arnd Bergmann <arnd@arndb.de> wrote:
> >> > I would first like to get an answer to the question I asked in my first mail,
> >> > which is what the use case of non-DT support in this driver is. If this
> >> > is used only by a new platform that has to use DT anyway, or by an existing
> >> > platform that is easy enough to convert, we probably shouldn't do all this
> >> > at all.
> >> >
> >>
> >> If the platform can convert to dt, then we do not have such issue.
> >> The question is do we allow the existing non-dt platforms to use it
> >> before converting?
> >
> > I think the answer to that is "it depends". It's basically a question of
> > how much work it would be to convert the platforms that need it over to
> > DT, and how much of the interface it actually needs. E.g. if there is
> > only one in-tree platform that needs to use syscon but can't easily be
> > moved over to DT, but that platform can only have a single syscon device,
> > then we don't need any of the matching support but could simply return
> > the first regmap area we have in the list.
> >
> > Of course, if the platform in question is out of tree, I would argue
> > that the whatever patches are needed by that platform should also
> > remain out of tree.
> >
>
> Basically i agree with your point.
> Alexander seems to be the first non-dt user of syscon driver.
> He may answer whether they could choose to convert to dt first.
> But one question i wonder is that it may be hard to know how many poteintial
> non-dt platforms may use syscon.
OK. I can convert platform to DT, no so easy, but possible.
But I will use syscon as way to using DT (and MULTIPLATFORM in the future),
this mean that I should completely drop ATAG support from this platform
(since I cannot use syscon device without DT support, but several platform devices
need to use system-wide registers).
Arnd, if its OK for you, I will use this way. (I talking about CLPS711X, you know it :) ).
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-02-20 12:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 14:42 [PATCH v3] mfd: syscon: Add non-DT support Alexander Shiyan
2013-02-18 16:02 ` Arnd Bergmann
2013-02-19 5:52 ` Dong Aisheng
2013-02-19 7:03 ` Re[2]: " Alexander Shiyan
2013-02-19 7:55 ` Dong Aisheng
2013-02-19 8:02 ` Dong Aisheng
2013-02-19 8:56 ` Re[4]: " Alexander Shiyan
2013-02-19 9:58 ` Dong Aisheng
2013-02-19 10:54 ` Re[6]: " Alexander Shiyan
2013-02-20 5:20 ` Dong Aisheng
2013-02-20 5:41 ` Re[8]: " Alexander Shiyan
2013-02-20 6:01 ` Dong Aisheng
2013-02-20 10:06 ` Arnd Bergmann
2013-02-20 11:05 ` Dong Aisheng
2013-02-20 11:14 ` Arnd Bergmann
2013-02-20 11:28 ` Dong Aisheng
2013-02-20 12:16 ` Arnd Bergmann
2013-02-20 12:47 ` Alexander Shiyan [this message]
2013-02-20 15:00 ` Re[10]: " Arnd Bergmann
2013-02-20 16:06 ` Re[12]: " Alexander Shiyan
2013-02-20 17:16 ` Arnd Bergmann
2013-02-20 17:27 ` Re[14]: " Alexander Shiyan
2013-02-20 21:27 ` Arnd Bergmann
2013-02-21 15:27 ` Re[16]: " Alexander Shiyan
2013-02-19 10:49 ` Re[2]: " Arnd Bergmann
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=1361364471.967042408@f233.mail.ru \
--to=shc_work@mail.ru \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dong.aisheng@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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