Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 13:08, Ulf Hansson wrote: > On 20 December 2017 at 10:02, Kishon Vijay Abraham I wrote: >> Hi Ulf, >> >> On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: >>> On 20 December 2017 at 07:42, Kishon Vijay Abraham I

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 13:08, Ulf Hansson wrote: > On 20 December 2017 at 10:02, Kishon Vijay Abraham I wrote: >> Hi Ulf, >> >> On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: >>> On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: Hi Ulf, On Wednesday 20

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 10:02, Kishon Vijay Abraham I wrote: > Hi Ulf, > > On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: >> On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: >>> Hi Ulf, >>> >>> On Wednesday 20 December 2017 02:52 AM, Ulf

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 10:02, Kishon Vijay Abraham I wrote: > Hi Ulf, > > On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: >> On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: >>> Hi Ulf, >>> >>> On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: The runtime PM

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

Hi Ulf, On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: > On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: >> Hi Ulf, >> >> On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: >>> The runtime PM deployment in the phy core is a bit unnecessary

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

Hi Ulf, On Wednesday 20 December 2017 02:05 PM, Ulf Hansson wrote: > On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: >> Hi Ulf, >> >> On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: >>> The runtime PM deployment in the phy core is a bit unnecessary complicated >>> and the

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: > Hi Ulf, > > On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: >> The runtime PM deployment in the phy core is a bit unnecessary complicated >> and the main reason is because it operates on the phy device, which

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

On 20 December 2017 at 07:42, Kishon Vijay Abraham I wrote: > Hi Ulf, > > On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: >> The runtime PM deployment in the phy core is a bit unnecessary complicated >> and the main reason is because it operates on the phy device, which is >> created

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

Hi Ulf, On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: > The runtime PM deployment in the phy core is a bit unnecessary complicated > and the main reason is because it operates on the phy device, which is > created by the phy core and assigned as a child device of the phy provider >

Re: [PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

Hi Ulf, On Wednesday 20 December 2017 02:52 AM, Ulf Hansson wrote: > The runtime PM deployment in the phy core is a bit unnecessary complicated > and the main reason is because it operates on the phy device, which is > created by the phy core and assigned as a child device of the phy provider >

[PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

The runtime PM deployment in the phy core is a bit unnecessary complicated and the main reason is because it operates on the phy device, which is created by the phy core and assigned as a child device of the phy provider device. Let's simplify the code, by replacing the existing calls to

[PATCH 1/3] phy: core: Move runtime PM reference counting to the parent device

The runtime PM deployment in the phy core is a bit unnecessary complicated and the main reason is because it operates on the phy device, which is created by the phy core and assigned as a child device of the phy provider device. Let's simplify the code, by replacing the existing calls to