From: Josh Cartwright <joshc@ni.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] led/led-class: Handle LEDs with the same name
Date: Thu, 19 Feb 2015 17:15:58 -0600 [thread overview]
Message-ID: <20150219231558.GA30417@jcartwri.amer.corp.natinst.com> (raw)
In-Reply-To: <CAK5ve-LNgZpUKhwe8jOPeipWDg7pv8ruQ9SSbjDmyUDDdbi04w@mail.gmail.com>
On Tue, Feb 17, 2015 at 04:52:45PM -0800, Bryan Wu wrote:
> On Tue, Feb 17, 2015 at 4:32 PM, Ricardo Ribalda Delgado
[..]
> > Then we have TWO gpios chip. Each of them have a led named red. When
> > the second gpio-led is probed we have an error. Everything else
> > (address offset, phandle, device renaming) is handled properly already
> > by the kernel.
> >
> > On this system I cannot control card.dtb, or which type of cards will
> > the user connect to the system. The DT is generated in run-time based
> > on the hardware connected to the pci slots.
> >
> So you're supposed to get 2 card.dtb files for 2 PCI cards, right?
> They should be different and you need to choose different name for the
> hardware.
Is this solvable by adding support for led properties in an aliases { }
node? I suppose that would mean you'd need to also overlay a selection
of which LED is "red", but I don't know if that is a problem.
Josh
next prev parent reply other threads:[~2015-02-19 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 12:26 Ricardo Ribalda Delgado
2015-02-12 19:48 ` Bryan Wu
2015-02-12 20:45 ` Ricardo Ribalda Delgado
2015-02-13 10:11 ` Ricardo Ribalda Delgado
2015-02-17 22:34 ` Bryan Wu
2015-02-17 22:54 ` Ricardo Ribalda Delgado
2015-02-17 23:35 ` Bryan Wu
2015-02-17 23:47 ` Ricardo Ribalda Delgado
2015-02-17 23:59 ` Bryan Wu
2015-02-18 0:32 ` Ricardo Ribalda Delgado
2015-02-18 0:52 ` Bryan Wu
2015-02-18 1:11 ` Ricardo Ribalda Delgado
2015-02-18 1:36 ` Bryan Wu
2015-02-18 6:55 ` Ricardo Ribalda Delgado
2015-02-19 19:12 ` Bryan Wu
2015-02-19 22:59 ` Ricardo Ribalda Delgado
2015-02-19 23:15 ` Josh Cartwright [this message]
2015-02-19 23:22 ` Ricardo Ribalda Delgado
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=20150219231558.GA30417@jcartwri.amer.corp.natinst.com \
--to=joshc@ni.com \
--cc=cooloney@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=ricardo.ribalda@gmail.com \
--cc=robh+dt@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®