From: Pavel Machek <pavel@ucw.cz>
To: anish kumar <yesanishhere@gmail.com>
Cc: anishkmr@amazon.com, dmurphy@ti.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org,
Karthik Poduval <kpoduval@lab126.com>,
Yue Hu <yhuamzn@amazon.com>
Subject: Re: [PATCH] leds: driver for O2 Micro LED IC
Date: Fri, 8 Nov 2024 11:13:53 +0100 [thread overview]
Message-ID: <Zy3kYZM0zYIpNcqS@duo.ucw.cz> (raw)
In-Reply-To: <CABCoZhDAg1LfUZ1XCTFkR=TbHEUn=yOQRqrugzDK5Apge3JVPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Wed 2024-11-06 14:03:24, anish kumar wrote:
> On Wed, Nov 6, 2024 at 9:49 AM Pavel Machek <pavel@ucw.cz> wrote:
> >
> > Hi!
> >
> > > +++ b/Documentation/devicetree/bindings/leds/leds-ozl003.txt
> > > @@ -0,0 +1,23 @@
> > > +*O2 Micro Compact LED Strobe Light Controller
> > > +
> > > +Compact LED strobe light controller, can be controlled by I2C or via a
> > > +PWM gpio controlled.
> > > +
> > > +Required properties:
> > > +- compatible : "o2micro,ozl003"
> >
> > o2micro needs to be registered as a prefix somewhere.
>
> Wondering if adding hereDocumentation/devicetree/bindings/vendor-prefixes.yaml
> not sufficient? I added that in the same patch though, I guess
> I will have to split the patch to add that first and then the
> driver.
Doing that in same patch is ok, sorry if I missed that.
BR,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-11-08 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:54 [PATCH] leds: driver for O2 Micro LED IC anishkmr
2024-11-06 10:46 ` Krzysztof Kozlowski
2024-11-06 15:48 ` anish kumar
2024-11-06 17:49 ` Pavel Machek
2024-11-06 22:03 ` anish kumar
2024-11-08 10:13 ` Pavel Machek [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=Zy3kYZM0zYIpNcqS@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=anishkmr@amazon.com \
--cc=dmurphy@ti.com \
--cc=kpoduval@lab126.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=yesanishhere@gmail.com \
--cc=yhuamzn@amazon.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