From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-bindings: touchscreen: silead_gsl1680: Document touchscreen-fw-name
Date: Tue, 30 Aug 2016 18:34:10 +0200 [thread overview]
Message-ID: <20160830163410.GI18605@lukather> (raw)
In-Reply-To: <64d65f63-db47-d9c2-1c3f-cc544c2da2ab@redhat.com>
On Mon, Aug 29, 2016 at 11:35:47AM +0200, Hans de Goede wrote:
> Hi,
>
> On 29-08-16 07:18, Maxime Ripard wrote:
> >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.
>
> Ack, I can still change it to firmware-name if you want (Maxime has not yet
> merged any dts changes using the touchscreen-fw-name). We should probably
> also decide if the silead/ prefix we're using (so the firmware files are
> /lib/firmware/silead/foo.fw under Linux) goes into the firmware-name
> property as my current wip code is doing, or if we put the "silead/"
> part in the driver and only put the part after it in the property.
>
> I've a feeling that just putting only the base filename (so no "silead/"
> prefix) in the property is best.
Yes, I would agree too.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160830/c9e82411/attachment.sig>
prev parent reply other threads:[~2016-08-30 16:34 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
2016-08-29 9:35 ` Hans de Goede
2016-08-30 16:34 ` Maxime Ripard [this message]
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=20160830163410.GI18605@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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