On 09/10/17 17:36, Todor Tomov wrote:
> Hi,
>
> On 30.05.2017 06:41, Rajendra Nayak wrote:
>> []..
>>
> I was proposing to have such a lower-layer by splitting the existing
> genpd framework so the drivers would have the option of calling the
> lower-level power control functions to
On 09/10/17 17:36, Todor Tomov wrote:
> Hi,
>
> On 30.05.2017 06:41, Rajendra Nayak wrote:
>> []..
>>
> I was proposing to have such a lower-layer by splitting the existing
> genpd framework so the drivers would have the option of calling the
> lower-level power control functions to
Hi,
On 30.05.2017 06:41, Rajendra Nayak wrote:
> []..
>
I was proposing to have such a lower-layer by splitting the existing
genpd framework so the drivers would have the option of calling the
lower-level power control functions to look-up pm-domains and control
them directly
Hi,
On 30.05.2017 06:41, Rajendra Nayak wrote:
> []..
>
I was proposing to have such a lower-layer by splitting the existing
genpd framework so the drivers would have the option of calling the
lower-level power control functions to look-up pm-domains and control
them directly
[]..
>>> I was proposing to have such a lower-layer by splitting the existing
>>> genpd framework so the drivers would have the option of calling the
>>> lower-level power control functions to look-up pm-domains and control
>>> them directly from their rpm callbacks (if they need to). Same as we
[]..
>>> I was proposing to have such a lower-layer by splitting the existing
>>> genpd framework so the drivers would have the option of calling the
>>> lower-level power control functions to look-up pm-domains and control
>>> them directly from their rpm callbacks (if they need to). Same as we
On 03/05/17 18:12, Ulf Hansson wrote:
> [...]
>
> What is missing, is how a call to pm_runtime_get_sync() by a driver,
> can inform the ->start() callback about what exact power resource(s)
> it shall turn on, because it may not always be all of them. Similar
> problem
On 03/05/17 18:12, Ulf Hansson wrote:
> [...]
>
> What is missing, is how a call to pm_runtime_get_sync() by a driver,
> can inform the ->start() callback about what exact power resource(s)
> it shall turn on, because it may not always be all of them. Similar
> problem
[...]
>>>
What is missing, is how a call to pm_runtime_get_sync() by a driver,
can inform the ->start() callback about what exact power resource(s)
it shall turn on, because it may not always be all of them. Similar
problem exists for pm_runtime_put().
>>>
>>> Yes that is
[...]
>>>
What is missing, is how a call to pm_runtime_get_sync() by a driver,
can inform the ->start() callback about what exact power resource(s)
it shall turn on, because it may not always be all of them. Similar
problem exists for pm_runtime_put().
>>>
>>> Yes that is
On 03/05/17 14:43, Ulf Hansson wrote:
> On 3 May 2017 at 10:32, Jon Hunter wrote:
>> On 03/05/17 09:12, Ulf Hansson wrote:
>>> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
...
> So
On 03/05/17 14:43, Ulf Hansson wrote:
> On 3 May 2017 at 10:32, Jon Hunter wrote:
>> On 03/05/17 09:12, Ulf Hansson wrote:
>>> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
...
> So unless I am misunderstanding you here, it
On 3 May 2017 at 10:32, Jon Hunter wrote:
>
> On 03/05/17 09:12, Ulf Hansson wrote:
>> Rafael, Jon,
>>
>> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
>>> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
On 25/04/17 22:17, Rafael J.
On 3 May 2017 at 10:32, Jon Hunter wrote:
>
> On 03/05/17 09:12, Ulf Hansson wrote:
>> Rafael, Jon,
>>
>> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
>>> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
On 25/04/17 22:17, Rafael J. Wysocki wrote:
> On Tue, Apr 25, 2017
Hi Ulf,
On Wed, May 3, 2017 at 8:43 AM, Geert Uytterhoeven wrote:
> On Wed, Apr 26, 2017 at 11:55 AM, Ulf Hansson wrote:
>> On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
>>> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson
Hi Ulf,
On Wed, May 3, 2017 at 8:43 AM, Geert Uytterhoeven wrote:
> On Wed, Apr 26, 2017 at 11:55 AM, Ulf Hansson wrote:
>> On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
>>> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson
>>> wrote:
On 26 April 2017 at 10:06, Geert Uytterhoeven
On 03/05/17 09:12, Ulf Hansson wrote:
> Rafael, Jon,
>
> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
>> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>>
>>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
On 03/05/17 09:12, Ulf Hansson wrote:
> Rafael, Jon,
>
> On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
>> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>>
>>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
wrote:
> On 25
Rafael, Jon,
On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>
>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
>> > On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
>> > wrote:
>> >> On 25 April
On 02/05/17 22:51, Rafael J. Wysocki wrote:
> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>
>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
>>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
On 25 April 2017 at 13:13, Jon Hunter
Rafael, Jon,
On 2 May 2017 at 23:51, Rafael J. Wysocki wrote:
> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>
>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
>> > On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
>> > wrote:
>> >> On 25 April 2017 at 13:13, Jon Hunter wrote:
>> >>>
>>
On 02/05/17 22:51, Rafael J. Wysocki wrote:
> On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>>
>> On 25/04/17 22:17, Rafael J. Wysocki wrote:
>>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
On 25 April 2017 at 13:13, Jon Hunter wrote:
>
> On 28/03/17 15:13, Jon
Hi Ulf,
On Wed, Apr 26, 2017 at 11:55 AM, Ulf Hansson wrote:
> On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
>> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
>>> On 26 April 2017 at 10:06, Geert Uytterhoeven
Hi Ulf,
On Wed, Apr 26, 2017 at 11:55 AM, Ulf Hansson wrote:
> On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
>> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
>>> On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
wrote:
On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>
> On 25/04/17 22:17, Rafael J. Wysocki wrote:
> > On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> >> On 25 April 2017 at 13:13, Jon Hunter wrote:
> >>>
> >>> On 28/03/17 15:13, Jon
On Tuesday, May 02, 2017 11:10:29 AM Jon Hunter wrote:
>
> On 25/04/17 22:17, Rafael J. Wysocki wrote:
> > On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> >> On 25 April 2017 at 13:13, Jon Hunter wrote:
> >>>
> >>> On 28/03/17 15:13, Jon Hunter wrote:
> The current generic PM domain
On 25/04/17 22:17, Rafael J. Wysocki wrote:
> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>> On 25 April 2017 at 13:13, Jon Hunter wrote:
>>>
>>> On 28/03/17 15:13, Jon Hunter wrote:
The current generic PM domain framework (GenDP) only
On 25/04/17 22:17, Rafael J. Wysocki wrote:
> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>> On 25 April 2017 at 13:13, Jon Hunter wrote:
>>>
>>> On 28/03/17 15:13, Jon Hunter wrote:
The current generic PM domain framework (GenDP) only allows a single
PM domain to be
On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
> Hi Ulf,
>
> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
>> On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
>>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson
On 26 April 2017 at 11:17, Geert Uytterhoeven wrote:
> Hi Ulf,
>
> On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
>> On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
>>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
However, we currently know about at least two different
Hi Ulf,
On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
> On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>>> However, we currently know about at least two
Hi Ulf,
On Wed, Apr 26, 2017 at 11:04 AM, Ulf Hansson wrote:
> On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
>> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>>> However, we currently know about at least two different SoCs that need
>>> this. Perhaps we can extend the below list
On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
> Hi Ulf,
>
> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>> However, we currently know about at least two different SoCs that need
>> this. Perhaps we can extend the below list to justify
On 26 April 2017 at 10:06, Geert Uytterhoeven wrote:
> Hi Ulf,
>
> On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
>> However, we currently know about at least two different SoCs that need
>> this. Perhaps we can extend the below list to justify adding a new
>> framework/APIs. Something
Hi Ulf,
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> However, we currently know about at least two different SoCs that need
> this. Perhaps we can extend the below list to justify adding a new
> framework/APIs. Something along the lines what you propose in
Hi Ulf,
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> However, we currently know about at least two different SoCs that need
> this. Perhaps we can extend the below list to justify adding a new
> framework/APIs. Something along the lines what you propose in $subject
> patchset.
>
> 1)
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> On 25 April 2017 at 13:13, Jon Hunter wrote:
>>
>> On 28/03/17 15:13, Jon Hunter wrote:
>>> The current generic PM domain framework (GenDP) only allows a single
>>> PM domain to be associated with
On Tue, Apr 25, 2017 at 9:34 PM, Ulf Hansson wrote:
> On 25 April 2017 at 13:13, Jon Hunter wrote:
>>
>> On 28/03/17 15:13, Jon Hunter wrote:
>>> The current generic PM domain framework (GenDP) only allows a single
>>> PM domain to be associated with a given device. There are several
>>>
On 25 April 2017 at 13:13, Jon Hunter wrote:
>
> On 28/03/17 15:13, Jon Hunter wrote:
>> The current generic PM domain framework (GenDP) only allows a single
>> PM domain to be associated with a given device. There are several
>> use-cases for various system-on-chip devices
On 25 April 2017 at 13:13, Jon Hunter wrote:
>
> On 28/03/17 15:13, Jon Hunter wrote:
>> The current generic PM domain framework (GenDP) only allows a single
>> PM domain to be associated with a given device. There are several
>> use-cases for various system-on-chip devices where it is necessary
On 28/03/17 15:13, Jon Hunter wrote:
> The current generic PM domain framework (GenDP) only allows a single
> PM domain to be associated with a given device. There are several
> use-cases for various system-on-chip devices where it is necessary for
> a PM domain consumer to control more than one
On 28/03/17 15:13, Jon Hunter wrote:
> The current generic PM domain framework (GenDP) only allows a single
> PM domain to be associated with a given device. There are several
> use-cases for various system-on-chip devices where it is necessary for
> a PM domain consumer to control more than one
The current generic PM domain framework (GenDP) only allows a single
PM domain to be associated with a given device. There are several
use-cases for various system-on-chip devices where it is necessary for
a PM domain consumer to control more than one PM domain where the PM
domains:
i). Do not
The current generic PM domain framework (GenDP) only allows a single
PM domain to be associated with a given device. There are several
use-cases for various system-on-chip devices where it is necessary for
a PM domain consumer to control more than one PM domain where the PM
domains:
i). Do not
44 matches
Mail list logo