From: Dmitry Torokhov <dtor@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Guenter Roeck <linux@roeck-us.net>,
Nick Crews <ncrews@chromium.org>,
enric.balletbo@collabora.com, Benson Leung <bleung@chromium.org>,
linux-leds@vger.kernel.org, jacek.anaszewski@gmail.com,
alexandre.belloni@bootlin.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
dlaurie@chromium.org, sjg@google.com,
Guenter Roeck <groeck@google.com>
Subject: Re: [PATCH v5 2/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support
Date: Sun, 7 Apr 2019 15:26:58 -0700 [thread overview]
Message-ID: <CAE_wzQ_5Ha6hNt28_+j-pF3mAdXXifv9CuotDCeXff8KC1DNmA@mail.gmail.com> (raw)
In-Reply-To: <20190407221846.GB6327@amd>
On Sun, Apr 7, 2019 at 3:18 PM Pavel Machek <pavel@ucw.cz> wrote:
>
>
> > > > This document also states "The naming scheme above leaves scope
> > > > for further attributes should they be needed". It does not permit,
> > > > however, to redefine one of the fields to mean "location", much less
> > > > the declaration that a devicename of "platform" shall refer to an
> > > > "internal" backlight, or that there shall be no more than one
> > > > "internal" backlight in a given system.
> > >
> > > "platform" is as good devicename as "wilco" or "chromeos".
> >
> > No, because "platform" is not a device, it is something that you are
> > trying to assign a magic meaning to.
>
> "chromeos" is not a device, either.
I agree, it is not a device name. We do not assign any specific
meaning to it though. We could change it to "cros_ec" if so desired
and nothing should break.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-04-07 22:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 17:10 [PATCH v5 1/3] platform/chrome: wilco_ec: Standardize mailbox interface Nick Crews
2019-04-04 17:10 ` [PATCH v5 2/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support Nick Crews
2019-04-04 19:52 ` Pavel Machek
2019-04-05 20:15 ` Guenter Roeck
2019-04-06 8:41 ` Pavel Machek
2019-04-07 21:46 ` Dmitry Torokhov
2019-04-07 22:18 ` Pavel Machek
2019-04-07 22:26 ` Dmitry Torokhov [this message]
2019-04-08 9:41 ` Keyboard backlight LED naming was " Pavel Machek
2019-04-08 13:31 ` Guenter Roeck
2019-04-04 17:10 ` [PATCH v5 3/3] platform/chrome: Standardize Chrome OS keyboard backlight name Nick Crews
2019-04-04 17:36 ` Guenter Roeck
2019-04-04 17:43 ` Dmitry Torokhov
2019-04-04 18:41 ` Nick Crews
2019-04-04 18:55 ` Dmitry Torokhov
2019-04-04 18:59 ` Pavel Machek
2019-04-04 19:05 ` Dmitry Torokhov
2019-04-04 19:19 ` Pavel Machek
2019-04-04 19:59 ` Dmitry Torokhov
2019-04-04 20:06 ` Pavel Machek
2019-04-04 20:13 ` Dmitry Torokhov
2019-04-04 20:20 ` Pavel Machek
2019-04-04 20:26 ` Dmitry Torokhov
2019-04-04 20:42 ` Pavel Machek
2019-04-04 21:48 ` Dmitry Torokhov
2019-04-04 22:05 ` Pavel Machek
2019-04-04 22:42 ` Guenter Roeck
2019-04-05 8:42 ` Enric Balletbo i Serra
2019-04-05 20:00 ` Jacek Anaszewski
2019-04-06 9:53 ` Pavel Machek
2019-04-06 14:15 ` Jacek Anaszewski
2019-04-06 22:17 ` Pavel Machek
2019-04-07 22:01 ` Dmitry Torokhov
2019-04-08 20:01 ` Jacek Anaszewski
2019-04-04 18:56 ` Pavel Machek
2019-04-08 23:58 ` Nick Crews
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=CAE_wzQ_5Ha6hNt28_+j-pF3mAdXXifv9CuotDCeXff8KC1DNmA@mail.gmail.com \
--to=dtor@google.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=bleung@chromium.org \
--cc=dlaurie@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@google.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ncrews@chromium.org \
--cc=pavel@ucw.cz \
--cc=sjg@google.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;
as well as URLs for NNTP newsgroup(s).