Hi Alim,
On Tuesday 05 July 2016 02:22 PM, Alim Akhtar wrote:
>
>
> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
>>> As per code flow it is possible that s3c_rtc_setfreq() might get called
>>> with rtc clock disabled and in set_freq we perform
Hi Alim,
On Tuesday 05 July 2016 02:22 PM, Alim Akhtar wrote:
>
>
> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
>>> As per code flow it is possible that s3c_rtc_setfreq() might get called
>>> with rtc clock disabled and in set_freq we perform
Hi Alim,
On Tuesday 05 July 2016 02:26 PM, Krzysztof Kozlowski wrote:
> On 07/05/2016 10:52 AM, Alim Akhtar wrote:
>>
>>
>> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
As per code flow it is possible that s3c_rtc_setfreq() might get
Hi Alim,
On Tuesday 05 July 2016 02:26 PM, Krzysztof Kozlowski wrote:
> On 07/05/2016 10:52 AM, Alim Akhtar wrote:
>>
>>
>> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
As per code flow it is possible that s3c_rtc_setfreq() might get
On 07/05/2016 10:52 AM, Alim Akhtar wrote:
>
>
> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
>>> As per code flow it is possible that s3c_rtc_setfreq() might get called
>>> with rtc clock disabled and in set_freq we perform h/w registers
>>>
On 07/05/2016 10:52 AM, Alim Akhtar wrote:
>
>
> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
>> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
>>> As per code flow it is possible that s3c_rtc_setfreq() might get called
>>> with rtc clock disabled and in set_freq we perform h/w registers
>>>
On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
On 07/04/2016 01:03 PM, Alim Akhtar wrote:
As per code flow it is possible that s3c_rtc_setfreq() might get called
with rtc clock disabled and in set_freq we perform h/w registers read/write,
which might results in a kernel crash while
On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote:
On 07/04/2016 01:03 PM, Alim Akhtar wrote:
As per code flow it is possible that s3c_rtc_setfreq() might get called
with rtc clock disabled and in set_freq we perform h/w registers read/write,
which might results in a kernel crash while
On 07/04/2016 01:03 PM, Alim Akhtar wrote:
> As per code flow it is possible that s3c_rtc_setfreq() might get called
> with rtc clock disabled and in set_freq we perform h/w registers read/write,
> which might results in a kernel crash while probing rtc driver.
> Below is one such case:
>
On 07/04/2016 01:03 PM, Alim Akhtar wrote:
> As per code flow it is possible that s3c_rtc_setfreq() might get called
> with rtc clock disabled and in set_freq we perform h/w registers read/write,
> which might results in a kernel crash while probing rtc driver.
> Below is one such case:
>
As per code flow it is possible that s3c_rtc_setfreq() might get called
with rtc clock disabled and in set_freq we perform h/w registers read/write,
which might results in a kernel crash while probing rtc driver.
Below is one such case:
s3c_rtc_probe()
clk_prepare_enable(info->rtc_clk) // rtc
As per code flow it is possible that s3c_rtc_setfreq() might get called
with rtc clock disabled and in set_freq we perform h/w registers read/write,
which might results in a kernel crash while probing rtc driver.
Below is one such case:
s3c_rtc_probe()
clk_prepare_enable(info->rtc_clk) // rtc
12 matches
Mail list logo