Re: H2200 - Red charging LED is not working

Hello Paul,

On Monday 02 July 2007 01:21:41 Paul Sokolovsky wrote:
> Hello Gerhard,
>
> Monday, July 2, 2007, 12:26:02 AM, you wrote:
> > Hello Anton,
> >
> > I had already put a few printk lines into hamcop_base without realizing
> > that there are pr_debug statements available and I had only to define
> > DEBUG. Thank you for the tip.
>
> As Anton suggested, you need to add DEBUG to leds-hamcop.c, not
> hamcop_base.
I'm sorry for the typo in my last mail (where I wrongly stated to have set
DEBUG in hamcop_base) but yes I indeed added DEBUG to leds-hamcop.c like
Anton suggested and all of the description below is concerning that case.

>
> > The result is:
> >
> > Switching on Bluetooth gives me the lines:
> > hamcop_set_led: LED number 2, 1, 31
> > hamcop_set_led: LED number 2, 0, 0
> > The blue LED is flashing!
>
> Bluetooth LED is working just because it access hamcop in old adhoc
> way, that needs to be fixed once leds-hamcop is debugged.
>
> > Putting h2200 into craddle or give power to the plug I see that the
> > battery gets loaded but nothing happens. No LED is flashing, no dmesg
> > output is created in leds-hamcop.c.
> >
> > leds-hamcop.c seems not to be the problem.
I see that there are a lot of pr_debug statements in leds-hamcop.c but as I
told you yesterday, the above two lines are the only thing I got by switching
Bluetooth on and off. No additional lines could be found in dmesg file.

I meanwhile realize that the two lines

 hamcop_set_led: LED number 2, 1, 31
 hamcop_set_led: LED number 2, 0, 0

are printed also during reboot as the blue LED is flashing once during boot.

> Based on your report, and answering your question in another mail,
> leds-hamcop exactly appears to be a culprit. It's what registers entries
> in /sys/class/leds/. So, please debug it - there're lots of printk's
> already.

Sorry to couldn't give you more info from DEBUG output.
Gerhard
Received on Mon Jul 02 2007 - 14:02:37 EDT