Query about vexpress_ct_ca9x4 watchdog issue ?

Query about vexpress_ct_ca9x4 watchdog issue ?

[bill]

Hi viresh and arm guys:)

I am testing sp805 watchdog at vexpress board.

After open /dev/watchdog , I use WDIOC_GETTIMELEFT ioctl to get the time left for rebooting in a loop;
while the timeleft is not decrementing, but stay as a constant 59s.

I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 

WdogValue     --> 0xf0918000
WdogControl   -->0x3


It seems the value is correct, but watchdog is not triggered.
I am really puzzled about this, can you give me some clue to find the root cause?


thanks


bill

Query about vexpress_ct_ca9x4 watchdog issue ?

[viresh kumar]

On 04/20/2011 07:37 AM, bill wrote:
> Hi viresh and arm guys:)
> 
> I am testing sp805 watchdog at vexpress board.
> 
> After open /dev/watchdog , I use WDIOC_GETTIMELEFT ioctl to get the time left for rebooting in a loop;
> while the timeleft is not decrementing, but stay as a constant 59s.
> 
> I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 
> 
> WdogValue     --> 0xf0918000
> WdogControl   -->0x3
> 
> 
> It seems the value is correct, but watchdog is not triggered.
> I am really puzzled about this, can you give me some clue to find the root cause?
> 

Hi Bill,

It looks that you are also not getting WDT reset after specified timeout? Is it so?
So, probably driver is fine as it is tested on SPEAr.

Probably the issue might be with clock rate and clock enable. What is the clock rate
for wdt in your platform?
Driver calls clk_enable() and clk_get_rate(). Can you please verify that this is
working correctly.

-- 
viresh

Query about vexpress_ct_ca9x4 watchdog issue ?

[bill]

At 2011-04-20 12:37:03?"viresh kumar" <viresh.kumar@st.com> wrote:

>On 04/20/2011 07:37 AM, bill wrote:
>> Hi viresh and arm guys:)
>> 
>> I am testing sp805 watchdog at vexpress board.
>> 
>> After open /dev/watchdog , I use WDIOC_GETTIMELEFT ioctl to get the time left for rebooting in a loop;
>> while the timeleft is not decrementing, but stay as a constant 59s.
>> 
>> I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 
>> 
>> WdogValue     --> 0xf0918000
>> WdogControl   -->0x3
>> 
>> 
>> It seems the value is correct, but watchdog is not triggered.
>> I am really puzzled about this, can you give me some clue to find the root cause?
>> 
>
>Hi Bill,
>
>It looks that you are also not getting WDT reset after specified timeout? Is it so?
>So, probably driver is fine as it is tested on SPEAr.
>

I have test this driver on SPEAr1310 with drivers/watchdog/coh901327_wdt.c
after open /dev/watchdog, console hanged after a while ,
but the system does not reboot as expected.


>Probably the issue might be with clock rate and clock enable. What is the clock rate
>for wdt in your platform?
>Driver calls clk_enable() and clk_get_rate(). Can you please verify that this is
>working correctly.
>


I did check the clock issue, current mach-vexpress use plat-versatile clock implementation
in plat-versatile/clock.c clk_enable is an empty function;
so I guess we don't need any clock gating function in mach-vexpress.

thanks

bill


>-- 
>viresh
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Query about vexpress_ct_ca9x4 watchdog issue ?

[viresh kumar]

On 04/20/2011 12:16 PM, bill wrote:
> At 2011-04-20 12:37:03?"viresh kumar" <viresh.kumar@st.com> wrote:
>> On 04/20/2011 07:37 AM, bill wrote:
>>> I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 
>>>
>>> WdogValue     --> 0xf0918000
>>> WdogControl   -->0x3
>>>
>>>
>>> It seems the value is correct, but watchdog is not triggered.
>>> I am really puzzled about this, can you give me some clue to find the root cause?
>>>
>>
>> Hi Bill,
>>
>> It looks that you are also not getting WDT reset after specified timeout? Is it so?
>> So, probably driver is fine as it is tested on SPEAr.
>>
> 
> I have test this driver on SPEAr1310 with drivers/watchdog/coh901327_wdt.c

Sorry i got confused here. Which driver did you test coh901327_wdt.c or SP805.
1310 doesn't have 805, neither have coh901327_wdt. It has cortex watchdog, for which
support is not added for spear.

coh901327_wdt.c is for ST Ericsson's U300 soc.


>> Probably the issue might be with clock rate and clock enable. What is the clock rate
>> for wdt in your platform?
>> Driver calls clk_enable() and clk_get_rate(). Can you please verify that this is
>> working correctly.
>>
> 
> 
> I did check the clock issue, current mach-vexpress use plat-versatile clock implementation
> in plat-versatile/clock.c clk_enable is an empty function;
> so I guess we don't need any clock gating function in mach-vexpress.

The only thing i can think of is clock, as wdt_value is not at all decrementing.

--
viresh

Query about vexpress_ct_ca9x4 watchdog issue ?

[bill]

        





At 2011-04-20 15:16:47?"viresh kumar" <viresh.kumar@st.com> wrote:

>On 04/20/2011 12:16 PM, bill wrote:
>> At 2011-04-20 12:37:03?"viresh kumar" <viresh.kumar@st.com> wrote:
>>> On 04/20/2011 07:37 AM, bill wrote:
>>>> I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 
>>>>
>>>> WdogValue     --> 0xf0918000
>>>> WdogControl   -->0x3
>>>>
>>>>
>>>> It seems the value is correct, but watchdog is not triggered.
>>>> I am really puzzled about this, can you give me some clue to find the root cause?
>>>>
>>>
>>> Hi Bill,
>>>
>>> It looks that you are also not getting WDT reset after specified timeout? Is it so?
>>> So, probably driver is fine as it is tested on SPEAr.
>>>
>> 
>> I have test this driver on SPEAr1310 with drivers/watchdog/coh901327_wdt.c
>
>Sorry i got confused here. Which driver did you test coh901327_wdt.c or SP805.
>1310 doesn't have 805, neither have coh901327_wdt. It has cortex watchdog, for which
>support is not added for spear.
>
>coh901327_wdt.c is for ST Ericsson's U300 soc.
>
>

I miss type the file name, it's cortexa9_wdt.c that I used test on SPEAr1310.
this file was rename with sp805_wdt.c in new kernel version.



>>> Probably the issue might be with clock rate and clock enable. What is the clock rate
>>> for wdt in your platform?
>>> Driver calls clk_enable() and clk_get_rate(). Can you please verify that this is
>>> working correctly.
>>>
>> 
>> 
>> I did check the clock issue, current mach-vexpress use plat-versatile clock implementation
>> in plat-versatile/clock.c clk_enable is an empty function;
>> so I guess we don't need any clock gating function in mach-vexpress.
>
>The only thing i can think of is clock, as wdt_value is not at all decrementing.
>
>--
>viresh
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Query about vexpress_ct_ca9x4 watchdog issue ?

[viresh kumar]

On 04/20/2011 12:57 PM, bill wrote:
>> Sorry i got confused here. Which driver did you test coh901327_wdt.c or SP805.
>> >1310 doesn't have 805, neither have coh901327_wdt. It has cortex watchdog, for which
>> >support is not added for spear.
>> >
>> >coh901327_wdt.c is for ST Ericsson's U300 soc.
>> >
>> >
> I miss type the file name, it's cortexa9_wdt.c that I used test on SPEAr1310.
> this file was rename with sp805_wdt.c in new kernel version.
> 

No. This is wrong.
There is no driver in kernel with name cortexa9_wdt.c. I sent patch for it once
but it never made through, and so we aren't supporting wdt for 1310 in mainline at all.

sp805 was present in spear3xx & 6xx.

What do you want to test sp805 or cortexa9_wdt???

-- 
viresh

Query about vexpress_ct_ca9x4 watchdog issue ?

[bill]

t 2011-04-20 16:09:26?"viresh kumar" <viresh.kumar@st.com> wrote:

>On 04/20/2011 12:57 PM, bill wrote:
>>> Sorry i got confused here. Which driver did you test coh901327_wdt.c or SP805.
>>> >1310 doesn't have 805, neither have coh901327_wdt. It has cortex watchdog, for which
>>> >support is not added for spear.
>>> >
>>> >coh901327_wdt.c is for ST Ericsson's U300 soc.
>>> >
>>> >
>> I miss type the file name, it's cortexa9_wdt.c that I used test on SPEAr1310.
>> this file was rename with sp805_wdt.c in new kernel version.
>> 
>
>No. This is wrong.
>There is no driver in kernel with name cortexa9_wdt.c. I sent patch for it once
>but it never made through, and so we aren't supporting wdt for 1310 in mainline at all.
>
>sp805 was present in spear3xx & 6xx.
>
>What do you want to test sp805 or cortexa9_wdt???

Oh, sorry for that.

I want to test sp805 on mach-vexpress.

thanks
bill

>
>-- 
>viresh
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Query about vexpress_ct_ca9x4 watchdog issue ?

[viresh kumar]

On 04/20/2011 01:52 PM, bill wrote:
>> >What do you want to test sp805 or cortexa9_wdt???
> Oh, sorry for that.
> 
> I want to test sp805 on mach-vexpress.
> 

Ok. So, this is what i said earlier.
sp805 driver is working fine on spear3xx & 6xx.
It looks that you are also not getting WDT reset after specified timeout? Is it so?

The only thing i can think of now is clock.
Can you simply program wdt using some debugger instead of driver and see if reset is
happening??

--
viresh

Query about vexpress_ct_ca9x4 watchdog issue ?

[bill]

At 2011-04-20 16:27:56?"viresh kumar" <viresh.kumar@st.com> wrote:

>On 04/20/2011 01:52 PM, bill wrote:
>>> >What do you want to test sp805 or cortexa9_wdt???
>> Oh, sorry for that.
>> 
>> I want to test sp805 on mach-vexpress.
>> 
>
>Ok. So, this is what i said earlier.
>sp805 driver is working fine on spear3xx & 6xx.
>It looks that you are also not getting WDT reset after specified timeout? Is it so?
>

yes, WDT does not trigger any interrupt/reset signal after specified timeout.


>The only thing i can think of now is clock.
>Can you simply program wdt using some debugger instead of driver and see if reset is
>happening??
>

yes ,I can try it using some usefull command in Uboot.



>--
>viresh
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel