From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC] ARM: shmobile: Koelsch DT serial integration prototype
Date: Wed, 23 Apr 2014 12:00:58 +0000 [thread overview]
Message-ID: <3315292.Fn4BZ0n38N@avalon> (raw)
In-Reply-To: <20140421013114.3236.90868.sendpatchset@w520>
Hi Magnus,
On Wednesday 23 April 2014 11:07:25 Magnus Damm wrote:
> On Mon, Apr 21, 2014 at 6:50 PM, Laurent Pinchart wrote:
> > On Monday 21 April 2014 10:31:14 Magnus Damm wrote:
> >> From: Magnus Damm <damm@opensource.se>
> >>
> >> 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's the next step, introducing new C DT reference-but-better board files ?
:-) The C DT reference board files need to be ported to DT or dropped
altogether right now. Any intermediate solution is just asking for trouble.
> since legacy does not use DT for "regular devices" at all. This seems quite
> messy in my mind, so with this proposal I hope to let all us upstream
> developers focus on the "DT-only board code" case that should move forward
> unrestricted, and at the same time keep the C board code as-is serial port
> wise but also start phasing out more aggressively.
>
> I'm also considering handling timers the same. The point is to allow
> unrestricted development of "DT-only board code" and still limit the
> amount of churn for legacy to a bare minimum.
Seriously ? Count me out on that...
> Let us discuss more face to face at ELC!
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-23 12:00 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 [this message]
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
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=3315292.Fn4BZ0n38N@avalon \
--to=laurent.pinchart@ideasonboard.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.