public inbox for linux-leds@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Cc: pavel@ucw.cz, dmurphy@ti.com, linux-leds@vger.kernel.org
Subject: Re: Leds-gpio discarding the entries in /sys/class/leds : Linux 5.4.38
Date: Sun, 21 Jun 2020 23:42:57 +0200	[thread overview]
Message-ID: <4b7e95e5-0889-1502-2f0b-796874f90083@gmail.com> (raw)
In-Reply-To: <6644A4B6-E6DA-413B-97CA-1E4D199D52CE@linux.vnet.ibm.com>

Hi Vishwanatha,

On 6/20/20 7:25 PM, Vishwanatha Subbanna wrote:
> Hi Jacek,
> 
> Thank you very much for the quick response. Greatly appreciate that.

You're welcome.

>> On 20-Jun-2020, at 3:27 AM, Jacek Anaszewski <jacek.anaszewski@gmail.com> wrote:
>>
>> Hi Vishwanatha,
>>
>> Please refer to Documentation/devicetree/bindings/leds/leds-pca955x.txt.
>>
>> At first glance I don't get why you have gpio-leds node, which is for
>> leds-gpio driver.
> 
> Not sure I understood it right.. But if you are asking me why I have "leds {"  and “gpio-leds” in there, then it is to get the entries in /sys/class/leds.
> The GPIOs from PCA9552 are connected to LED. Also, that is how we have had in the past, and that worked.
> 
> Example: https://github.com/openbmc/linux/blob/dev-5.4/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts#L115

Thanks. Yeah, that looks OK, I had to take closer look at the driver.

> The problem I am running into is for : https://github.com/openbmc/linux/blob/dev-5.4/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts
> 
>>
>> On 6/19/20 3:34 PM, Vishwanatha Subbanna wrote:
>>> Hello,
>>> I am Vishwanath, working with IBM and looking for your help on one of the issues that I am running into. Would really appreciate help on this. I run Linux 5.4.38
>>> I have 2 number of PCA9552 chips, one on the Planar and other on the card that is optionally pluggable. The optional card must be plugged prior to booting and is not hot pluggable. In my experiment, I am running *without* the optional card plugged in.
>>> In the device tree, I have a "leds {" section that looks like below for the PCA9552 that is on the planar and everything works fine and I can see /sys/class/leds/fan0
>>>   leds {
>>>          compatible = "gpio-leds”;
>>>          fan0 {
>>>              retain-state-shutdown;
>>>              default-state = "keep";
>>>              gpios = <&pca0 0 GPIO_ACTIVE_LOW>;
>>>          };
>>> };
>>> &i2c7 {
>>>      status = "okay”;
>>>      pca0: pca9552@61 {
>>>         compatible = "nxp,pca9552";
>>>          reg = <0x61>;
>>>          #address-cells = <1>;
>>>          #size-cells = <0>;
>>>          gpio-controller;
>>>          #gpio-cells = <2>;
>>>          gpio@0 {
>>>              reg = <0>;
>>>              type = <PCA955X_TYPE_GPIO>;
>>>       	};
>>>      };
>>> };
>>> Similarly, if I update the device tree entry for PCA9552 for the card that is optionally pluggable, then I don’t see any leds entries in /sys/class/leds.
>>
>> Please share your DT node after the update.
>>
> 
> Pasting the GPIO_0 entry only here for brevity.
> 
> leds {
>          compatible = "gpio-leds”;
> 
>          fan0 {
>              retain-state-shutdown;
>              default-state = "keep";
>              gpios = <&pca0 0 GPIO_ACTIVE_LOW>;
>          };
> 
>          nvmeslot0 {
>              retain-state-shutdown;
>              default-state = "keep";
>              gpios = <&pca1 0 GPIO_ACTIVE_LOW>;
>          };
> };
> 
> &i2c7 {
>      status = "okay”;
>      pca0: pca9552@61 {
>         compatible = "nxp,pca9552";
>          reg = <0x61>;
>          #address-cells = <1>;
>          #size-cells = <0>;
>          gpio-controller;
>          #gpio-cells = <2>;
> 
>          gpio@0 {
>              reg = <0>;
>              type = <PCA955X_TYPE_GPIO>;
>       	};
>      };
> };
> 
> &i2c13
> {
>      pca1: pca9552@60 {
>         compatible = "nxp,pca9552";
>         reg = <0x60>;
>         #address-cells = <1>;
>         #size-cells = <0>;
> 
>         gpio-controller;
>         #gpio-cells = <2>;
> 
>         gpio@0 {
>             reg = <0>;
>             type = <PCA955X_TYPE_GPIO>;
>         };
>      };
> };
> 
> Thanks
> !! Vishwa !!
> 
>>> I don’t even see “fan0” that is on the PCA9552 on planar also. I was expecting that I should see “/sys/class/leds/fan0”.
>>> However, I could see all the entries in “/proc/device-tree/leds”.
>>> Data from the failure.
>>> [    7.895757] leds-pca955x 7-0061: leds-pca955x: Using pca9552 16-bit LED driver at slave address 0x61
>>> [    7.907659] leds-pca955x 7-0061: gpios 168...183

It is weird that you don't see "fan0" LED since this gpio seems to have
been properly registered according to this log.

>>> [    7.913012] leds-pca955x 13-0060: leds-pca955x: Using pca9552 16-bit LED driver at slave address 0x60
>>> [    7.923486] leds-pca955x 13-0060: pca955x_write_pwm: reg 0x0, val 0x80, err -6

This indicates the problem with finding pca955x device at address 0x60
on I2C bus connected to the I2C controller labelled as i2c13.

There are two options:
1) There is a problem with a physical connection with the chip on the
    card
2) You mismatched the I2C controller with the bus that controls the card

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2020-06-21 21:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 13:34 Leds-gpio discarding the entries in /sys/class/leds : Linux 5.4.38 Vishwanatha Subbanna
2020-06-19 21:57 ` Jacek Anaszewski
2020-06-20 17:25   ` Vishwanatha Subbanna
2020-06-21 21:42     ` Jacek Anaszewski [this message]
2020-06-22  6:58       ` Vishwanatha Subbanna
2020-06-22 10:54         ` Jacek Anaszewski
2020-06-22 11:01           ` Jacek Anaszewski
2020-06-26 13:04             ` Vishwanatha Subbanna
2020-06-22 11:07           ` Vishwanatha Subbanna
2020-06-22 11:36             ` Jacek Anaszewski
     [not found]               ` <F6E7B2CD-3871-4C41-A7F0-8A77E824D155@linux.vnet.ibm.com>
2020-06-22 18:13                 ` Vishwanatha Subbanna
2020-06-22 20:08                 ` Jacek Anaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b7e95e5-0889-1502-2f0b-796874f90083@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=dmurphy@ti.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=vishwa@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox