[PATCH v6 20/22] driver core: Allow deferring probes until late init

Add a field to struct device that instructs the device-driver core to defer the probe of this device until the late_initcall level. By letting all built-in drivers to register before starting to probe, we can avoid any deferred probes by probing dependencies on demand. Signed-off-by: Tomeu

[PATCH v6 14/22] usb: phy: Probe phy devices on demand

When looking up a phy through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 21/22] driver core: Start processing deferred probes earlier

in device_initcall_sync we increase the chances that the initcalls mentioned before will find the devices they depend on to have already probed. Signed-off-by: Tomeu Vizoso --- Changes in v4: - Start processing deferred probes in device_initcall_sync drivers/base/dd.c | 4 ++-- 1 file changed, 2

[PATCH v6 16/22] pinctrl: Probe pinctrl devices on demand

-by: Tomeu Vizoso --- drivers/pinctrl/devicetree.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pinctrl/devicetree.c b/drivers/pinctrl/devicetree.c index fe04e748dfe4..f5340b8e1dbe 100644 --- a/drivers/pinctrl/devicetree.c +++ b/drivers/pinctrl/devicetree.c @@ -18,6 +18,7

[PATCH v6 02/22] ARM: amba: Move reading of periphid to amba_match()

. Signed-off-by: Tomeu Vizoso --- Changes in v6: - Drop bus_type.pre_probe and read the periphid in match() instead as suggested by Alan Stern. Changes in v4: - Added bus.pre_probe callback so the probes of Primecell devices can be deferred if their device IDs cannot be yet read because of the clock

[PATCH v6 17/22] phy: core: Probe phy providers on demand

-by: Tomeu Vizoso --- drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index fc48fac003a6..94e90031d7f3 100644 --- a/drivers/phy/phy-core.c +++ b/drivers/phy/phy-core.c @@ -18,6 +18,7 @@ #include #include #include

[PATCH v6 19/22] power-supply: Probe power supplies on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/power/power_supply_core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/power/power_supply_core.c b/drivers/power/power_supply_core.c index 456987c88baa..80bc89f4ae89 100644 --- a/drivers/power/power_supply_core.c +++ b/d

[PATCH v6 13/22] backlight: Probe backlight devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/video/backlight/backlight.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c index bddc8b17a4d8..9bcdc16eacdf 100644 --- a/drivers/video/backlight/backl

[PATCH v6 03/22] of/platform: Point to struct device from device node

When adding platform and AMBA devices, set the device node's device member to point to it. This speeds lookups considerably and is safe because we only create one of these devices for any given device node. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5:

[PATCH v6 01/22] driver core: handle -EPROBE_DEFER from bus_type.match()

because a clock driver hasn't probed yet). Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/base/dd.c | 24 ++-- include/linux/device.h | 2 +- 2 files changed, 23 insertions(+), 3 deletions(-) diff --git a/drivers/base/dd.c b/drivers/base/dd.c

[PATCH v6 08/22] regulator: core: Probe regulators on demand

When looking up a regulator through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 07/22] regulator: core: Remove regulator_list

As we are already registering a device with regulator_class for each regulator device, regulator_list is redundant and can be replaced with calls to class_find_device() and class_for_each_device(). Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v6: - Merge c

Re: [PATCH v5 07/23] regulator: core: Remove regulator_list

On 19 September 2015 at 17:01, Mark Brown <broo...@kernel.org> wrote: > On Thu, Sep 17, 2015 at 02:57:01PM +0200, Tomeu Vizoso wrote: >> As we are already registering a device with regulator_class for each >> regulator device, regulator_list is redundant and can be r

[PATCH v6 09/22] drm: Probe panels on demand

When looking up a panel through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 10/22] drm/tegra: Probe dpaux devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/gpu/drm/tegra/dpaux.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/tegra/dpaux.c b/drivers/gpu/drm/tegra/dpaux.c index 6aecb6647313..40bdc2a98548 100644 --- a/drivers/gpu/drm/tegra/dpaux.c +++ b/drivers/gpu/drm

[PATCH v6 12/22] pwm: Probe PWM chip devices on demand

When looking up a PWM chip through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 11/22] i2c: core: Probe i2c adapters and devices on demand

-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/i2c/i2c-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c index 5f89f1e3c2f2..02da3acbbd35 100644 --- a/drivers/i2c/i2c-core.c +++ b/drivers/i2c/i2c-core.c @@ -1413,6 +

Re: [PATCH v5 07/23] regulator: core: Remove regulator_list

On 20 September 2015 at 22:32, Russell King - ARM Linux <li...@arm.linux.org.uk> wrote: > On Sat, Sep 19, 2015 at 08:01:29AM -0700, Mark Brown wrote: >> On Thu, Sep 17, 2015 at 02:57:01PM +0200, Tomeu Vizoso wrote: >> > As we are already registering a device with

[PATCH v6 04/22] of: add function to allow probing a device from a OF node

to be probed as well (when they get registered). Subsystems can use this when looking up resources for drivers, to reduce the chances of deferred probes because of the probing order of devices. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: - Move the assignment to devic

[PATCH v6 05/22] gpio: Probe GPIO drivers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/gpio/gpiolib-of.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index fa6e3c8823d6..9a439dab7a87 100644 --- a/drivers/gpio/gpiolib-of.c +++ b/drivers/gpio/gpiolib-of.c @@

[PATCH v6 06/22] gpio: Probe pinctrl devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/gpio/gpiolib-of.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index 9a439dab7a87..05da9a56608d 100644 --- a/drivers/gpio/gpiolib-of.c +++ b/drivers/gpio/gpiolib-of.c @@

[PATCH v6 22/22] of/platform: Defer probes of registered devices

registered already. This allows us to prevent deferred probes by probing dependencies on demand. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v4: - Also defer probes of AMBA devices registered from the DT as they can also request resources. drivers/of/platform.

[PATCH v6 18/22] dma: of: Probe DMA controllers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/dma/of-dma.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/dma/of-dma.c b/drivers/dma/of-dma.c index 1e1f2986eba8..e899832f7df3 100644 --- a/drivers/dma/of-dma.c +++ b/drivers/dma/of-dma.c @@ -16,6 +16,7 @@ #i

[PATCH v6 0/22] On-demand device probing

could be used for machines with ACPI, but I haven't been able to find one that had to defer its probes because of the device probe order. Tomeu Vizoso (22): driver core: handle -EPROBE_DEFER from bus_type.match() ARM: amba: Move reading of periphid to amba_match() of/platform: Point to struct devic

[PATCH v6 15/22] clk: Probe clk providers on demand

When looking up a clock through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 14/22] usb: phy: Probe phy devices on demand

When looking up a phy through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 21/22] driver core: Start processing deferred probes earlier

in device_initcall_sync we increase the chances that the initcalls mentioned before will find the devices they depend on to have already probed. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v4: - Start processing deferred probes in device_initcall_sync drivers/bas

[PATCH v6 20/22] driver core: Allow deferring probes until late init

Add a field to struct device that instructs the device-driver core to defer the probe of this device until the late_initcall level. By letting all built-in drivers to register before starting to probe, we can avoid any deferred probes by probing dependencies on demand. Signed-off-by: Tomeu

[PATCH v6 17/22] phy: core: Probe phy providers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index fc48fac003a6..94e90031d7f3 100644 --- a/drivers/phy/phy-core.c +++ b/drivers/phy/phy-core.c @@ -18,6 +18,7 @@ #i

[PATCH v6 02/22] ARM: amba: Move reading of periphid to amba_match()

. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v6: - Drop bus_type.pre_probe and read the periphid in match() instead as suggested by Alan Stern. Changes in v4: - Added bus.pre_probe callback so the probes of Primecell devices can be deferred if their device IDs

[PATCH v6 16/22] pinctrl: Probe pinctrl devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/pinctrl/devicetree.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pinctrl/devicetree.c b/drivers/pinctrl/devicetree.c index fe04e748dfe4..f5340b8e1dbe 100644 --- a/drivers/pinctrl/devicetree.c +++ b/drivers/p

Re: [PATCH v5 01/23] driver core: Add pre_probe callback to bus_type

On 17 September 2015 at 17:52, Alan Stern wrote: > On Thu, 17 Sep 2015, Tomeu Vizoso wrote: > >> Some buses (eg. AMBA) need access to some HW resources (it may need a >> clock to be enabled so a device ID can be read) before a device can be >> matched to a driver. >

Re: [PATCH v5 01/23] driver core: Add pre_probe callback to bus_type

On 17 September 2015 at 17:52, Alan Stern <st...@rowland.harvard.edu> wrote: > On Thu, 17 Sep 2015, Tomeu Vizoso wrote: > >> Some buses (eg. AMBA) need access to some HW resources (it may need a >> clock to be enabled so a device ID can be read) before a device can b

[PATCH v5 04/23] of: add function to allow probing a device from a OF node

to be probed as well (when they get registered). Subsystems can use this when looking up resources for drivers, to reduce the chances of deferred probes because of the probing order of devices. Signed-off-by: Tomeu Vizoso --- Changes in v5: - Move the assignment to device_node->device for AMBA devi

[PATCH v5 05/23] gpio: Probe GPIO drivers on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpio/gpiolib-of.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index fa6e3c8823d6..9a439dab7a87 100644 --- a/drivers/gpio

[PATCH v5 02/23] ARM: amba: Move reading of periphid to pre_probe()

requirements. Signed-off-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: - Added bus.pre_probe callback so the probes of Primecell devices can be deferred if their device IDs cannot be yet read because of the clock driver not having probed when they are registered. Maybe this goes overboard

[PATCH v5 01/23] driver core: Add pre_probe callback to bus_type

of the resources needed are missing. This gives us more flexibility when setting the order in which devices are probed because the resources needed to get the matching information don't need to be available by the time that the bus devices are registered. Signed-off-by: Tomeu Vizoso --- Changes

[PATCH v5 07/23] regulator: core: Remove regulator_list

As we are already registering a device with regulator_class for each regulator device, regulator_list is redundant and can be replaced with calls to class_find_device() and class_for_each_device(). Signed-off-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None

[PATCH v5 08/23] regulator: core: Drop redundant locking

reg_fixed_voltage_probe regulator_register Signed-off-by: Tomeu Vizoso --- Changes in v5: - Use regulator_class' klist of devices instead of regulator_list to store and lookup regulator devices. Changes in v4: - Take a reference

[PATCH v5 14/23] backlight: Probe backlight devices on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/video/backlight/backlight.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c index bddc8b17a4d8

[PATCH v5 11/23] drm/tegra: Probe dpaux devices on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpu/drm/tegra/dpaux.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/tegra/dpaux.c b/drivers/gpu/drm/tegra/dpaux.c index 6aecb6647313..40bdc2a98548 100644 --- a/drivers

[PATCH v5 10/23] drm: Probe panels on demand

When looking up a panel through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 06/23] gpio: Probe pinctrl devices on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpio/gpiolib-of.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index 9a439dab7a87..05da9a56608d 100644 --- a/drivers/gpio

[PATCH v5 13/23] pwm: Probe PWM chip devices on demand

When looking up a PWM chip through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 12/23] i2c: core: Probe i2c adapters and devices on demand

-off-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/i2c/i2c-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c index 5f89f1e3c2f2..02da3acbbd35 100644 --- a/drivers/i2c/i2c

[PATCH v5 15/23] usb: phy: Probe phy devices on demand

When looking up a phy through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 16/23] clk: Probe clk providers on demand

When looking up a clock through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 18/23] phy: core: Probe phy providers on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index fc48fac003a6..94e90031d7f3 100644 --- a/drivers/phy/phy-core.c +++ b

[PATCH v5 17/23] pinctrl: Probe pinctrl devices on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/pinctrl/devicetree.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pinctrl/devicetree.c b/drivers/pinctrl/devicetree.c index fe04e748dfe4..f5340b8e1dbe 100644 --- a/drivers

[PATCH v5 22/23] driver core: Start processing deferred probes earlier

in device_initcall_sync we increase the chances that the initcalls mentioned before will find the devices they depend on to have already probed. Signed-off-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: - Start processing deferred probes in device_initcall_sync Changes in v3: None Changes

[PATCH v5 21/23] driver core: Allow deferring probes until late init

Add a field to struct device that instructs the device-driver core to defer the probe of this device until the late_initcall level. By letting all built-in drivers to register before starting to probe, we can avoid any deferred probes by probing dependencies on demand. Signed-off-by: Tomeu

[PATCH v5 19/23] dma: of: Probe DMA controllers on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/dma/of-dma.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/dma/of-dma.c b/drivers/dma/of-dma.c index 1e1f2986eba8..e899832f7df3 100644 --- a/drivers/dma/of-dma.c +++ b

[PATCH v5 09/23] regulator: core: Probe regulators on demand

When looking up a regulator through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 20/23] power-supply: Probe power supplies on demand

-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/power/power_supply_core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/power/power_supply_core.c b/drivers/power/power_supply_core.c index 456987c88baa..80bc89f4ae89 100644

[PATCH v5 23/23] of/platform: Defer probes of registered devices

registered already. This allows us to prevent deferred probes by probing dependencies on demand. Signed-off-by: Tomeu Vizoso --- Changes in v5: None Changes in v4: - Also defer probes of AMBA devices registered from the DT as they can also request resources. Changes in v3: None Changes in v2: None

[PATCH v5 0/23] On-demand device probing

ACPI, but I haven't been able to find one that had to defer its probes because of the device probe order. - Avoid unlocking the regulator device's mutex if we don't have a device Changes in v2: - Acquire regulator device lock before returning from regulator_dev_lookup() Tomeu Vizoso (23): dri

[PATCH v5 03/23] of/platform: Point to struct device from device node

When adding platform and AMBA devices, set the device node's device member to point to it. This speeds lookups considerably and is safe because we only create one of these devices for any given device node. Signed-off-by: Tomeu Vizoso --- Changes in v5: - Set the pointer to struct device also

[PATCH RESEND] ARM: dts: Move display-timings node from fimd to dp

From: Sean Paul This patch moves the display-timings node from fimd to dp to reflect the device tree bindings change. Signed-off-by: Sean Paul [tomeu.viz...@collabora.com: Rebased] Signed-off-by: Tomeu Vizoso --- Hi, looks like a long time ago the bindings were changed and the DTs

Re: [linux-next] oops in ip_route_input_noref

On 17 September 2015 at 01:47, Sergey Senozhatsky wrote: > On (09/16/15 07:07), David Ahern wrote: >> Hi Sergey: >> > > Hi, > > sorry for long reply. Baremetal. So grabbing the backtrace is > a bit complicated. But it looks very close to what Richard Alpe > has posted. Hi, in this boot log you

Re: [linux-next] oops in ip_route_input_noref

On 17 September 2015 at 01:47, Sergey Senozhatsky wrote: > On (09/16/15 07:07), David Ahern wrote: >> Hi Sergey: >> > > Hi, > > sorry for long reply. Baremetal. So grabbing the backtrace is > a bit complicated. But it looks very close to what Richard Alpe > has

[PATCH RESEND] ARM: dts: Move display-timings node from fimd to dp

From: Sean Paul <seanp...@chromium.org> This patch moves the display-timings node from fimd to dp to reflect the device tree bindings change. Signed-off-by: Sean Paul <seanp...@chromium.org> [tomeu.viz...@collabora.com: Rebased] Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabor

[PATCH v5 0/23] On-demand device probing

ACPI, but I haven't been able to find one that had to defer its probes because of the device probe order. - Avoid unlocking the regulator device's mutex if we don't have a device Changes in v2: - Acquire regulator device lock before returning from regulator_dev_lookup() Tomeu Vizoso (23): dri

[PATCH v5 03/23] of/platform: Point to struct device from device node

When adding platform and AMBA devices, set the device node's device member to point to it. This speeds lookups considerably and is safe because we only create one of these devices for any given device node. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5:

[PATCH v5 20/23] power-supply: Probe power supplies on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/power/power_supply_core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/power/power_supply_core.c b/drivers/power/power_supply_core.c

[PATCH v5 09/23] regulator: core: Probe regulators on demand

When looking up a regulator through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 19/23] dma: of: Probe DMA controllers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/dma/of-dma.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/dma/of-dma.c b/drivers/dma/of-dma.c index 1e1f2986eba8..e899832f7df3

[PATCH v5 18/23] phy: core: Probe phy providers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index fc48fac003a6..94e90031d7f3

[PATCH v5 16/23] clk: Probe clk providers on demand

When looking up a clock through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 10/23] drm: Probe panels on demand

When looking up a panel through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 07/23] regulator: core: Remove regulator_list

As we are already registering a device with regulator_class for each regulator device, regulator_list is redundant and can be replaced with calls to class_find_device() and class_for_each_device(). Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes

[PATCH v5 08/23] regulator: core: Drop redundant locking

reg_fixed_voltage_probe regulator_register Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: - Use regulator_class' klist of devices instead of regulator_list to store and lookup regulator d

[PATCH v5 06/23] gpio: Probe pinctrl devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpio/gpiolib-of.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index 9a439dab7a87..05da9a

[PATCH v5 11/23] drm/tegra: Probe dpaux devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpu/drm/tegra/dpaux.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/tegra/dpaux.c b/drivers/gpu/drm/tegra/dpaux.c index 6aecb6

[PATCH v5 14/23] backlight: Probe backlight devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/video/backlight/backlight.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backl

[PATCH v5 02/23] ARM: amba: Move reading of periphid to pre_probe()

requirements. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: - Added bus.pre_probe callback so the probes of Primecell devices can be deferred if their device IDs cannot be yet read because of the clock driver not having probed when they are regi

[PATCH v5 01/23] driver core: Add pre_probe callback to bus_type

of the resources needed are missing. This gives us more flexibility when setting the order in which devices are probed because the resources needed to get the matching information don't need to be available by the time that the bus devices are registered. Signed-off-by: Tomeu Vizoso <tomeu.

[PATCH v5 04/23] of: add function to allow probing a device from a OF node

to be probed as well (when they get registered). Subsystems can use this when looking up resources for drivers, to reduce the chances of deferred probes because of the probing order of devices. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: - Move the assignment to devic

[PATCH v5 05/23] gpio: Probe GPIO drivers on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/gpio/gpiolib-of.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c index fa6e3c8823d6..9a439d

[PATCH v5 13/23] pwm: Probe PWM chip devices on demand

When looking up a PWM chip through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 12/23] i2c: core: Probe i2c adapters and devices on demand

-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/i2c/i2c-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c index 5f89f1e3c2f2..02da3a

[PATCH v5 15/23] usb: phy: Probe phy devices on demand

When looking up a phy through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v5 17/23] pinctrl: Probe pinctrl devices on demand

-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None drivers/pinctrl/devicetree.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pinctrl/devicetree.c b/drivers/pinctrl/devicetree.c index fe04e7

[PATCH v5 22/23] driver core: Start processing deferred probes earlier

in device_initcall_sync we increase the chances that the initcalls mentioned before will find the devices they depend on to have already probed. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: - Start processing deferred probes in device_initcal

[PATCH v5 21/23] driver core: Allow deferring probes until late init

Add a field to struct device that instructs the device-driver core to defer the probe of this device until the late_initcall level. By letting all built-in drivers to register before starting to probe, we can avoid any deferred probes by probing dependencies on demand. Signed-off-by: Tomeu

[PATCH v5 23/23] of/platform: Defer probes of registered devices

registered already. This allows us to prevent deferred probes by probing dependencies on demand. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v5: None Changes in v4: - Also defer probes of AMBA devices registered from the DT as they can also request resources. Changes

Re: [PATCH] driver core: Ensure proper suspend/resume ordering

On 17 September 2015 at 02:27, Rafael J. Wysocki wrote: > On Wednesday, September 16, 2015 03:22:37 PM Alan Stern wrote: >> >> It would also help if your patch checked to see if the device has any >> children, and avoided moving it to the end of the list if it does. In >> fact, that might be

Re: [PATCH v4 04/22] of: add function to allow probing a device from a OF node

On 11 September 2015 at 14:08, Mark Brown wrote: > On Mon, Sep 07, 2015 at 02:23:29PM +0200, Tomeu Vizoso wrote: >> Walks the OF tree up and finds the closest ancestor that has a struct >> device associated with it, probing it if isn't bound to a driver yet. > >>

Re: [PATCH v4 04/22] of: add function to allow probing a device from a OF node

On 11 September 2015 at 14:08, Mark Brown <broo...@kernel.org> wrote: > On Mon, Sep 07, 2015 at 02:23:29PM +0200, Tomeu Vizoso wrote: >> Walks the OF tree up and finds the closest ancestor that has a struct >> device associated with it, probing it if isn't bound to a drive

Re: [PATCH] driver core: Ensure proper suspend/resume ordering

On 17 September 2015 at 02:27, Rafael J. Wysocki wrote: > On Wednesday, September 16, 2015 03:22:37 PM Alan Stern wrote: >> >> It would also help if your patch checked to see if the device has any >> children, and avoided moving it to the end of the list if it does. In >>

Re: [PATCH v4 21/22] driver core: Start processing deferred probes earlier

On 11 September 2015 at 14:24, Mark Brown wrote: > On Mon, Sep 07, 2015 at 02:23:46PM +0200, Tomeu Vizoso wrote: >> Some initcalls in the late level assume that some devices will have >> already probed without explicitly checking for that. >> >> After the recent move

Re: [PATCH v3 02/18] of/platform: add of_platform_probe

On 11 September 2015 at 17:35, Mark Brown wrote: > On Fri, Sep 11, 2015 at 04:06:07PM +0200, Tomeu Vizoso wrote: > >> Once a platform device (with the platform bus as its parent) is >> retrieved from the deferred queue, both the parent and the device in >> question are lo

Re: [PATCH v4 21/22] driver core: Start processing deferred probes earlier

On 11 September 2015 at 14:24, Mark Brown <broo...@kernel.org> wrote: > On Mon, Sep 07, 2015 at 02:23:46PM +0200, Tomeu Vizoso wrote: >> Some initcalls in the late level assume that some devices will have >> already probed without explicitly checking for that. >> >&g

Re: [PATCH v3 02/18] of/platform: add of_platform_probe

On 11 September 2015 at 17:35, Mark Brown <broo...@kernel.org> wrote: > On Fri, Sep 11, 2015 at 04:06:07PM +0200, Tomeu Vizoso wrote: > >> Once a platform device (with the platform bus as its parent) is >> retrieved from the deferred queue, both the parent and the device i

Re: [PATCH v4 20/22] driver core: Allow deferring probes until late init

On 11 September 2015 at 14:17, Mark Brown wrote: > On Mon, Sep 07, 2015 at 02:23:45PM +0200, Tomeu Vizoso wrote: >> Add a field to struct device that instructs the device-driver core to >> defer the probe of this device until the late_initcall level. >> >> By l

Re: [PATCH v4 20/22] driver core: Allow deferring probes until late init

On 11 September 2015 at 14:17, Mark Brown <broo...@kernel.org> wrote: > On Mon, Sep 07, 2015 at 02:23:45PM +0200, Tomeu Vizoso wrote: >> Add a field to struct device that instructs the device-driver core to >> defer the probe of this device until the late_initcall level. >&

Re: [PATCH v3 02/18] of/platform: add of_platform_probe

On 11 September 2015 at 11:57, Mark Brown wrote: > On Mon, Sep 07, 2015 at 02:31:06PM +0200, Tomeu Vizoso wrote: >> On 11 August 2015 at 11:37, Tomeu Vizoso wrote: >> > On 7 August 2015 at 14:19, Mark Brown wrote: > >> >> This sounds like it's going to bre

Re: [PATCH v3 02/18] of/platform: add of_platform_probe

On 11 September 2015 at 11:57, Mark Brown <broo...@kernel.org> wrote: > On Mon, Sep 07, 2015 at 02:31:06PM +0200, Tomeu Vizoso wrote: >> On 11 August 2015 at 11:37, Tomeu Vizoso <tomeu.viz...@collabora.com> wrote: >> > On 7 August 2015 at 14:19, Mark Br

Re: [PATCH v4 04/22] of: add function to allow probing a device from a OF node

On 9 September 2015 at 03:29, Rob Herring wrote: > On 09/07/2015 07:23 AM, Tomeu Vizoso wrote: >> Walks the OF tree up and finds the closest ancestor that has a struct >> device associated with it, probing it if isn't bound to a driver yet. >> >> The above should

Re: [PATCH v4 04/22] of: add function to allow probing a device from a OF node

On 9 September 2015 at 03:29, Rob Herring <r...@kernel.org> wrote: > On 09/07/2015 07:23 AM, Tomeu Vizoso wrote: >> Walks the OF tree up and finds the closest ancestor that has a struct >> device associated with it, probing it if isn't bound to a driver yet. >>

Re: [PATCH v4 0/22] On-demand device probing

On 9 September 2015 at 03:33, Rob Herring wrote: > On 09/08/2015 02:30 AM, Tomeu Vizoso wrote: >> On 7 September 2015 at 22:50, Rob Herring wrote: >>> On Mon, Sep 7, 2015 at 7:23 AM, Tomeu Vizoso >>> wrote: >>>> Hello, >>>> >>>>

<    5   6   7   8   9   10   11   12   13   14   >