From: Pavel Machek <pavel@ucw.cz>
To: Dan Murphy <dmurphy@ti.com>
Cc: Rob Herring <robh@kernel.org>,
mark.rutland@arm.com, rpurdie@rpsys.net,
jacek.anaszewski@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: dts: fun with chip names Re: [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver
Date: Thu, 16 Nov 2017 21:11:21 +0100 [thread overview]
Message-ID: <20171116201121.GA28848@amd> (raw)
In-Reply-To: <d3483e49-650d-1d68-bec6-eeb84d8ac48a@ti.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Hi!
> >> +Required properties:
> >> + - compatible:
> >> + "ti,lm3692x"
> >
> > Don't use wildcards in compatible strings.
>
> Do you mean to remove the x? How do we denote a family of parts
> then?
I guess you should specify the exact chip.
Which will present interesting problem for me on Nokia N9/N950; in one
case, compatible chip is produced by two companies, and it looks like
some machines have one and some have the other; but we'd like to share
the dts as user has no chance telling them apart (and it is not
important, anyway).
In second case, chip is refered as APDS990X and I don't know where to
get more exact data.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-11-16 20:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 19:42 [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver Dan Murphy
2017-11-15 19:42 ` [PATCH v3 2/2] leds: lm3692x: Introduce LM3692x dual string driver Dan Murphy
2017-11-15 21:12 ` Pavel Machek
2017-11-15 21:25 ` Dan Murphy
2017-11-18 14:19 ` Jacek Anaszewski
2017-11-28 12:53 ` Dan Murphy
2017-11-15 20:15 ` [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver Jacek Anaszewski
2017-11-15 20:31 ` Dan Murphy
2017-11-15 22:23 ` Pavel Machek
2017-11-16 20:14 ` Jacek Anaszewski
2017-11-16 21:42 ` Dan Murphy
2017-11-17 2:19 ` Jingoo Han
2017-11-17 11:20 ` Pavel Machek
2017-11-17 16:30 ` Jingoo Han
2017-11-17 18:02 ` Dan Murphy
2017-11-17 23:58 ` Pavel Machek
2017-11-28 17:27 ` Dan Murphy
2017-11-16 15:41 ` Rob Herring
2017-11-16 15:45 ` Dan Murphy
2017-11-16 15:58 ` Rob Herring
2017-11-16 20:11 ` Pavel Machek [this message]
2017-11-16 20:36 ` dts: fun with chip names " Rob Herring
2017-11-16 21:40 ` Dan Murphy
2017-11-18 14:19 ` Jacek Anaszewski
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=20171116201121.GA28848@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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