Re: 3.18.1->3.19-rc2: In-band Error seen by MPU

["Peter Kümmel" <syntheticpp@gmx.net>]

Am 06.01.2015 um 12:52 schrieb Sebastian Reichel:
> Hi,
>
> On Tue, Jan 06, 2015 at 12:25:12PM +0100, Peter Kümmel wrote:
>> Am 05.01.2015 um 16:43 schrieb Felipe Balbi:
>>> Just booted AM335x with CONFIG_PREEMPT and haven't seen any problem.
>>> Perhaps this is something related to another OMAP3-only driver?
>>> Perhaps HSI/SSI ?
>>
>> I see a ssi error directly before the IN-Band error:
>>
>> [    0.339935] platform 48058000.ssi-controller: Cannot lookup hwmod 'ssi'
>> [    0.346893] In-band Error seen by MPU  at address 0
>> [    0.346923] ------------[ cut here ]------------
>
> mh I guess your board's dts included omap36xx.dtsi or omap34xx.dtsi.
> Since ssi controller is not available on DM3xxx/AM3xxx (AFAIK) it
> should be disabled for those SoCs:
>
> &ssi {
>      status = "disabled";
> };

Indeed, I include omap36xx.dtsi.
Disabling ssi removes ssi the error.
But the In-Band error is still there, so not related to ssi.


I also see these errors:

omap_hwmod: mcbsp2_sidetone using broken dt data from mcbsp
omap_hwmod: mcbsp3_sidetone using broken dt data from mcbsp
omap_hwmod: mcbsp2: cannot be enabled for reset (3)

and

irq: no irq domain found for /ocp/pinmux@48002030 !

Could these errors also be fixed by the dts.

Peter

>
>  From what I can see the following in-tree .dts files should be
> fixed, too:
>
> * am3517_mt_ventoux.dts
>    Currently includes "omap34xx.dtsi" instead of "am3517.dtsi".
>
> Apart from that the following boards seem to use omap36xx.dtsi
> include, but are actually DM37xx, so they should disable the
> ssi block:
>
> * omap3-igep.dtsi
> * omap3-lilly-a83x.dtsi
> * omap3-overo-storm.dtsi
>
> I will prepare a patch for that later.
>
> -- Sebastian
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html