On Thursday 25 January 2018 09:48 PM, David Lechner wrote:
> On 01/25/2018 06:53 AM, Sekhar Nori wrote:
>> On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
>>> 2018-01-23 21:23 GMT+01:00 David Lechner :
On 01/23/2018 02:05 PM, David Lechner wrote:
>
On Thursday 25 January 2018 09:48 PM, David Lechner wrote:
> On 01/25/2018 06:53 AM, Sekhar Nori wrote:
>> On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
>>> 2018-01-23 21:23 GMT+01:00 David Lechner :
On 01/23/2018 02:05 PM, David Lechner wrote:
>
> On 01/23/2018
On 01/25/2018 06:53 AM, Sekhar Nori wrote:
On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
2018-01-23 21:23 GMT+01:00 David Lechner :
On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM,
On 01/25/2018 06:53 AM, Sekhar Nori wrote:
On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
2018-01-23 21:23 GMT+01:00 David Lechner :
On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski
2018-01-25 13:53 GMT+01:00 Sekhar Nori :
> On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
>> 2018-01-23 21:23 GMT+01:00 David Lechner :
>>> On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
2018-01-25 13:53 GMT+01:00 Sekhar Nori :
> On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
>> 2018-01-23 21:23 GMT+01:00 David Lechner :
>>> On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
>
> On 01/23/2018 01:53 PM,
On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
> 2018-01-23 21:23 GMT+01:00 David Lechner :
>> On 01/23/2018 02:05 PM, David Lechner wrote:
>>>
>>> On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
On Wednesday 24 January 2018 01:33 PM, Bartosz Golaszewski wrote:
> 2018-01-23 21:23 GMT+01:00 David Lechner :
>> On 01/23/2018 02:05 PM, David Lechner wrote:
>>>
>>> On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
>
>
> In the
2018-01-23 21:23 GMT+01:00 David Lechner :
> On 01/23/2018 02:05 PM, David Lechner wrote:
>>
>> On 01/23/2018 02:01 PM, David Lechner wrote:
>>>
>>> On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't
2018-01-23 21:23 GMT+01:00 David Lechner :
> On 01/23/2018 02:05 PM, David Lechner wrote:
>>
>> On 01/23/2018 02:01 PM, David Lechner wrote:
>>>
>>> On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but
On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but somehow the clock doesn't end up in the list of the device's
clocks - which is
On 01/23/2018 02:05 PM, David Lechner wrote:
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but somehow the clock doesn't end up in the list of the device's
clocks - which is
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but somehow the clock doesn't end up in the list of the device's
clocks - which is why it's not enabled by pm_runtime_get_sync().
On 01/23/2018 02:01 PM, David Lechner wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but somehow the clock doesn't end up in the list of the device's
clocks - which is why it's not enabled by pm_runtime_get_sync().
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
2018-01-23 20:24 GMT+01:00 David Lechner :
On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
2018-01-23 19:26 GMT+01:00 David Lechner :
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
2018-01-23 20:24 GMT+01:00 David Lechner :
On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
2018-01-23 19:26 GMT+01:00 David Lechner :
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
On Tue,
2018-01-23 20:24 GMT+01:00 David Lechner :
> On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
>>
>> 2018-01-23 19:26 GMT+01:00 David Lechner :
>>>
>>> On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam
2018-01-23 20:24 GMT+01:00 David Lechner :
> On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
>>
>> 2018-01-23 19:26 GMT+01:00 David Lechner :
>>>
>>> On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
>
>
> On Tue, Jan 23, 2018
On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
2018-01-23 19:26 GMT+01:00 David Lechner :
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner
On 01/23/2018 12:34 PM, Bartosz Golaszewski wrote:
2018-01-23 19:26 GMT+01:00 David Lechner :
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner
wrote:
On 01/23/2018 10:03 AM, David Lechner wrote:
2018-01-23 19:26 GMT+01:00 David Lechner :
> On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
>>
>> 2018-01-23 18:03 GMT+01:00 Adam Ford :
>>>
>>> On Tue, Jan 23, 2018 at 10:06 AM, David Lechner
>>> wrote:
On 01/23/2018
2018-01-23 19:26 GMT+01:00 David Lechner :
> On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
>>
>> 2018-01-23 18:03 GMT+01:00 Adam Ford :
>>>
>>> On Tue, Jan 23, 2018 at 10:06 AM, David Lechner
>>> wrote:
On 01/23/2018 10:03 AM, David Lechner wrote:
>
>
> You can see if
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
On 01/23/2018 10:03 AM, David Lechner wrote:
You can see if the clock is enabled by running:
cat
On 01/23/2018 12:10 PM, Bartosz Golaszewski wrote:
2018-01-23 18:03 GMT+01:00 Adam Ford :
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
On 01/23/2018 10:03 AM, David Lechner wrote:
You can see if the clock is enabled by running:
cat /sys/kernel/debug/clk/clk_summary
I
2018-01-23 18:03 GMT+01:00 Adam Ford :
> On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
>> On 01/23/2018 10:03 AM, David Lechner wrote:
>>>
>>> You can see if the clock is enabled by running:
>>>
>>> cat /sys/kernel/debug/clk/clk_summary
>>>
2018-01-23 18:03 GMT+01:00 Adam Ford :
> On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
>> On 01/23/2018 10:03 AM, David Lechner wrote:
>>>
>>> You can see if the clock is enabled by running:
>>>
>>> cat /sys/kernel/debug/clk/clk_summary
>>>
>>
>> I just realized if you can't boot,
2018-01-23 17:03 GMT+01:00 David Lechner :
> On 01/23/2018 08:54 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-22 18:30 GMT+01:00 David Lechner :
>>>
>>> On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David
2018-01-23 17:03 GMT+01:00 David Lechner :
> On 01/23/2018 08:54 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-22 18:30 GMT+01:00 David Lechner :
>>>
>>> On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
>
>
> This series
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
> On 01/23/2018 10:03 AM, David Lechner wrote:
>>
>> You can see if the clock is enabled by running:
>>
>> cat /sys/kernel/debug/clk/clk_summary
>>
>
> I just realized if you can't boot, you can't do this. :-/
I
On Tue, Jan 23, 2018 at 10:06 AM, David Lechner wrote:
> On 01/23/2018 10:03 AM, David Lechner wrote:
>>
>> You can see if the clock is enabled by running:
>>
>> cat /sys/kernel/debug/clk/clk_summary
>>
>
> I just realized if you can't boot, you can't do this. :-/
I can boot with the latest
On 01/23/2018 10:03 AM, David Lechner wrote:
You can see if the clock is enabled by running:
cat /sys/kernel/debug/clk/clk_summary
I just realized if you can't boot, you can't do this. :-/
On 01/23/2018 10:03 AM, David Lechner wrote:
You can see if the clock is enabled by running:
cat /sys/kernel/debug/clk/clk_summary
I just realized if you can't boot, you can't do this. :-/
On 01/23/2018 08:54 AM, Bartosz Golaszewski wrote:
2018-01-22 18:30 GMT+01:00 David Lechner :
On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock
On 01/23/2018 08:54 AM, Bartosz Golaszewski wrote:
2018-01-22 18:30 GMT+01:00 David Lechner :
On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock framework.
The series works like this, the
2018-01-22 18:11 GMT+01:00 David Lechner :
> On 01/22/2018 07:29 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-20 18:13 GMT+01:00 David Lechner :
>>>
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works like
2018-01-22 18:11 GMT+01:00 David Lechner :
> On 01/22/2018 07:29 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-20 18:13 GMT+01:00 David Lechner :
>>>
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works like this, the first 19 patches create new clock
2018-01-22 18:30 GMT+01:00 David Lechner :
> On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-20 18:13 GMT+01:00 David Lechner :
>>>
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works like
2018-01-22 18:30 GMT+01:00 David Lechner :
> On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
>>
>> 2018-01-20 18:13 GMT+01:00 David Lechner :
>>>
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works like this, the first 19 patches create new clock
On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework.
On 01/22/2018 05:14 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework. There are basically 3
On 01/22/2018 07:29 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework.
On 01/22/2018 07:29 AM, Bartosz Golaszewski wrote:
2018-01-20 18:13 GMT+01:00 David Lechner :
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework. There are basically 3
2018-01-20 18:13 GMT+01:00 David Lechner :
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of clocks -
> PLL,
2018-01-20 18:13 GMT+01:00 David Lechner :
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of clocks -
> PLL, PSC and CFGCHIP
2018-01-20 18:13 GMT+01:00 David Lechner :
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of clocks -
> PLL,
2018-01-20 18:13 GMT+01:00 David Lechner :
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of clocks -
> PLL, PSC and CFGCHIP
On Sat, Jan 20, 2018 at 11:13 AM, David Lechner wrote:
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of
On Sat, Jan 20, 2018 at 11:13 AM, David Lechner wrote:
> This series converts mach-davinci to use the common clock framework.
>
> The series works like this, the first 19 patches create new clock drivers
> using the common clock framework. There are basically 3 groups of clocks -
> PLL, PSC and
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework. There are basically 3 groups of clocks -
PLL, PSC and CFGCHIP (syscon). There are six different SoCs that each have
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 19 patches create new clock drivers
using the common clock framework. There are basically 3 groups of clocks -
PLL, PSC and CFGCHIP (syscon). There are six different SoCs that each have
50 matches
Mail list logo