From: Tero Kristo <t-kristo@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>
Cc: Jeroen Hofstee <linux-arm@myspectrum.nl>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: AM35xx: fix system control module clocks
Date: Mon, 1 Jun 2015 21:04:34 +0300 [thread overview]
Message-ID: <556C9EB2.6060208@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1506011733180.14902@utopia.booyaka.com>
On 06/01/2015 08:44 PM, Paul Walmsley wrote:
> On Mon, 1 Jun 2015, Tony Lindgren wrote:
>
>> * Jeroen Hofstee <linux-arm@myspectrum.nl> [150601 09:58]:
>>> On 01-06-15 17:30, Tero Kristo wrote:
>>>> New system control module layout for omap3 overlooked parts of the am35xx
>>>> configuration. Basically the am35xx clocks were not converted to use the
>>>> changed offsets, which caused weird boot warnings. The errors were not
>>>> fatal so far, so they were not caught earlier. Fixed by applying the
>>>> proper offsets for the AM35xx scm clocks.
>>>>
>>>> Fixes: b8845074cf ("ARM: dts: omap3: add minimal l4 bus layout with...")
>>>>
>>>> Signed-off-by: Tero Kristo <t-kristo@ti.com>
>>>> Reported-by: Jeroen Hofstee <linux-arm@myspectrum.nl>
>>>> Cc: Paul Walmsley <paul@pwsan.com>
>>>> Cc: Tony Lindgren <tony@atomide.com>
>>>> ---
>>>> arch/arm/boot/dts/am35xx-clocks.dtsi | 14 +++++++-------
>>>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>> With this patch the error interrupt / stack dumps are no longer present.
>>>
>>> Thanks,
>>>
>>> Tested-by: Jeroen Hofstee <jeroen@myspectrum.nl>
>>
>> Thanks, I'm suprised this was not caught earlier with all the automated
>> boot testing going on?
>
> At least speaking in terms the testbed results that I post, the warnings
> get reported. But not many people seem to act on them. (Jeroen is a
> pleasant exception.)
>
> See for example the "Build warnings from toolchain", "Kernel warnings
> during boot to userspace", "Kernel warnings during PM test", and "Obsolete
> Kconfig symbols" sections here:
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc6/20150601012139/README.txt
>
>
> 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 added some extra logic into my test setup today for detecting this.
Previously the dumps were pretty much hidden as there are existing dumps
so I kind of ignored the new ones semi-blindly. >.<
-Tero
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: AM35xx: fix system control module clocks
Date: Mon, 1 Jun 2015 21:04:34 +0300 [thread overview]
Message-ID: <556C9EB2.6060208@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1506011733180.14902@utopia.booyaka.com>
On 06/01/2015 08:44 PM, Paul Walmsley wrote:
> On Mon, 1 Jun 2015, Tony Lindgren wrote:
>
>> * Jeroen Hofstee <linux-arm@myspectrum.nl> [150601 09:58]:
>>> On 01-06-15 17:30, Tero Kristo wrote:
>>>> New system control module layout for omap3 overlooked parts of the am35xx
>>>> configuration. Basically the am35xx clocks were not converted to use the
>>>> changed offsets, which caused weird boot warnings. The errors were not
>>>> fatal so far, so they were not caught earlier. Fixed by applying the
>>>> proper offsets for the AM35xx scm clocks.
>>>>
>>>> Fixes: b8845074cf ("ARM: dts: omap3: add minimal l4 bus layout with...")
>>>>
>>>> Signed-off-by: Tero Kristo <t-kristo@ti.com>
>>>> Reported-by: Jeroen Hofstee <linux-arm@myspectrum.nl>
>>>> Cc: Paul Walmsley <paul@pwsan.com>
>>>> Cc: Tony Lindgren <tony@atomide.com>
>>>> ---
>>>> arch/arm/boot/dts/am35xx-clocks.dtsi | 14 +++++++-------
>>>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>> With this patch the error interrupt / stack dumps are no longer present.
>>>
>>> Thanks,
>>>
>>> Tested-by: Jeroen Hofstee <jeroen@myspectrum.nl>
>>
>> Thanks, I'm suprised this was not caught earlier with all the automated
>> boot testing going on?
>
> At least speaking in terms the testbed results that I post, the warnings
> get reported. But not many people seem to act on them. (Jeroen is a
> pleasant exception.)
>
> See for example the "Build warnings from toolchain", "Kernel warnings
> during boot to userspace", "Kernel warnings during PM test", and "Obsolete
> Kconfig symbols" sections here:
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc6/20150601012139/README.txt
>
>
> 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 added some extra logic into my test setup today for detecting this.
Previously the dumps were pretty much hidden as there are existing dumps
so I kind of ignored the new ones semi-blindly. >.<
-Tero
next prev parent reply other threads:[~2015-06-01 18:04 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 [this message]
2015-06-01 18:04 ` Tero Kristo
2015-06-05 8:01 ` Jeroen Hofstee
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=556C9EB2.6060208@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm@myspectrum.nl \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.