From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Felipe Balbi" <balbi@ti.com>,
sre@debian.org, sre@ring0.de,
"kernel list" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>
Subject: Re: Nokia n900 problems in 3.18-rc1 (was Re: USB Ethernet gadget on Nokia n900)
Date: Wed, 29 Oct 2014 07:09:44 -0700 [thread overview]
Message-ID: <20141029140943.GX2542@atomide.com> (raw)
In-Reply-To: <20141029084637.GA30662@amd>
* Pavel Machek <pavel@ucw.cz> [141029 01:48]:
>
> Speaking of testing:
>
> I'm not sure what is omap_l3_smx neccessary for, but it does not work.
>
> [ 0.223297] omap_l3_smx omap_l3_smx.0: couldn't request debug irq
> [ 0.223419] omap_l3_smx: probe of omap_l3_smx.0 failed with error
> -22
Hmm this should be fixed to get interrupts about invalid bus
access.
> There is some fun in pinmuxing:
>
> [ 0.247131] irq: no irq domain found for /ocp/pinmux@48002030 !
> [ 0.248291] irq: no irq domain found for /ocp/pinmux@48002030 !
> ...
> [ 0.384826] omap_i2c 48070000.i2c: could not find pctldev for node
> /ocp/pinmux@48002030/pinmux_i\
> 2c1_pins, deferring probe
> [ 0.384918] platform 48070000.i2c: Driver omap_i2c requests probe
> deferral
> [ 0.385070] omap_i2c 48072000.i2c: could not find pctldev for node
> /ocp/pinmux@48002030/pinmux_i\
> 2c2_pins, deferring probe
> [ 0.385162] platform 48072000.i2c: Driver omap_i2c requests probe
> deferral
> [ 0.385284] omap_i2c 48060000.i2c: could not find pctldev for node
> /ocp/pinmux@48002030/pinmux_i\
> 2c3_pins, deferring probe
> [ 0.385375] platform 48060000.i2c: Driver omap_i2c requests probe
> deferral
These are related to deferred probe and should go away when we
make drivers/i2c/busses/i2c-omap.c to use regular module_init and
stop using subsys_initcall. But I think legacy booting still needs
it early, could be omap1 only nowadays though.
> And serial has some problems:
>
> [ 0.482208] of_get_named_gpiod_flags: can't parse 'rts-gpio'
> property of node '/ocp/serial@4806c\
> 000[0]'
> [ 0.482513] omap_uart 4806c000.serial: ttyO1 at MMIO 0x4806c000
> (irq = 223, base_baud = 3000000)\
> is a OMAP UART1
> [ 0.484588] of_get_named_gpiod_flags: can't parse 'rts-gpio'
> property of node '/ocp/serial@49020\
> 000[0]'
> [ 0.484771] omap_uart 49020000.serial: ttyO2 at MMIO 0x49020000
> (irq = 224, base_baud = 3000000)\
> is a OMAP UART2
I these come from the GPIO framework when booting with debug enabled.
> There's a lot of noise from probe defferal :-(. And it looks like mmc
> properties have some problems:
>
> [ 0.739349] of_get_named_gpiod_flags: can't parse 'wp-gpios'
> property of node '/ocp/mmc@4809c000\
> [0]'
> [ 0.740142] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator
> -517
> [ 0.740386] platform 4809c000.mmc: Driver omap_hsmmc requests probe
> deferral
> [ 0.740661] of_get_named_gpiod_flags: can't parse 'cd-gpios'
> property of node '/ocp/mmc@480b4000\
> [0]'
> [ 0.740692] of_get_named_gpiod_flags: can't parse 'wp-gpios'
> property of node '/ocp/mmc@480b4000\
> [0]'
These too. But yeah, I agree, let's try to patch away some of
the deferred probe noise.
> omapfb reports problems, but seems to work ok:
>
> [ 0.990386] omapfb omapfb: cannot parse default modes
> [ 1.004791] Console: switching to colour frame buffer device 100x30
> [ 1.073150] omapfb omapfb: using display 'lcd' mode 800x480
Tomi, is the default mode warning correct here?
Regards,
Tony
next prev parent reply other threads:[~2014-10-29 14:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 9:01 USB Ethernet gadget on Nokia n900 Pavel Machek
2014-10-19 10:07 ` Pavel Machek
2014-10-19 14:58 ` Pali Rohár
2014-10-19 20:50 ` Pavel Machek
2014-10-19 21:00 ` Pali Rohár
2014-10-19 22:30 ` Pavel Machek
2014-10-20 13:08 ` Pavel Machek
2014-10-20 16:45 ` Tony Lindgren
2014-10-20 22:03 ` Pavel Machek
2014-10-20 22:29 ` Tony Lindgren
2014-10-21 21:52 ` Pavel Machek
2014-10-19 15:24 ` Felipe Balbi
2014-10-19 19:19 ` Pavel Machek
2014-10-19 19:29 ` Pavel Machek
2014-10-20 21:35 ` Aaro Koskinen
2014-10-20 21:37 ` Aaro Koskinen
2014-10-20 22:42 ` Pavel Machek
2014-10-26 11:08 ` Pavel Machek
2014-10-26 11:12 ` Pali Rohár
2014-10-26 12:00 ` Pavel Machek
2014-10-26 21:17 ` Pavel Machek
2014-10-26 21:22 ` Pali Rohár
2014-10-26 21:55 ` Pavel Machek
2014-10-26 22:23 ` Pali Rohár
2014-10-27 19:52 ` Tony Lindgren
2014-10-27 22:31 ` Tony Lindgren
2014-10-28 22:04 ` Pavel Machek
2014-10-28 22:11 ` Tony Lindgren
2014-10-29 8:46 ` Nokia n900 problems in 3.18-rc1 (was Re: USB Ethernet gadget on Nokia n900) Pavel Machek
2014-10-29 14:09 ` Tony Lindgren [this message]
2014-10-29 14:18 ` Tomi Valkeinen
2014-10-29 21:34 ` Pavel Machek
2014-10-31 20:03 ` Pavel Machek
2014-10-31 20:30 ` Pali Rohár
2014-10-28 22:21 ` USB Ethernet gadget on Nokia n900 Pavel Machek
2014-10-28 22:26 ` Tony Lindgren
2015-07-06 13:24 ` Pali Rohár
2015-07-06 13:53 ` Tony Lindgren
2015-07-07 7:46 ` Pali Rohár
2015-07-07 11:46 ` Tony Lindgren
2016-01-19 20:58 ` Pali Rohár
2016-02-11 14:43 ` Pali Rohár
2016-02-11 14:50 ` Pali Rohár
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=20141029140943.GX2542@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--cc=tomi.valkeinen@ti.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 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).