linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: dts: imx25-pinfunc: add all UART mux modes
Date: Tue, 19 Apr 2016 09:30:23 +0200	[thread overview]
Message-ID: <20160419073023.GH10108@pengutronix.de> (raw)
In-Reply-To: <20160330131207.GK28207@tiger>

Hey Shawn,

On Wed, Mar 30, 2016 at 09:12:08PM +0800, Shawn Guo wrote:
> On Wed, Mar 09, 2016 at 08:44:33PM +0100, Uwe Kleine-K?nig wrote:
> > Apart from a few additions this also contains two fixes where the daisy
> > chain input selection register was missing. Moreover dropped _MUX from
> > some pins for consistency.
> > 
> > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> 
> Applied both, thanks.

I think I found yet another problem that involves the SION bit. On the
same hardware where I debugged that UART problem we also had an issue
that resulted in messages like:

[  108.939397] usb 1-1: new full-speed USB device number 6 using ci_hdrc
[  109.154390] usb 1-1: device descriptor read/64, error -71
[  109.469404] usb 1-1: device descriptor read/64, error -71
[  109.689385] usb 1-1: new full-speed USB device number 7 using ci_hdrc
[  109.904383] usb 1-1: device descriptor read/64, error -71
[  110.219376] usb 1-1: device descriptor read/64, error -71
[  110.439396] usb 1-1: new full-speed USB device number 8 using ci_hdrc
[  110.919379] usb 1-1: device not accepting address 8, error -71
[  111.034396] usb 1-1: new full-speed USB device number 9 using ci_hdrc
[  111.514384] usb 1-1: device not accepting address 9, error -71
[  111.522547] usb usb1-port1: unable to enumerate USB device

whenever the spi FRAM is accessed. Now I noticed that the involved
pin/functions (i.e. MX25_PAD_CSI_D2__CSPI3_MOSI,
MX25_PAD_CSI_D3__CSPI3_MISO, MX25_PAD_CSI_D6__GPIO_1_31 for CS) also
have the SION bit set and these have also an USBOTG function (which is
not defined in imx25-pinfunc.h, so you have to check the reference
manual).

Assuming that removing the SION bits fixes that issue (this is still to
be tested) I wonder if we should remove all SION bits.

What do you think?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2016-04-19  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 10:00 [PATCH] ARM: dts: imx25-pinfunc: add MX25_PAD_KPP_ROW3__UART1_RI Uwe Kleine-König
2016-03-04 12:33 ` Lothar Waßmann
2016-03-04 13:25   ` about the input paths in i.MX25 pinmuxing Uwe Kleine-König
2016-03-08 11:18 ` [PATCH 1/2] ARM: dts: imx25-pinfunc: add all UART mux modes Uwe Kleine-König
2016-03-08 11:18   ` [PATCH 2/2] ARM: dts: imx25-pinfunc: remove SION for pins with an UART handshaking input mode Uwe Kleine-König
2016-03-09 19:44 ` [PATCH v2 1/2] ARM: dts: imx25-pinfunc: add all UART mux modes Uwe Kleine-König
2016-03-09 19:44   ` [PATCH v2 2/2] ARM: dts: imx25-pinfunc: remove SION for pins with an UART handshaking input mode Uwe Kleine-König
2016-03-30 13:12   ` [PATCH v2 1/2] ARM: dts: imx25-pinfunc: add all UART mux modes Shawn Guo
2016-04-19  7:30     ` Uwe Kleine-König [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=20160419073023.GH10108@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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).