From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: shmobile: koelsch: Add support HSCIF1
Date: Fri, 13 Jun 2014 13:24:12 +0000 [thread overview]
Message-ID: <1751840.oCdYe48VRu@avalon> (raw)
In-Reply-To: <CAMuHMdUd=E=TcSTPwy0xbpAcZH+voiEkjND=qzdSzG_zKdPe9g@mail.gmail.com>
Hi Geert,
On Friday 13 June 2014 13:16:34 Geert Uytterhoeven wrote:
> On Fri, Jun 13, 2014 at 12:49 PM, Laurent Pinchart wrote:
> > On Friday 13 June 2014 16:43:07 Simon Horman wrote:
> >> On Fri, Jun 13, 2014 at 09:01:27AM +0200, Laurent Pinchart wrote:
> >> > 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.
>
> You mean HRX1, HTX1, and HSCIF1?
*sigh*... :-)
> HTX1 and HRX1 can be connected to the DEBUG1 transceiver by stuffing
> zero-Ohm resisters to R834 and R835.
>
> About your comment about the resistors and capacitors, which applies to
> both HSCIF0 and HSCIF1: probably the serial port will still work if
> these are present.
With a 4.7µF capacitive load on the transmission line, assuming a drive
strength of 40mA (which is pretty high), switching between 0V and 3.3V takes
388µs, corresponding to 2579 Hz. You'll have to reduce the baud rate :-)
> >> If you would like me to revert this patch I am happy to consider doing
> >> so.
> >
> > That's one option, but I'd like to get feedback on my point of view before
> > reverting it. Who knows, I might be wrong ;-)
>
> Nevertheless, I agree with Laurent.
>
> HSCIF1 (and HSCIF0) cannot be used on the Koelsch board as-is, hence they
> should not be present in the plain Koelsch DTS. They should be put in
> an overlay DTS instead.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: shmobile: koelsch: Add support HSCIF1
Date: Fri, 13 Jun 2014 15:24:12 +0200 [thread overview]
Message-ID: <1751840.oCdYe48VRu@avalon> (raw)
In-Reply-To: <CAMuHMdUd=E=TcSTPwy0xbpAcZH+voiEkjND=qzdSzG_zKdPe9g@mail.gmail.com>
Hi Geert,
On Friday 13 June 2014 13:16:34 Geert Uytterhoeven wrote:
> On Fri, Jun 13, 2014 at 12:49 PM, Laurent Pinchart wrote:
> > On Friday 13 June 2014 16:43:07 Simon Horman wrote:
> >> On Fri, Jun 13, 2014 at 09:01:27AM +0200, Laurent Pinchart wrote:
> >> > 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.
>
> You mean HRX1, HTX1, and HSCIF1?
*sigh*... :-)
> HTX1 and HRX1 can be connected to the DEBUG1 transceiver by stuffing
> zero-Ohm resisters to R834 and R835.
>
> About your comment about the resistors and capacitors, which applies to
> both HSCIF0 and HSCIF1: probably the serial port will still work if
> these are present.
With a 4.7?F capacitive load on the transmission line, assuming a drive
strength of 40mA (which is pretty high), switching between 0V and 3.3V takes
388?s, corresponding to 2579 Hz. You'll have to reduce the baud rate :-)
> >> If you would like me to revert this patch I am happy to consider doing
> >> so.
> >
> > That's one option, but I'd like to get feedback on my point of view before
> > reverting it. Who knows, I might be wrong ;-)
>
> Nevertheless, I agree with Laurent.
>
> HSCIF1 (and HSCIF0) cannot be used on the Koelsch board as-is, hence they
> should not be present in the plain Koelsch DTS. They should be put in
> an overlay DTS instead.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-06-13 13:24 UTC|newest]
Thread overview: 20+ 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 2:34 ` Nobuhiro Iwamatsu
2014-06-10 4:14 ` Magnus Damm
2014-06-10 4:14 ` Magnus Damm
2014-06-10 7:00 ` Simon Horman
2014-06-10 7:00 ` Simon Horman
2014-06-13 7:01 ` Laurent Pinchart
2014-06-13 7:01 ` Laurent Pinchart
2014-06-13 7:43 ` Simon Horman
2014-06-13 7:43 ` Simon Horman
2014-06-13 10:49 ` Laurent Pinchart
2014-06-13 10:49 ` Laurent Pinchart
2014-06-13 11:16 ` Geert Uytterhoeven
2014-06-13 11:16 ` Geert Uytterhoeven
2014-06-13 13:24 ` Laurent Pinchart [this message]
2014-06-13 13:24 ` Laurent Pinchart
2014-06-13 14:21 ` Geert Uytterhoeven
2014-06-13 14:21 ` Geert Uytterhoeven
2014-06-16 0:09 ` Simon Horman
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=1751840.oCdYe48VRu@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 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.