From: Sudeep Holla <sudeep.holla@arm.com>
To: "Guenter Roeck" <linux@roeck-us.net>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
Date: Mon, 15 Feb 2016 18:39:53 +0000 [thread overview]
Message-ID: <56C21B79.8000408@arm.com> (raw)
In-Reply-To: <56C21518.5030606@roeck-us.net>
On 15/02/16 18:12, Guenter Roeck wrote:
[...]
>
> I added some debugging on top of your patch, and get:
>
> platform basic-mmio-gpio.1.auto: Device node exists
> [/smb/motherboard/iofpga@7,00000000/sysreg@00000/sys_led@08],
> of_driver_match_device() failed
> platform basic-mmio-gpio.1.auto: platform_match_id() succeeded
> platform basic-mmio-gpio.2.auto: Device node exists
> [/smb/motherboard/iofpga@7,00000000/sysreg@00000/sys_mci@48],
> of_driver_match_device() failed
> platform basic-mmio-gpio.2.auto: platform_match_id() succeeded
> platform basic-mmio-gpio.3.auto: Device node exists
> [/smb/motherboard/iofpga@7,00000000/sysreg@00000/sys_flash@4c],
> of_driver_match_device() failed
> platform basic-mmio-gpio.3.auto: platform_match_id() succeeded
>
> So it isn't the mmc driver failing to instantiate directly,
> but (I think) vexpress-sysreg.
>
That's correct, I could reproduce this issue and reported with similar
analysis earlier [1]
--
Regards,
Sudeep
[1] http://www.spinics.net/lists/arm-kernel/msg483107.html
WARNING: multiple messages have this Message-ID (diff)
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
Date: Mon, 15 Feb 2016 18:39:53 +0000 [thread overview]
Message-ID: <56C21B79.8000408@arm.com> (raw)
In-Reply-To: <56C21518.5030606@roeck-us.net>
On 15/02/16 18:12, Guenter Roeck wrote:
[...]
>
> I added some debugging on top of your patch, and get:
>
> platform basic-mmio-gpio.1.auto: Device node exists
> [/smb/motherboard/iofpga at 7,00000000/sysreg at 00000/sys_led at 08],
> of_driver_match_device() failed
> platform basic-mmio-gpio.1.auto: platform_match_id() succeeded
> platform basic-mmio-gpio.2.auto: Device node exists
> [/smb/motherboard/iofpga at 7,00000000/sysreg at 00000/sys_mci at 48],
> of_driver_match_device() failed
> platform basic-mmio-gpio.2.auto: platform_match_id() succeeded
> platform basic-mmio-gpio.3.auto: Device node exists
> [/smb/motherboard/iofpga at 7,00000000/sysreg at 00000/sys_flash at 4c],
> of_driver_match_device() failed
> platform basic-mmio-gpio.3.auto: platform_match_id() succeeded
>
> So it isn't the mmc driver failing to instantiate directly,
> but (I think) vexpress-sysreg.
>
That's correct, I could reproduce this issue and reported with similar
analysis earlier [1]
--
Regards,
Sudeep
[1] http://www.spinics.net/lists/arm-kernel/msg483107.html
next prev parent reply other threads:[~2016-02-15 18:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:50 arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' Guenter Roeck
2016-02-14 19:55 ` Uwe Kleine-König
2016-02-14 19:55 ` Uwe Kleine-König
2016-02-14 20:07 ` Russell King - ARM Linux
2016-02-14 20:07 ` Russell King - ARM Linux
2016-02-15 8:17 ` Uwe Kleine-König
2016-02-15 8:17 ` Uwe Kleine-König
2016-02-15 8:58 ` Russell King - ARM Linux
2016-02-15 8:58 ` Russell King - ARM Linux
2016-02-15 9:14 ` Uwe Kleine-König
2016-02-15 9:14 ` Uwe Kleine-König
2016-02-15 10:04 ` Russell King - ARM Linux
2016-02-15 10:04 ` Russell King - ARM Linux
2016-02-15 10:10 ` Uwe Kleine-König
2016-02-15 10:10 ` Uwe Kleine-König
2016-02-15 10:13 ` Russell King - ARM Linux
2016-02-15 10:13 ` Russell King - ARM Linux
2016-02-14 21:08 ` Guenter Roeck
2016-02-14 21:08 ` Guenter Roeck
2016-02-15 7:48 ` Uwe Kleine-König
2016-02-15 7:48 ` Uwe Kleine-König
2016-02-15 10:59 ` Uwe Kleine-König
2016-02-15 10:59 ` Uwe Kleine-König
2016-02-15 13:11 ` Robin Murphy
2016-02-15 13:11 ` Robin Murphy
2016-02-15 14:43 ` Russell King - ARM Linux
2016-02-15 14:43 ` Russell King - ARM Linux
2016-02-15 16:27 ` Uwe Kleine-König
2016-02-15 16:27 ` Uwe Kleine-König
2016-02-15 16:49 ` Greg Kroah-Hartman
2016-02-15 16:49 ` Greg Kroah-Hartman
2016-02-15 17:12 ` Uwe Kleine-König
2016-02-15 17:12 ` Uwe Kleine-König
2016-02-15 21:03 ` Greg Kroah-Hartman
2016-02-15 21:03 ` Greg Kroah-Hartman
2016-02-15 15:41 ` Guenter Roeck
2016-02-15 15:41 ` Guenter Roeck
2016-02-15 16:12 ` Russell King - ARM Linux
2016-02-15 16:12 ` Russell King - ARM Linux
2016-02-15 17:00 ` Uwe Kleine-König
2016-02-15 17:00 ` Uwe Kleine-König
2016-02-15 18:12 ` Guenter Roeck
2016-02-15 18:12 ` Guenter Roeck
2016-02-15 18:39 ` Sudeep Holla [this message]
2016-02-15 18:39 ` Sudeep Holla
2016-02-15 17:41 ` Sudeep Holla
2016-02-15 17:41 ` Sudeep Holla
2016-02-15 18:03 ` Russell King - ARM Linux
2016-02-15 18:03 ` Russell King - ARM Linux
2016-02-15 18:15 ` Sudeep Holla
2016-02-15 18:15 ` Sudeep Holla
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=56C21B79.8000408@arm.com \
--to=sudeep.holla@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=u.kleine-koenig@pengutronix.de \
/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.