All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeroen Hofstee <linux-arm@myspectrum.nl>
To: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Jeroen Hofstee <jeroen@myspectrum.nl>
Subject: Re: [PATCH] ARM: dts: AM35xx: fix system control module clocks
Date: Fri, 05 Jun 2015 10:01:50 +0200	[thread overview]
Message-ID: <5571576E.6020207@myspectrum.nl> (raw)
In-Reply-To: <alpine.DEB.2.02.1506011733180.14902@utopia.booyaka.com>

Hello Paul,

On 01-06-15 19:44, Paul Walmsley wrote:
> The best way to make this work IMHO would be for us not to accept any new
> feature addition patches as long as there are warnings reported in the
> test results.  The only real exception that I would foresee is if those
> warnings are due to something outside of our control, e.g., a crappy
> bootloader, as I suspect the USB_OTG initiator warnings are for the
> CM-T3517.
>

I doubt this is related to the bootloader. I have the suspicion that is 
actually
a bug in linux but only triggered depending on whether the ROMcode setup
the USB OTG or not. Here is some data to backup my statement:

Linux booting without USB_OTG error trap
md 480022F0 1
480022f0: 0000032f                               /...
md 48002580 1
48002580: 0f00b7a2                               ....

bit USBOTG_PHY_RESET is 0 -> out of reset


USB_OTG sees memory hole
md 480022F0 1
480022f0: 0000030f    ....
md 48002580 1
48002580: 0f00c71e    ....

USBOTG_PHY_RESET is 1 -> still in reset when booting linux.

Does that match with how your am3517 boards boot?

Regards,
Jeroen



WARNING: multiple messages have this Message-ID (diff)
From: linux-arm@myspectrum.nl (Jeroen Hofstee)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: AM35xx: fix system control module clocks
Date: Fri, 05 Jun 2015 10:01:50 +0200	[thread overview]
Message-ID: <5571576E.6020207@myspectrum.nl> (raw)
In-Reply-To: <alpine.DEB.2.02.1506011733180.14902@utopia.booyaka.com>

Hello Paul,

On 01-06-15 19:44, Paul Walmsley wrote:
> The best way to make this work IMHO would be for us not to accept any new
> feature addition patches as long as there are warnings reported in the
> test results.  The only real exception that I would foresee is if those
> warnings are due to something outside of our control, e.g., a crappy
> bootloader, as I suspect the USB_OTG initiator warnings are for the
> CM-T3517.
>

I doubt this is related to the bootloader. I have the suspicion that is 
actually
a bug in linux but only triggered depending on whether the ROMcode setup
the USB OTG or not. Here is some data to backup my statement:

Linux booting without USB_OTG error trap
md 480022F0 1
480022f0: 0000032f                               /...
md 48002580 1
48002580: 0f00b7a2                               ....

bit USBOTG_PHY_RESET is 0 -> out of reset


USB_OTG sees memory hole
md 480022F0 1
480022f0: 0000030f    ....
md 48002580 1
48002580: 0f00c71e    ....

USBOTG_PHY_RESET is 1 -> still in reset when booting linux.

Does that match with how your am3517 boards boot?

Regards,
Jeroen

  parent reply	other threads:[~2015-06-05  8:01 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30 15:50 OMAP baseline test results for v4.1-rc5 Paul Walmsley
2015-05-30 15:50 ` Paul Walmsley
2015-05-30 15:56 ` Jeroen Hofstee
2015-05-30 15:56   ` Jeroen Hofstee
2015-05-31 22:15   ` Jeroen Hofstee
2015-05-31 22:15     ` Jeroen Hofstee
2015-06-01  5:49     ` Paul Walmsley
2015-06-01  5:49       ` Paul Walmsley
2015-06-01 15:29       ` Tero Kristo
2015-06-01 15:29         ` Tero Kristo
2015-06-01 15:30       ` [PATCH] ARM: dts: AM35xx: fix system control module clocks Tero Kristo
2015-06-01 15:30         ` Tero Kristo
2015-06-01 16:56         ` Jeroen Hofstee
2015-06-01 16:56           ` Jeroen Hofstee
2015-06-01 17:31           ` Tony Lindgren
2015-06-01 17:31             ` Tony Lindgren
2015-06-01 17:44             ` Paul Walmsley
2015-06-01 17:44               ` Paul Walmsley
2015-06-01 18:04               ` Tony Lindgren
2015-06-01 18:04                 ` Tony Lindgren
2015-06-01 18:06                 ` Tony Lindgren
2015-06-01 18:06                   ` Tony Lindgren
2015-06-01 21:26                   ` Paul Walmsley
2015-06-01 21:26                     ` Paul Walmsley
2015-06-02  7:15                     ` Tero Kristo
2015-06-02  7:15                       ` Tero Kristo
2015-06-01 21:21                 ` Paul Walmsley
2015-06-01 21:21                   ` Paul Walmsley
2015-06-01 18:04               ` Tero Kristo
2015-06-01 18:04                 ` Tero Kristo
2015-06-05  8:01               ` Jeroen Hofstee [this message]
2015-06-05  8:01                 ` Jeroen Hofstee
2015-06-05  8:04                 ` Jeroen Hofstee
2015-06-05  8:04                   ` Jeroen Hofstee
2015-06-07  9:41                   ` Jeroen Hofstee
2015-06-07  9:41                     ` Jeroen Hofstee
2015-06-07 19:56                     ` Paul Walmsley
2015-06-07 19:56                       ` Paul Walmsley
2015-06-08  2:38                       ` Paul Walmsley
2015-06-08  2:38                         ` Paul Walmsley
2015-06-08 22:00                         ` Jeroen Hofstee
2015-06-08 22:00                           ` Jeroen Hofstee
2015-06-08 21:43                       ` Jeroen Hofstee
2015-06-08 21:43                         ` Jeroen Hofstee

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=5571576E.6020207@myspectrum.nl \
    --to=linux-arm@myspectrum.nl \
    --cc=jeroen@myspectrum.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /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.