From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v22 01/16] dt: bindings: Add multicolor class dt bindings documention
Date: Wed, 29 Apr 2020 11:54:25 -0500 [thread overview]
Message-ID: <8d35f760-1d32-0541-6f5d-da6ce4324f2f@ti.com> (raw)
In-Reply-To: <8991ffea-3ac6-555d-1cab-b50ec4d46372@ti.com>
Jacek
On 4/29/20 10:44 AM, Dan Murphy wrote:
> Jacek
>
> On 4/29/20 10:37 AM, Jacek Anaszewski wrote:
>> Hi Dan,
>>
>> Thanks for the conversion, but now the binding example is missing.
>> In Documentation/devicetree/bindings/leds/common.yaml we do have
>> examples.
>>
> I have looked at a few recent examples of yaml files
> (rohm,bd71828-leds and max77650) and there are no examples.
>
> I am not sure if examples are required but more of a nice to have
> especially for peripherals.
>
> But additionalProperties: false is required
>
> I can add a really basic example but I thought the intent of the
> examples was to derive a sample dts.
>
I added examples to both the multicolor yaml and the LP50xx yaml.
I will post v23 tomorrow to give this series some soak time.
Dan
> Dan
>
next prev parent reply other threads:[~2020-04-29 17:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 12:56 [PATCH v22 00/16] Multicolor Framework v22 Dan Murphy
2020-04-29 12:56 ` [PATCH v22 01/16] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2020-04-29 15:37 ` Jacek Anaszewski
2020-04-29 15:44 ` Dan Murphy
2020-04-29 16:54 ` Dan Murphy [this message]
2020-04-29 12:56 ` [PATCH v22 02/16] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2020-04-29 12:56 ` [PATCH v22 03/16] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2020-04-29 12:56 ` [PATCH v22 04/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2020-04-29 12:56 ` [PATCH v22 05/16] dt: bindings: lp55xx: Be consistent in the document with LED acronym Dan Murphy
2020-04-29 12:56 ` [PATCH v22 06/16] dt: bindings: lp55xx: Update binding for Multicolor Framework Dan Murphy
2020-04-29 12:56 ` [PATCH v22 07/16] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2020-04-29 12:56 ` [PATCH v22 08/16] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2020-04-29 12:56 ` [PATCH v22 09/16] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes Dan Murphy
2020-04-29 12:56 ` [PATCH v22 10/16] leds: lp55xx: Convert LED class registration to devm_* Dan Murphy
2020-04-29 12:56 ` [PATCH v22 11/16] leds: lp55xx: Add multicolor framework support to lp55xx Dan Murphy
2020-04-29 12:56 ` [PATCH v22 12/16] leds: lp5523: Update the lp5523 code to add multicolor brightness function Dan Murphy
2020-04-29 12:56 ` [PATCH v22 13/16] leds: lp5521: Add multicolor framework multicolor brightness support Dan Murphy
2020-04-29 12:56 ` [PATCH v22 14/16] leds: lp55xx: Fix checkpatch file permissions issues Dan Murphy
2020-04-29 12:56 ` [PATCH v22 15/16] leds: lp5523: Fix checkpatch issues in the code Dan Murphy
2020-04-29 12:56 ` [PATCH v22 16/16] dt: bindings: Update lp55xx binding to recommended LED naming Dan Murphy
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=8d35f760-1d32-0541-6f5d-da6ce4324f2f@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®