arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Russell King - ARM Linux <hidden>
Date: 2016-02-15 10:14:02
Also in:
linux-next, lkml
Possibly related (same subject, not in this thread)
- 2016-02-15 · Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
- 2016-02-15 · Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' · Sudeep Holla <hidden>
- 2016-02-15 · Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' · Sudeep Holla <hidden>
- 2016-02-15 · Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' · Guenter Roeck <linux@roeck-us.net>
- 2016-02-15 · Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles' · Russell King - ARM Linux <hidden>
On Mon, Feb 15, 2016 at 11:10:14AM +0100, Uwe Kleine-K?nig wrote:
Hello Russell, On Mon, Feb 15, 2016 at 10:04:15AM +0000, Russell King - ARM Linux wrote:quoted
On Mon, Feb 15, 2016 at 10:14:06AM +0100, Uwe Kleine-K?nig wrote:quoted
On Mon, Feb 15, 2016 at 08:58:18AM +0000, Russell King - ARM Linux wrote:quoted
On Mon, Feb 15, 2016 at 09:17:50AM +0100, Uwe Kleine-K?nig wrote:quoted
On Sun, Feb 14, 2016 at 08:07:55PM +0000, Russell King - ARM Linux wrote:quoted
On Sun, Feb 14, 2016 at 08:55:01PM +0100, Uwe Kleine-K?nig wrote:quoted
So the unexpected abnormality here is that even though this device is instantiated by dt, the driver doesn't provide any compatibles. Either my expectation is wrong, then 67d02a1bbb33455 should be revertedYour expectation is wrong. AMBA primecell devices have hardware IDs and are matched to their drivers by those IDs. Just like PCI.pci devices don't appear in dt, do they? I don't see the connection between amba devices and platform devices, see my other mail in this thread for some more details.They both have hardware IDs, and they are both matched via those hardware IDs.I changed platform_match which is about matching by dt compatible, acpi and/or device name. I don't see how this can affect an amba device given they match to a driver by a hardware id.quoted
Your change has introduced a regression and is therefore wrong.I'd like to understand though why and how my commit is wrong to be able to fix it instead of getting it reverted.I don't have the commit, and I haven't seen the patch so I can't comment further, sorry.It's in -next. For a quick look: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67d02a1bbb33455
Well, if that's only touching the platform device matching, it can't have any effect on AMBA bus matching, which uses completely different code. The AMBA bus code is entirely separate from platform devices. -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.