Hello,
I am developping an embedded system based on a ARM PXA270. I am using 2.6.27
kernel.
I have developped a tiny led driver for my embedded kernel based on leds class.
My driver is almost identical as the leds-cm-x270.c driver. When I insert my
driver in the kernel the probe function is
PAtrick Gerber wrote:
Hello,
I am developping an embedded system based on a ARM PXA270. I am using 2.6.27
kernel.
I have developped a tiny led driver for my embedded kernel based on leds
class. My driver is almost identical as the leds-cm-x270.c driver. When I
insert my driver in the
PAtrick Gerber, 03.02.2009:
Hello,
I am developping an embedded system based on a ARM PXA270. I am using
2.6.27 kernel.
I have developped a tiny led driver for my embedded kernel based on
leds class. My driver is almost identical as the leds-cm-x270.c
This driver has been removed after
Probably the driver/device name mismatch which has for
effect that driver probe function is not being called.
Can you post your driver for us to see what you
did/are missing?
With pleasure, see the attached code.
Patrick
leds-colibri.c
Description: Binary data
Maybe you don't need to write a driver at all and can use the leds-gpio
driver as well?
Do you have an example ?
Have you adjusted your board code? You have to add a struct
platform_device, so that the kernel knows that and on which pins you
have LEDs.
No, I was thinking that the struct
PAtrick Gerber, 03.02.2009:
Maybe you don't need to write a driver at all and can use the leds-gpio
driver as well?
Do you have an example ?
No, but I'm sure you can find examples in the source tree.
Have you adjusted your board code? You have to add a struct
platform_device, so that the
