[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56C21B79.8000408@arm.com>
Date: Mon, 15 Feb 2016 18:39:53 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Guenter Roeck <linux@...ck-us.net>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: Sudeep Holla <sudeep.holla@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: arm qemu test failures due to 'driver-core: platform: probe
of-devices only using list of compatibles'
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@...00/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@...00/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@...00/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
Powered by blists - more mailing lists