From: Dong Aisheng <dong.aisheng@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alexander Shiyan <shc_work@mail.ru>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Re[8]: [PATCH v3] mfd: syscon: Add non-DT support
Date: Wed, 20 Feb 2013 19:05:59 +0800 [thread overview]
Message-ID: <CAP1dx+xj3+PVu98pRBAOhLxvOzhwE7VNShMLmqk-jy_CgXh8GA@mail.gmail.com> (raw)
In-Reply-To: <201302201006.41287.arnd@arndb.de>
On 20 February 2013 18:06, Arnd Bergmann <arnd@arndb.de> wrote:
> On Wednesday 20 February 2013, Alexander Shiyan wrote:
>> On 20 February 2013 13:41, Alexander Shiyan <shc_work@mail.ru> wrote:
>> >
>> > One problem is that every user needs to add their syscon compatible device
>> > support(platform_device_id) in syscon driver first before they can use it.
>> > But it looks to me just like how other driver generally does.
>>
>> I agree, this is a more proper way, but in this case we should create a big table
>> here with records for each device...
>>
>> > Arnd,
>> > Do you think this is an issue?
>
> 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?
Regards
Dong Aisheng
next prev parent reply other threads:[~2013-02-20 11:06 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 [this message]
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 ` Re[10]: " Alexander Shiyan
2013-02-20 15:00 ` 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=CAP1dx+xj3+PVu98pRBAOhLxvOzhwE7VNShMLmqk-jy_CgXh8GA@mail.gmail.com \
--to=dong.aisheng@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=shc_work@mail.ru \
/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.