From: Andrea Scian - DAVE Embedded Systems <andrea.scian@dave.eu>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: about pca955x led driver gpio management
Date: Wed, 25 Oct 2017 00:36:04 +0200 [thread overview]
Message-ID: <7c7304df-9a08-4343-8c73-da2d54436d77@dave.eu> (raw)
In-Reply-To: <36851faf-6236-3717-f75d-cbec9bded7b7@kaod.org>
Il 24/10/2017 07:51, Cédric Le Goater ha scritto:
> On 10/17/2017 11:16 AM, Andrea Scian - DAVE Embedded Systems wrote:
>>
>>> On 10/17/2017 10:20 AM, Andrea Scian - DAVE Embedded Systems wrote:
>>>>
>>>> Il 17/10/2017 10:18, Cédric Le Goater ha scritto:
>>>>> On 10/17/2017 09:36 AM, Andrea Scian - DAVE Embedded Systems wrote:
>>>>>> Dear all,
>>>>>>
>>>>>> I'm working on an iMX6 based board with a PCA9555 which is used both to drive LEDs and manage some GPIOs.
>>>>> The PCA9555 chip and the PCA955[0-3] chips have different control
>>>>> registers. You need a different led driver for it.
>>>>
>>>> My typo sorry, as you can see in the device tree below, I'm using pca9551
>>>
>>> ok.
>>>
>>> You might want to take a look at how we mixed gpios and leds on the witherspoon
>>> system using pca9552 chips. we added a gpio-leds binding.
>>>
>>> https://github.com/openbmc/linux/blob/dev-4.10/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
>>
>> understood: you configure all pins of PCA955x as GPIOs and the map the one you need as led with gpio-leds binding.
>
> Sorry I got distracted.
>
>> However to me this is a kind of workaround or, at least, there's nothing about this limitation into the devicetree binding (in fact, IMHO, the device tree binding example will just fail)
>
> euh ? what do you mean. There is a real system using this device tree.
> I think we would know about it if it didn't work. Please explain
>
I mean that, for what I understand, your configuration is working
because all pin of 9551 are configured as GPIOs (and the binded back as led)
In my configuration I have some pins configured as led and some as
GPIOs, and this is not working.
>> I wrote the attached patch which should fix the issue and allow a more generic approach. WDYT?
>>
>> (in case it looks good, I'll send the patch in the correct way)
>
> Please send the patch to discuss, add Andrew Jeffery <andrew@aj.id.au>
> in cc:
>
Sorry for the delay but I'm busy in Prague with OSSummit and ELCE. I'll
send a proper patch and more comments, if needed, by the begin of next week.
(BTW, if some of you are here, drop me a line and have a beer together!
;-) )
next prev parent reply other threads:[~2017-10-24 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 7:36 Andrea Scian - DAVE Embedded Systems
2017-10-17 8:18 ` Cédric Le Goater
2017-10-17 8:20 ` Andrea Scian - DAVE Embedded Systems
2017-10-17 8:52 ` Cédric Le Goater
2017-10-17 9:16 ` Andrea Scian - DAVE Embedded Systems
2017-10-23 19:12 ` Jacek Anaszewski
2017-10-24 5:51 ` Cédric Le Goater
2017-10-24 22:36 ` Andrea Scian - DAVE Embedded Systems [this message]
2017-10-25 8:18 ` Cédric Le Goater
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=7c7304df-9a08-4343-8c73-da2d54436d77@dave.eu \
--to=andrea.scian@dave.eu \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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
all inboxes | Powered by JetHome®