From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC/PATCH 5/6] ARM: shmobile: lager: Enable SCIF0 and SCIF1 serial ports in DT
Date: Wed, 30 Apr 2014 16:23:40 +0000 [thread overview]
Message-ID: <3042921.YNIkMUtkoO@avalon> (raw)
In-Reply-To: <1398817906-6023-6-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Simon,
On Wednesday 30 April 2014 10:34:12 Simon Horman wrote:
> On Wed, Apr 30, 2014 at 10:29:23AM +0900, Simon Horman wrote:
> > On Wed, Apr 30, 2014 at 03:02:20AM +0200, Laurent Pinchart wrote:
> > > On Wednesday 30 April 2014 09:59:56 Simon Horman wrote:
> > > > On Wed, Apr 30, 2014 at 02:31:45AM +0200, Laurent Pinchart wrote:
> > > > > SCIF0 and SCIF1 are used as debug serial ports. Enable them and
> > > > > configure pinmuxing appropriately. We can now remove the clkdev
> > > > > registration hack for SCIF devices from the Lager reference board
> > > > > file.
> > > > >
> > > > > As a side effect of switching to DT-based serial port instantiation,
> > > > > ttySC6 and ttySC7 get renamed to ttySC0 and ttySC1. As the device
> > > > > tree source if now shared between lager and lager-reference, we need
> > > > > to update the serial ports in C code as well.
> > > >
> > > > I believe the second paragraph is no longer correct.
> > >
> > > Oops, you're right. If no other problem is found with the series, could
> > > you please just drop that paragraph ?
> >
> > Yes. But could you look at my other comment below?
>
> I mean yes with the following caveat.
>
> It seems to me that each of patch 4 and 5 could applied independently
> of the earlier patches in the series. This seems nice.
I suppose you mean patches 5 and 6.
> It seems to me that patches 3 and 4 depend on patch 2 which in turn
> depends on patch 1. This is less fun. So I was thinking of waiting
> for at least patch 2 to be accepted (by Greg) before applying
> 3 and 4.
That's fine with me.
> With regards to patch 1. Perhaps it would be best for Greg to take
> that with patch 2?
That's fine with me as well.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-30 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 0:31 [RFC/PATCH 5/6] ARM: shmobile: lager: Enable SCIF0 and SCIF1 serial ports in DT Laurent Pinchart
2014-04-30 0:59 ` Simon Horman
2014-04-30 1:02 ` Laurent Pinchart
2014-04-30 1:29 ` Simon Horman
2014-04-30 1:34 ` Simon Horman
2014-04-30 16:21 ` Laurent Pinchart
2014-04-30 16:23 ` Laurent Pinchart [this message]
2014-04-30 20:09 ` Geert Uytterhoeven
2014-04-30 21:44 ` Simon Horman
2014-04-30 21:47 ` Laurent Pinchart
2014-05-01 6:04 ` Simon Horman
2014-05-01 6:05 ` Simon Horman
2014-05-14 5:13 ` Simon Horman
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=3042921.YNIkMUtkoO@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.