From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: shmobile: koelsch: Add support HSCIF1
Date: Fri, 13 Jun 2014 07:43:07 +0000 [thread overview]
Message-ID: <20140613074306.GA15286@verge.net.au> (raw)
In-Reply-To: <10020827.IyD6srEo7g@avalon>
On Fri, Jun 13, 2014 at 09:01:27AM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Tuesday 10 June 2014 16:00:48 Simon Horman wrote:
> > On Tue, Jun 10, 2014 at 01:14:27PM +0900, Magnus Damm wrote:
> > > On Tue, Jun 10, 2014 at 11:34 AM, Nobuhiro Iwamatsu wrote:
> > > > Koelsch can use HSCIF1 insetead of SCIF1 as serial port. But if we want
> > > > to use, we will need to disable the GPIO key and remodeling of the
> > > > board. Therefore status of hscif1 does not set the "okay".
> > > >
> > > > Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> > > > ---
> > > >
> > > > V2: Remove hscif1_clk from renesas,groups. This pin does not use.
> > >
> > > Thanks for updating the patch. This looks fine to me.
> > >
> > > Acked-by: Magnus Damm <damm+renesas@opensource.se>
> >
> > Thanks, I will queue this up.
>
> Sorry for the late reply, but I have some doubts about this. The HRX0 and
> HTX0 signals are connected to push buttons and used as GPIOs. Beside,
> they're not routed to serial port transceiver. If we want to use HSCIF0
> on those pins on Koelsch and extension board must be connected to the
> EXIO C connector, and two resistors and two capacitors should be
> unsoldered. I thus don't think the Koeslch DT should contain pinmux data
> for the HSCIF0 device. If an extension board is used and HSCIF0 needed,
> then the DT file for the extension board should define pinmuxing for the
> serial port.
If you would like me to revert this patch I am happy to consider doing so.
next prev parent reply other threads:[~2014-06-13 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 2:34 [PATCH v2] ARM: shmobile: koelsch: Add support HSCIF1 Nobuhiro Iwamatsu
2014-06-10 4:14 ` Magnus Damm
2014-06-10 7:00 ` Simon Horman
2014-06-13 7:01 ` Laurent Pinchart
2014-06-13 7:43 ` Simon Horman [this message]
2014-06-13 10:49 ` Laurent Pinchart
2014-06-13 11:16 ` Geert Uytterhoeven
2014-06-13 13:24 ` Laurent Pinchart
2014-06-13 14:21 ` Geert Uytterhoeven
2014-06-16 0:09 ` 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=20140613074306.GA15286@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).