From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: pavel@ucw.cz, lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
hns@goldelico.com
Subject: Re: [PATCH 2/2] leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver
Date: Thu, 6 Apr 2023 13:43:14 +0200 [thread overview]
Message-ID: <20230406134314.25f8d3a0@aktux> (raw)
In-Reply-To: <7d8c558f-0d21-91ed-ecd0-cac079d366ee@gmail.com>
Hi Matti,
thanks for the review:
On Thu, 6 Apr 2023 11:57:15 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> > + priv->regmap = devm_regmap_init_i2c(client, &bd2606mvv_regmap);
> > + if (IS_ERR(priv->regmap)) {
> > + err = PTR_ERR(priv->regmap);
> > + dev_err(dev, "Failed to allocate register map: %d\n", err);
> > + return err;
> > + }
> > +
> > + i2c_set_clientdata(client, priv);
> > +
>
> The IC seems to have an enable pin. I think you might add the
> enable-gpio in dt-bindings and try to (optionally) get and enable it here.
It has an enable pin. I would prefer to just have the binding as complete as
possible and have it added later in the driver by someone needing it
since I cannot test that.
Regards,
Andreas
next prev parent reply other threads:[~2023-04-06 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 6:08 [PATCH 0/2] leds: Add a driver for the BD2606MVV Andreas Kemnade
2023-04-06 6:08 ` [PATCH 1/2] dt-bindings: leds: ROHM BD2606MVV LED driver Andreas Kemnade
2023-04-06 8:32 ` Matti Vaittinen
2023-04-06 11:33 ` Andreas Kemnade
2023-04-06 12:16 ` Matti Vaittinen
2023-04-06 6:08 ` [PATCH 2/2] leds: bd2606mvv: Driver for the Rohm 6 Channel i2c " Andreas Kemnade
2023-04-06 8:57 ` Matti Vaittinen
2023-04-06 11:43 ` Andreas Kemnade [this message]
2023-04-06 12:17 ` Matti Vaittinen
2023-04-06 19:45 ` Andreas Kemnade
2023-04-07 9:56 ` Matti Vaittinen
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=20230406134314.25f8d3a0@aktux \
--to=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@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