From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Rob Herring <robh@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chen-Yu Tsai <wens@csie.org>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: touchscreen: silead_gsl1680: Document touchscreen-fw-name
Date: Mon, 29 Aug 2016 07:18:34 +0200 [thread overview]
Message-ID: <20160829051834.GW3165@lukather> (raw)
In-Reply-To: <20160829003725.GA20749@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Hi Rob,
On Sun, Aug 28, 2016 at 07:37:25PM -0500, Rob Herring wrote:
> On Tue, Aug 23, 2016 at 05:04:48PM +0200, Hans de Goede wrote:
> > The driver has supported touchscreen-fw-name to specify the firmware to
> > load since day 0, but this was omitted from the binding, document this.
> >
> > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > ---
> > Documentation/devicetree/bindings/input/touchscreen/silead_gsl1680.txt | 1 +
> > 1 file changed, 1 insertion(+)
>
> I'd really like to deprecate in favor of a standard property name. We've
> somewhat agreed on 'firmware-name' though there is no common binding doc
> yet. But given this is in use:
This has been introduced in 4.8-rc1, so it hasn't been used in any
stable version yet, and we don't have any users in tree so far.
If you want to something else, it feels like now is the time to change
it.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-29 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:04 [PATCH] dt-bindings: touchscreen: silead_gsl1680: Document touchscreen-fw-name Hans de Goede
2016-08-29 0:37 ` Rob Herring
2016-08-29 5:18 ` Maxime Ripard [this message]
2016-08-29 9:35 ` Hans de Goede
[not found] ` <64d65f63-db47-d9c2-1c3f-cc544c2da2ab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-08-30 16:34 ` Maxime Ripard
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=20160829051834.GW3165@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wens@csie.org \
/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).