leds-gpio: no GPIO labels (in debugfs)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I jut noticed that the used GPIOs for leds-gpio do not have an actual label 
which is visible in debugfs (/sys/kernel/debug/gpio):
> gpiochip4: GPIOs 368-383, parent: spi/spi0.2, mcp23s17, can sleep:
>  gpio-369 P0.1 (?           ) out hi
>  gpio-370 P0.2 (?           ) out lo
>  gpio-371 P0.3 (?           ) out lo
>  gpio-372 P0.4 (?           ) out lo
>  gpio-373 P0.5 (?           ) out lo
>  gpio-374 P0.6 (?           ) out lo

The reason is that the call to devm_get_gpiod_from_child() in 
gpio_leds_create() eventually calls "gpiod_request(desc, NULL);" in 
fwnode_get_named_gpiod. So no label attached to GPIO, hence "?" output.

As we have already a gpiod in create_gpio_led(), devm_gpio_request_one() with 
the proper label is not called.
I don't know much of that code, so what would be needed to have a proper GPIO 
label? And how?

Best regards,
Alexander Stein
-- 
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
alexander.stein@xxxxxxxxxxxxxxxxxxxxx

Legal and Commercial Address:
Am Windrad 2
08468 Heinsdorfergrund
Germany

Office: +49 (0) 3765 38600-0
Fax:    +49 (0) 3765 38600-4100
 
Managing Directors:
	Director Technology/CEO: Dipl.-Phys. Siegmar Schmidt;
	Director Commercial Affairs/COO: Dipl. Ing. (FH) Armin von Collrepp
Commercial Registry:
	Amtsgericht Chemnitz, HRB 28082; USt.-Id Nr. DE150534010

--
To unsubscribe from this list: send the line "unsubscribe linux-leds" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux