From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC] ARM: shmobile: Koelsch DT serial integration prototype
Date: Thu, 24 Apr 2014 18:48:10 +0000 [thread overview]
Message-ID: <53595C6A.6080004@cogentembedded.com> (raw)
In-Reply-To: <20140421013114.3236.90868.sendpatchset@w520>
Hello.
On 04/24/2014 09:45 AM, Magnus Damm wrote:
>> [...]
>>>>>>> A simple serial port integration prototype that happens to
>>>>>>> target Koelsch. Written to propose how to move one step closer
>>>>>>> to integrate DT support for serial ports on mach-shmobile.
>>>>>> I think you've over-engineering it. I would just switch serial devices
>>>>>> to
>>>>>> DT in one go, like we do for all other devices.
>>>>> I agree about the risk of over-engineering! =)
>>>>> At the same time I would like to integrate your serial DT support as
>>>>> soon as
>>>>> possible. Order wise I'd like to integrate your serial DT support before
>>>>> phasing out legacy board code. We can of course discuss the order, but
>>>>> if we
>>>>> first integrate serial DT then we end up with 3 different serial cases
>>>> The fact that we even have 3 different cases (DT only, C DT reference and
>>>> C
>>>> legacy) shows that there's a problem. We started with C code that we
>>>> forked
>>>> into C DT reference code instead of porting the C code over to DT, and
>>>> now we
>>>> want to keep using platform devices in the C DT reference code ? Come
>>>> on...
>>> What is the problem? We need to encourage development and also provide
>>> a stable base. And from my point of view, you're not even supposed to
>>> use the C DT reference code as a developer - you should use DT-only
>>> board support for development.
>> I wonder how DT-only support (without C reference code) is possible with
>> the current devel branch: only board-{lager|koelsch}-reference.c include
>> call to of_platform_populate() without which DT probing drivers won't see
>> their devices. If we had that call in the setup-r8a779[01].c then I would
>> have understood what you mean by DT-only...
> I believe the machine vector in setup-r8a779x.c is enough at this
> point, perhaps you don't are missing the default case when certain
> callbacks are left as NULL?
Ah, indeed, init_machine() is missing and in this case
of_platform_populate() is called! Thank you, it wasn't obvious to me.
> / magnus
WBR, Sergei
prev parent reply other threads:[~2014-04-24 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 1:31 [PATCH/RFC] ARM: shmobile: Koelsch DT serial integration prototype Magnus Damm
2014-04-21 8:56 ` Geert Uytterhoeven
2014-04-21 9:50 ` Laurent Pinchart
2014-04-21 10:22 ` Geert Uytterhoeven
2014-04-21 21:09 ` Laurent Pinchart
2014-04-21 21:26 ` Geert Uytterhoeven
2014-04-23 0:46 ` Simon Horman
2014-04-23 2:01 ` Magnus Damm
2014-04-23 2:07 ` Magnus Damm
2014-04-23 12:00 ` Laurent Pinchart
2014-04-23 12:22 ` Magnus Damm
2014-04-23 13:36 ` Magnus Damm
2014-04-23 22:18 ` Sergei Shtylyov
2014-04-24 0:49 ` Simon Horman
2014-04-24 5:45 ` Magnus Damm
2014-04-24 7:03 ` Geert Uytterhoeven
2014-04-24 18:48 ` Sergei Shtylyov [this message]
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=53595C6A.6080004@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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.