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

On 24 October 2015 at 15:57, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Thursday, October 22, 2015 03:01:45 PM Tomeu Vizoso wrote: >> On 22 October 2015 at 03:02, Rafael J. Wysocki <r...@rjwysocki.net> wrote: >> > On Monday, September 21, 2015 04:02:43 PM

[PATCH] staging: board: Set PM domain before probe

PM domains shouldn't be modified after a device is probed, so set it before device registration to be sure of that. In the future the PM domain pointer will be set through a setter that will WARN if the device has been probed already. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com&

[PATCH v11 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Reviewed-by: Ulf Hansson <ulf.hans...@linaro.org> --- Changes in v9: - Move to CONFIG_PM_SLEEP as suggested by Rafael and Ulf. - Rename from device_check_

Re: [GIT PULL] On-demand device probing

On 26 October 2015 at 11:51, Michael Turquette wrote: > Quoting Rafael J. Wysocki (2015-10-25 06:54:39) >> On Sun, Oct 25, 2015 at 12:06 AM, Mark Brown wrote: >> > On Sat, Oct 24, 2015 at 04:17:12PM +0200, Rafael J. Wysocki wrote: >> > >> >> Well, I'm not quite sure why exactly everyone is so

Re: [PATCH v10 2/4] PM / Domains: add setter for dev.pm_domain

On 25 October 2015 at 16:18, Rafael J. Wysocki wrote: > On Wednesday, October 21, 2015 05:34:12 PM Tomeu Vizoso wrote: >> Adds a function that sets the pointer to dev_pm_domain in struct device >> and that warns if the device has already finished probing. The reason >> w

Re: [PATCH v10 2/4] PM / Domains: add setter for dev.pm_domain

On 25 October 2015 at 16:18, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Wednesday, October 21, 2015 05:34:12 PM Tomeu Vizoso wrote: >> Adds a function that sets the pointer to dev_pm_domain in struct device >> and that warns if the device has already finished probing.

Re: [GIT PULL] On-demand device probing

On 26 October 2015 at 11:51, Michael Turquette wrote: > Quoting Rafael J. Wysocki (2015-10-25 06:54:39) >> On Sun, Oct 25, 2015 at 12:06 AM, Mark Brown wrote: >> > On Sat, Oct 24, 2015 at 04:17:12PM +0200, Rafael J. Wysocki wrote: >> > >> >> Well, I'm

Re: [GIT PULL] On-demand device probing

On 10/22/2015 09:26 PM, Greg Kroah-Hartman wrote: > On Thu, Oct 22, 2015 at 11:53:31AM -0700, Frank Rowand wrote: >> On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote: >>> >>> >>> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote: >>>>

Re: [GIT PULL] On-demand device probing

On 10/22/2015 09:26 PM, Greg Kroah-Hartman wrote: > On Thu, Oct 22, 2015 at 11:53:31AM -0700, Frank Rowand wrote: >> On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote: >>> <oops, sent too early...> >>> >>> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vi

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

On 22 October 2015 at 00:51, Scott Wood wrote: > On Wed, 2015-10-21 at 08:44 -0500, Rob Herring wrote: >> On Wed, Oct 21, 2015 at 12:54 AM, Scott Wood >> wrote: >> > On Mon, 2015-09-21 at 16:03 +0200, Tomeu Vizoso wrote: >> > > Instead of trying to match and p

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

On 22 October 2015 at 03:06, Rafael J. Wysocki wrote: > On Monday, September 21, 2015 04:02:44 PM 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 v6 03/22] of/platform: Point to struct device from device node

On 22 October 2015 at 03:02, Rafael J. Wysocki wrote: > On Monday, September 21, 2015 04:02:43 PM Tomeu Vizoso wrote: >> When adding platform and AMBA devices, set the device node's device >> member to point to it. >> >> This speeds lookups considerably and is safe

Re: [GIT PULL] On-demand device probing

On 22 October 2015 at 02:54, Rafael J. Wysocki wrote: > On Tuesday, October 20, 2015 06:21:55 PM Tomeu Vizoso wrote: >> On 20 October 2015 at 18:04, Alan Stern wrote: >> > On Tue, 20 Oct 2015, Mark Brown wrote: >> > >> >> On Tue, Oct 20, 201

Re: [GIT PULL] On-demand device probing

On 21 October 2015 at 23:50, Frank Rowand wrote: > On 10/21/2015 2:12 PM, Rob Herring wrote: >> On Wed, Oct 21, 2015 at 1:18 PM, Frank Rowand wrote: >>> On 10/21/2015 9:27 AM, Mark Brown wrote: >>>> On Wed, Oct 21, 2015 at 08:59:51AM -0700, Frank Rowand wrote: >

Re: [GIT PULL] On-demand device probing

On 22 October 2015 at 02:54, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Tuesday, October 20, 2015 06:21:55 PM Tomeu Vizoso wrote: >> On 20 October 2015 at 18:04, Alan Stern <st...@rowland.harvard.edu> wrote: >> > On Tue, 20 Oct 2015, Mark Brown wrote: >>

Re: [GIT PULL] On-demand device probing

d, Oct 21, 2015 at 08:59:51AM -0700, Frank Rowand wrote: >>>>> On 10/19/2015 5:34 AM, Tomeu Vizoso wrote: >>>> >>>>>> To be clear, I was saying that this series should NOT affect total >>>>>> boot times much. >>>> >>>

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

On 22 October 2015 at 00:51, Scott Wood <scottw...@freescale.com> wrote: > On Wed, 2015-10-21 at 08:44 -0500, Rob Herring wrote: >> On Wed, Oct 21, 2015 at 12:54 AM, Scott Wood <scottw...@freescale.com> >> wrote: >> > On Mon, 2015-09-21 at 16:03 +0200, Tomeu Vi

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

On 22 October 2015 at 03:02, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Monday, September 21, 2015 04:02:43 PM Tomeu Vizoso wrote: >> When adding platform and AMBA devices, set the device node's device >> member to point to it. >> >> This speeds lookups co

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

On 22 October 2015 at 03:06, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Monday, September 21, 2015 04:02:44 PM 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

Re: [PATCH] driver core: Disable late probes by default

On 21 October 2015 at 17:14, Greg Kroah-Hartman wrote: > On Wed, Oct 21, 2015 at 04:35:58PM +0200, Tomeu Vizoso wrote: >> On 21 October 2015 at 05:39, Greg Kroah-Hartman >> wrote: >> > On Tue, Oct 20, 2015 at 06:17:39PM +0200, Tomeu Vizoso wrote: >> >> On

[PATCH v10 1/4] device core: add device_is_bound()

that we can simplify code quite a bit if we can always assume that. Signed-off-by: Tomeu Vizoso Reviewed-by: Ulf Hansson --- Changes in v9: - Add docs noting the need for the device lock to be held before calling device_is_bound() Changes in v8: - Add device_is_bound() drivers/base/dd.c

[PATCH v10 2/4] PM / Domains: add setter for dev.pm_domain

that. This patch also changes all current code that directly sets the dev.pm_domain pointer. Signed-off-by: Tomeu Vizoso Reviewed-by: Ulf Hansson --- Changes in v9: - Add docs noting the need for the device lock to be held before calling dev_pm_domain_set() Changes in v8: - Add

[PATCH v10 4/4] USB / PM: Allow USB devices to remain runtime-suspended when sleeping

Have dev_pm_ops.prepare return 1 for USB devices and ports so that USB devices can remain runtime-suspended when the system goes to a sleep state, if their wakeup state is correct and they have runtime PM enabled. Signed-off-by: Tomeu Vizoso Reviewed-by: Ulf Hansson --- Changes in v10

[PATCH v10 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso Reviewed-by: Ulf Hansson --- Changes in v9: - Move to CONFIG_PM_SLEEP as suggested by Rafael and Ulf. - Rename from device_check_pm_callbacks to device_pm_check_callbacks to follow

[PATCH v10 0/4] Allow USB devices to remain runtime-suspended when sleeping

eck for all dev_pm_ops instances associated to a device, updating a no_pm_callbacks flag at the times when that could change. Tomeu Vizoso (4): device core: add device_is_bound() PM / Domains: add setter for dev.pm_domain PM / sleep: Go direct_complete if driver has no callbacks USB / PM: Al

Re: [PATCH] driver core: Disable late probes by default

On 21 October 2015 at 05:39, Greg Kroah-Hartman wrote: > On Tue, Oct 20, 2015 at 06:17:39PM +0200, Tomeu Vizoso wrote: >> On 20 October 2015 at 16:05, Greg Kroah-Hartman >> wrote: >> > On Tue, Oct 20, 2015 at 09:40:48AM +0200, Tomeu Vizoso wrote: >> >> On

Re: [PATCH] driver core: Disable late probes by default

On 21 October 2015 at 05:39, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Tue, Oct 20, 2015 at 06:17:39PM +0200, Tomeu Vizoso wrote: >> On 20 October 2015 at 16:05, Greg Kroah-Hartman >> <gre...@linuxfoundation.org> wrote: >> > On Tue, Oct 20, 20

[PATCH v10 0/4] Allow USB devices to remain runtime-suspended when sleeping

eck for all dev_pm_ops instances associated to a device, updating a no_pm_callbacks flag at the times when that could change. Tomeu Vizoso (4): device core: add device_is_bound() PM / Domains: add setter for dev.pm_domain PM / sleep: Go direct_complete if driver has no callbacks USB / PM: Al

Re: [PATCH] driver core: Disable late probes by default

On 21 October 2015 at 17:14, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Wed, Oct 21, 2015 at 04:35:58PM +0200, Tomeu Vizoso wrote: >> On 21 October 2015 at 05:39, Greg Kroah-Hartman >> <gre...@linuxfoundation.org> wrote: >> > On Tue, Oct 20, 20

[PATCH v10 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Reviewed-by: Ulf Hansson <ulf.hans...@linaro.org> --- Changes in v9: - Move to CONFIG_PM_SLEEP as suggested by Rafael and Ulf. - Rename from device_check_

[PATCH v10 4/4] USB / PM: Allow USB devices to remain runtime-suspended when sleeping

Have dev_pm_ops.prepare return 1 for USB devices and ports so that USB devices can remain runtime-suspended when the system goes to a sleep state, if their wakeup state is correct and they have runtime PM enabled. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Reviewed-by: Ulf H

[PATCH v10 1/4] device core: add device_is_bound()

that we can simplify code quite a bit if we can always assume that. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Reviewed-by: Ulf Hansson <ulf.hans...@linaro.org> --- Changes in v9: - Add docs noting the need for the device lock to be held before calling device_is_boun

[PATCH v10 2/4] PM / Domains: add setter for dev.pm_domain

that. This patch also changes all current code that directly sets the dev.pm_domain pointer. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Reviewed-by: Ulf Hansson <ulf.hans...@linaro.org> --- Changes in v9: - Add docs noting the need for the device lock to be held be

Re: [GIT PULL] On-demand device probing

On 20 October 2015 at 18:04, Alan Stern wrote: > On Tue, 20 Oct 2015, Mark Brown wrote: > >> On Tue, Oct 20, 2015 at 10:40:03AM -0400, Alan Stern wrote: >> >> > Furthermore, that applies only to devices that use synchronous suspend. >> > Async suspend is becoming common, and there the only

Re: [PATCH] driver core: Disable late probes by default

On 20 October 2015 at 16:05, Greg Kroah-Hartman wrote: > On Tue, Oct 20, 2015 at 09:40:48AM +0200, Tomeu Vizoso wrote: >> On 19 October 2015 at 17:19, Greg Kroah-Hartman >> wrote: >> > On Mon, Oct 19, 2015 at 05:13:22PM +0200, Tomeu Vizoso wrote: >> >> To

Re: [PATCH] driver core: Disable late probes by default

On 19 October 2015 at 17:19, Greg Kroah-Hartman wrote: > On Mon, Oct 19, 2015 at 05:13:22PM +0200, Tomeu Vizoso wrote: >> To smooth the transition to late probes, make disabled the default for >> DELAY_DEVICE_PROBES and let individual SoCs enable the option as they >> get fi

Re: [PATCH] driver core: Disable late probes by default

On 19 October 2015 at 17:19, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Mon, Oct 19, 2015 at 05:13:22PM +0200, Tomeu Vizoso wrote: >> To smooth the transition to late probes, make disabled the default for >> DELAY_DEVICE_PROBES and let individual S

Re: [GIT PULL] On-demand device probing

On 20 October 2015 at 18:04, Alan Stern wrote: > On Tue, 20 Oct 2015, Mark Brown wrote: > >> On Tue, Oct 20, 2015 at 10:40:03AM -0400, Alan Stern wrote: >> >> > Furthermore, that applies only to devices that use synchronous suspend. >> > Async suspend is becoming

Re: [PATCH] driver core: Disable late probes by default

On 20 October 2015 at 16:05, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Tue, Oct 20, 2015 at 09:40:48AM +0200, Tomeu Vizoso wrote: >> On 19 October 2015 at 17:19, Greg Kroah-Hartman >> <gre...@linuxfoundation.org> wrote: >> > On Mon, Oct 19, 20

[PATCH] driver core: Disable late probes by default

To smooth the transition to late probes, make disabled the default for DELAY_DEVICE_PROBES and let individual SoCs enable the option as they get fixed. Signed-off-by: Tomeu Vizoso Link: https://lkml.kernel.org/g/20151016181129.ga1...@gradator.net --- Hi Rob, I'm sending this in case you think

Re: [GIT PULL] On-demand device probing

On 19 October 2015 at 16:30, Russell King - ARM Linux wrote: > On Mon, Oct 19, 2015 at 04:10:56PM +0200, Tomeu Vizoso wrote: >> On 19 October 2015 at 15:18, Russell King - ARM Linux >> wrote: >> > On Mon, Oct 19, 2015 at 02:34:22PM +0200, Tomeu Vizoso wrote: >> &

Re: [GIT PULL] On-demand device probing

On 19 October 2015 at 15:18, Russell King - ARM Linux wrote: > On Mon, Oct 19, 2015 at 02:34:22PM +0200, Tomeu Vizoso wrote: >> ... If a device is available and has >> a compatible driver, but it cannot be probed because a dependency >> isn't going to be available, that's

Re: [GIT PULL] On-demand device probing

On 18 October 2015 at 21:53, Mark Brown wrote: > On Sun, Oct 18, 2015 at 12:37:57PM -0700, Greg Kroah-Hartman wrote: >> On Sun, Oct 18, 2015 at 08:29:31PM +0100, Mark Brown wrote: >> > On Fri, Oct 16, 2015 at 11:57:50PM -0700, Greg Kroah-Hartman wrote: > >> > > I can't see adding calls like this

Re: [GIT PULL] On-demand device probing

On 18 October 2015 at 21:53, Mark Brown wrote: > On Sun, Oct 18, 2015 at 12:37:57PM -0700, Greg Kroah-Hartman wrote: >> On Sun, Oct 18, 2015 at 08:29:31PM +0100, Mark Brown wrote: >> > On Fri, Oct 16, 2015 at 11:57:50PM -0700, Greg Kroah-Hartman wrote: > >> > > I can't see

Re: [GIT PULL] On-demand device probing

On 19 October 2015 at 15:18, Russell King - ARM Linux <li...@arm.linux.org.uk> wrote: > On Mon, Oct 19, 2015 at 02:34:22PM +0200, Tomeu Vizoso wrote: >> ... If a device is available and has >> a compatible driver, but it cannot be probed because a dependency >> isn't go

Re: [GIT PULL] On-demand device probing

On 19 October 2015 at 16:30, Russell King - ARM Linux <li...@arm.linux.org.uk> wrote: > On Mon, Oct 19, 2015 at 04:10:56PM +0200, Tomeu Vizoso wrote: >> On 19 October 2015 at 15:18, Russell King - ARM Linux >> <li...@arm.linux.org.uk> wrote: >> > On Mon, Oct

[PATCH] driver core: Disable late probes by default

To smooth the transition to late probes, make disabled the default for DELAY_DEVICE_PROBES and let individual SoCs enable the option as they get fixed. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Link: https://lkml.kernel.org/g/20151016181129.ga1...@gradator.net --- Hi Rob

Re: Atmel SoCs and the newly added CONFIG_DELAY_DEVICE_PROBES option

On 16 October 2015 at 20:11, Sylvain Rochet wrote: > Hi, > > FYI, to save you a git bisect, the recently added > CONFIG_DELAY_DEVICE_PROBES (enabled by default) breaks Atmel SoCs. > > For a few of quickly noticeable issues: > - PM is not working: at91_pm_sram_init: sram pool unavailable! > -

Re: [PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

On 16 October 2015 at 19:26, Stephen Boyd wrote: > On 10/16, Michael Turquette wrote: >> Quoting Krzysztof Kozlowski (2015-10-15 16:46:27) >> > On 15.10.2015 19:31, Tomeu Vizoso wrote: >> > > When the DISP1 power domain is powered off, there's two clocks that

Re: [RFT PATCH v2 3/6] ARM: dts: Mark SDIO as non-removable in exynos5250-snow-common

gt; > Signed-off-by: Javier Martinez Canillas Reviewed-by: Tomeu Vizoso Tested-by: Tomeu Vizoso Thanks, Tomeu > > Changes since v1: > - Remove card-detect-delay property as well. > - Use the correct mmc node. Suggested by Tomeu. > > arch/arm/boot/dts/exynos5250-snow

Re: [RFT PATCH v2 6/6] ARM: dts: Mark eMMC as non-removable in exynos5250-snow-common

> > Signed-off-by: Javier Martinez Canillas Reviewed-by: Tomeu Vizoso Tested-by: Tomeu Vizoso Thanks, Tomeu > --- > > Changes since v1: > - None, new patch. > > arch/arm/boot/dts/exynos5250-snow-common.dtsi | 3 +-- > 1 file changed, 1 insertion(+), 2 delet

Re: [PATCH v2 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

On 10/16/2015 01:44 AM, Krzysztof Kozlowski wrote: > On 15.10.2015 19:31, Tomeu Vizoso wrote: >> Adds to the node of the DISP1 power domain the two clocks that need to >> be reparented while the domain is powered off: >> CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1

Re: [PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

On 16 October 2015 at 19:26, Stephen Boyd <sb...@codeaurora.org> wrote: > On 10/16, Michael Turquette wrote: >> Quoting Krzysztof Kozlowski (2015-10-15 16:46:27) >> > On 15.10.2015 19:31, Tomeu Vizoso wrote: >> > > When the DISP1 power domain is power

Re: Atmel SoCs and the newly added CONFIG_DELAY_DEVICE_PROBES option

On 16 October 2015 at 20:11, Sylvain Rochet wrote: > Hi, > > FYI, to save you a git bisect, the recently added > CONFIG_DELAY_DEVICE_PROBES (enabled by default) breaks Atmel SoCs. > > For a few of quickly noticeable issues: > - PM is not working: at91_pm_sram_init:

Re: [PATCH v2 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

On 10/16/2015 01:44 AM, Krzysztof Kozlowski wrote: > On 15.10.2015 19:31, Tomeu Vizoso wrote: >> Adds to the node of the DISP1 power domain the two clocks that need to >> be reparented while the domain is powered off: >> CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1

Re: [RFT PATCH v2 6/6] ARM: dts: Mark eMMC as non-removable in exynos5250-snow-common

needed with > non-removable. > > Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com> Reviewed-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Tested-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Thanks, Tomeu > --- > > Changes since v1: >

Re: [RFT PATCH v2 3/6] ARM: dts: Mark SDIO as non-removable in exynos5250-snow-common

with > non-removable. > > Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com> Reviewed-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Tested-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Thanks, Tomeu > > Changes since v1: > - Remove card-detect-

Re: [RFT PATCH 3/3] ARM: dts: Mark SDIO as non-removable in exynos5250-snow-common

On 15 October 2015 at 12:55, Javier Martinez Canillas wrote: > The Exynos5250 Snow Chromebooks have a Marvell WiFi SDIO chip which > can't neither be removed nor be detected. But the node isn't marked > as non-removable and instead has the broken-cd DT property. > > This causes the device to be

[GIT PULL] On-demand device probing

(2015-10-15 13:25:47 +0200) Tomeu Vizoso (20): driver core: handle -EPROBE_DEFER from bus_type.match() ARM: amba: Move reading of periphid to amba_match() of/platform: Point to struct device from device node

[PATCH v2 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

Adds to the node of the DISP1 power domain the two clocks that need to be reparented while the domain is powered off: CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1_SUB. Otherwise the state is unknown at power up and the mixer's clocks are all messed up. Signed-off-by: Tomeu Vizoso Link

[PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

-off-by: Tomeu Vizoso Acked-by: Stephen Boyd --- Changes in v2: - Reuse mout_aclk200_p - Rename div_aclk300 as div_aclk300_disp drivers/clk/samsung/clk-exynos5250.c | 14 +- include/dt-bindings/clock/exynos5250.h | 4 +++- 2 files changed, 16 insertions(+), 2 deletions(-) diff

[PATCH v2 0/2] Fix display on second resume on 5250-snow

Tomeu Vizoso (2): clk: samsung: exynos5250: Add DISP1 clocks ARM: dts: exynos5250: Add clocks to DISP1 domain arch/arm/boot/dts/exynos5250.dtsi | 4 drivers/clk/samsung/clk-exynos5250.c | 14 +- include/dt-bindings/clock/exynos5250.h | 4 +++- 3 files changed, 20

Re: [RFT PATCH 3/3] ARM: dts: Mark SDIO as non-removable in exynos5250-snow-common

On 15 October 2015 at 12:55, Javier Martinez Canillas wrote: > The Exynos5250 Snow Chromebooks have a Marvell WiFi SDIO chip which > can't neither be removed nor be detected. But the node isn't marked > as non-removable and instead has the broken-cd DT property. > > This

[PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> Acked-by: Stephen Boyd <sb...@codeaurora.org> --- Changes in v2: - Reuse mout_aclk200_p - Rename div_aclk300 as div_aclk300_disp drivers/clk/samsung/clk-exynos5250.c | 14 +- include/dt-bindings/clock/exynos5250.h | 4 +

[PATCH v2 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

Adds to the node of the DISP1 power domain the two clocks that need to be reparented while the domain is powered off: CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1_SUB. Otherwise the state is unknown at power up and the mixer's clocks are all messed up. Signed-off-by: Tomeu Vizoso

[PATCH v2 0/2] Fix display on second resume on 5250-snow

Tomeu Vizoso (2): clk: samsung: exynos5250: Add DISP1 clocks ARM: dts: exynos5250: Add clocks to DISP1 domain arch/arm/boot/dts/exynos5250.dtsi | 4 drivers/clk/samsung/clk-exynos5250.c | 14 +- include/dt-bindings/clock/exynos5250.h | 4 +++- 3 files changed, 20

[GIT PULL] On-demand device probing

(2015-10-15 13:25:47 +0200) Tomeu Vizoso (20): driver core: handle -EPROBE_DEFER from bus_type.match() ARM: amba: Move reading of periphid to amba_match() of/platform: Point to struct device from device node

[PATCH v1 1/2] clk: samsung: exynos5250: Add DISP1 clocks

-off-by: Tomeu Vizoso --- drivers/clk/samsung/clk-exynos5250.c | 16 +++- include/dt-bindings/clock/exynos5250.h | 4 +++- 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/drivers/clk/samsung/clk-exynos5250.c b/drivers/clk/samsung/clk-exynos5250.c index 55b83c7ef878

[PATCH v1 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

Adds to the node of the DISP1 power domain the two clocks that need to be reparented while the domain is powered off: CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1_SUB. Otherwise the state is unknown at power up and the mixer's clocks are all messed up. Signed-off-by: Tomeu Vizoso Link

[PATCH v1 0/2] Fix display on second resume on 5250-snow

beneath our feet. This series tasks the kernel to do the reparenting itself so that the HW state always matches the kernel's internal state. Thanks, Tomeu [0] http://lkml.kernel.org/g/561cdc33.7050...@collabora.com Tomeu Vizoso (2): clk: samsung: exynos5250: Add DISP1 clocks ARM: dts

[GIT PULL] On-demand device probing

://git.collabora.co.uk/git/user/tomeu/linux.git on-demand-probes-for-next for you to fetch changes up to 587402133fe433759d2d535e5d92ead87fd7f615: of/platform: Defer probes of registered devices (2015-10-14 10:08:23 +0200) Tomeu Vizoso (20

Re: [BUG] broken mixer after second resume from mem

On 14 October 2015 at 07:55, Krzysztof Kozlowski wrote: > On 13.10.2015 19:25, Tomeu Vizoso wrote: >> Hi, >> >> have been hunting down a bug on exynos5250-snow which caused both HDMI >> and LVDS output to be broken after the second resume (with suspend to >> me

Re: [BUG] broken mixer after second resume from mem

On 14 October 2015 at 07:55, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 13.10.2015 19:25, Tomeu Vizoso wrote: >> Hi, >> >> have been hunting down a bug on exynos5250-snow which caused both HDMI >> and LVDS output to be broken after the seco

[GIT PULL] On-demand device probing

://git.collabora.co.uk/git/user/tomeu/linux.git on-demand-probes-for-next for you to fetch changes up to 587402133fe433759d2d535e5d92ead87fd7f615: of/platform: Defer probes of registered devices (2015-10-14 10:08:23 +0200) Tomeu Vizoso (20

[PATCH v1 2/2] ARM: dts: exynos5250: Add clocks to DISP1 domain

Adds to the node of the DISP1 power domain the two clocks that need to be reparented while the domain is powered off: CLK_MOUT_ACLK200_DISP1_SUB and CLK_MOUT_ACLK300_DISP1_SUB. Otherwise the state is unknown at power up and the mixer's clocks are all messed up. Signed-off-by: Tomeu Vizoso

[PATCH v1 0/2] Fix display on second resume on 5250-snow

beneath our feet. This series tasks the kernel to do the reparenting itself so that the HW state always matches the kernel's internal state. Thanks, Tomeu [0] http://lkml.kernel.org/g/561cdc33.7050...@collabora.com Tomeu Vizoso (2): clk: samsung: exynos5250: Add DISP1 clocks ARM: dts

[PATCH v1 1/2] clk: samsung: exynos5250: Add DISP1 clocks

-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/clk/samsung/clk-exynos5250.c | 16 +++- include/dt-bindings/clock/exynos5250.h | 4 +++- 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/drivers/clk/samsung/clk-exynos5250.c b/drivers/clk/samsu

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

On 26 September 2015 at 20:17, Rob Herring wrote: > On 09/21/2015 09:02 AM, Tomeu Vizoso wrote: >> Hello, >> >> I have a problem with the panel on my Tegra Chromebook taking longer >> than expected to be ready during boot (Stéphane Marchesin reported what >>

[BUG] broken mixer after second resume from mem

Hi, have been hunting down a bug on exynos5250-snow which caused both HDMI and LVDS output to be broken after the second resume (with suspend to mem, but not to idle). What I have found is that when powering down the DISP1 power domain while suspending for the second time, the contents of the

[BUG] broken mixer after second resume from mem

Hi, have been hunting down a bug on exynos5250-snow which caused both HDMI and LVDS output to be broken after the second resume (with suspend to mem, but not to idle). What I have found is that when powering down the DISP1 power domain while suspending for the second time, the contents of the

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

On 26 September 2015 at 20:17, Rob Herring <r...@kernel.org> wrote: > On 09/21/2015 09:02 AM, Tomeu Vizoso wrote: >> Hello, >> >> I have a problem with the panel on my Tegra Chromebook taking longer >> than expected to be ready during boot (Stéphane Marchesin repor

[PATCH v9 1/4] device core: add device_is_bound()

that we can simplify code quite a bit if we can always assume that. Signed-off-by: Tomeu Vizoso --- Changes in v9: - Add docs noting the need for the device lock to be held before calling device_is_bound() Changes in v8: - Add device_is_bound() drivers/base/dd.c | 18

[PATCH v9 4/4] USB / PM: Allow USB devices to remain runtime-suspended when sleeping

Have dev_pm_ops.prepare return 1 for USB devices and ports so that USB devices can remain runtime-suspended when the system goes to a sleep state, if their wakeup state is correct and they have runtime PM enabled. Signed-off-by: Tomeu Vizoso --- drivers/usb/core/port.c | 6 ++ drivers

[PATCH v9 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso --- Changes in v9: - Move to CONFIG_PM_SLEEP as suggested by Rafael and Ulf. - Rename from device_check_pm_callbacks to device_pm_check_callbacks to follow with the naming convention of existing

[PATCH v9 2/4] PM / Domains: add setter for dev.pm_domain

that. This patch also changes all current code that directly sets the dev.pm_domain pointer. Signed-off-by: Tomeu Vizoso --- Changes in v9: - Add docs noting the need for the device lock to be held before calling dev_pm_domain_set() Changes in v8: - Add dev_pm_domain_set() and update code

[PATCH v9 0/4] Allow USB devices to remain runtime-suspended when sleeping

lag at the times when that could change. Tomeu Vizoso (4): device core: add device_is_bound() PM / Domains: add setter for dev.pm_domain PM / sleep: Go direct_complete if driver has no callbacks USB / PM: Allow USB devices to remain runtime-suspended when sleeping arch/arm/mach-om

Re: [PATCH v8 3/4] PM / sleep: Go direct_complete if driver has no callbacks

On 2 October 2015 at 15:42, Rafael J. Wysocki wrote: > On Friday, October 02, 2015 10:40:49 AM Ulf Hansson wrote: >> On 2 October 2015 at 10:10, Tomeu Vizoso wrote: >> > On 2 October 2015 at 09:48, Ulf Hansson wrote: >> >> On 2 October 2015 at 09:

Re: [PATCH v5 1/2] PM / sleep: Go direct_complete if driver has no callbacks

On 4 October 2015 at 17:16, Pavel Machek wrote: > On Tue 2015-09-29 14:29:19, Tomeu Vizoso wrote: >> If a suitable prepare callback cannot be found for a given device and >> its driver has no PM callbacks at all, assume that it can go direct to >> complete when the

Re: [PATCH v5 1/2] PM / sleep: Go direct_complete if driver has no callbacks

On 4 October 2015 at 17:16, Pavel Machek <pa...@ucw.cz> wrote: > On Tue 2015-09-29 14:29:19, Tomeu Vizoso wrote: >> If a suitable prepare callback cannot be found for a given device and >> its driver has no PM callbacks at all, assume that it can go direct to >> co

Re: [PATCH v8 3/4] PM / sleep: Go direct_complete if driver has no callbacks

On 2 October 2015 at 15:42, Rafael J. Wysocki <r...@rjwysocki.net> wrote: > On Friday, October 02, 2015 10:40:49 AM Ulf Hansson wrote: >> On 2 October 2015 at 10:10, Tomeu Vizoso <tomeu.viz...@collabora.com> wrote: >> > On 2 October 2015 at 09:48, Ulf Hansson

[PATCH v9 1/4] device core: add device_is_bound()

that we can simplify code quite a bit if we can always assume that. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v9: - Add docs noting the need for the device lock to be held before calling device_is_bound() Changes in v8: - Add device_is_bound() drivers/bas

[PATCH v9 4/4] USB / PM: Allow USB devices to remain runtime-suspended when sleeping

Have dev_pm_ops.prepare return 1 for USB devices and ports so that USB devices can remain runtime-suspended when the system goes to a sleep state, if their wakeup state is correct and they have runtime PM enabled. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- drivers/us

[PATCH v9 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v9: - Move to CONFIG_PM_SLEEP as suggested by Rafael and Ulf. - Rename from device_check_pm_callbacks to device_pm_check_callbacks to

[PATCH v9 2/4] PM / Domains: add setter for dev.pm_domain

that. This patch also changes all current code that directly sets the dev.pm_domain pointer. Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com> --- Changes in v9: - Add docs noting the need for the device lock to be held before calling dev_pm_domain_set() Changes in v8:

[PATCH v9 0/4] Allow USB devices to remain runtime-suspended when sleeping

lag at the times when that could change. Tomeu Vizoso (4): device core: add device_is_bound() PM / Domains: add setter for dev.pm_domain PM / sleep: Go direct_complete if driver has no callbacks USB / PM: Allow USB devices to remain runtime-suspended when sleeping arch/arm/mach-om

Re: [PATCH v8 3/4] PM / sleep: Go direct_complete if driver has no callbacks

On 2 October 2015 at 09:48, Ulf Hansson wrote: > On 2 October 2015 at 09:14, Tomeu Vizoso wrote: >> If a suitable prepare callback cannot be found for a given device and >> its driver has no PM callbacks at all, assume that it can go direct to >> complete when the

[PATCH v8 1/4] device core: add device_is_bound()

that we can simplify code quite a bit if we can always assume that. Signed-off-by: Tomeu Vizoso --- Changes in v8: - Add device_is_bound() drivers/base/dd.c | 9 +++-- include/linux/device.h | 2 ++ 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/base/dd.c b

[PATCH v8 3/4] PM / sleep: Go direct_complete if driver has no callbacks

to prevent their ancestors to do direct_complete if they can support it. Signed-off-by: Tomeu Vizoso --- Changes in v8: - Move no_pm_callbacks field into CONFIG_PM_SLEEP - Call device_check_pm_callbacks only after a device is bound or unbound Changes in v7: - Reduce indentation by adding a label

[PATCH v8 4/4] USB / PM: Allow USB devices to remain runtime-suspended when sleeping

Have dev_pm_ops.prepare return 1 for USB devices and ports so that USB devices can remain runtime-suspended when the system goes to a sleep state, if their wakeup state is correct and they have runtime PM enabled. Signed-off-by: Tomeu Vizoso --- drivers/usb/core/port.c | 6 ++ drivers

[PATCH v8 2/4] PM / Domains: add setter for dev.pm_domain

that. This patch also changes all current code that directly sets the dev.pm_domain pointer. Signed-off-by: Tomeu Vizoso --- Changes in v8: - Add dev_pm_domain_set() and update code to use it arch/arm/mach-omap2/omap_device.c | 7 --- drivers/acpi/acpi_lpss.c | 5 +++-- drivers

<    3   4   5   6   7   8   9   10   11   12   >