lkml.org 
[lkml]   [2020]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 3/3] leds: add sgm3140 driver
Date
Hi Dan,

On Mittwoch, 11. März 2020 14:02:44 CET Dan Murphy wrote:
> Luca
>
> On 3/9/20 3:35 PM, Luca Weiss wrote:
> > Add a driver for the SGMICRO SGM3140 Buck/Boost Charge Pump LED driver.
> >
> > This device is controlled by two GPIO pins, one for enabling and the
> > second one for switching between torch and flash mode.
>
> How does one enable torch and one enable flash?
>
> Is the flash-gpio control this or does the enable-gpio enable the flash?

Enabling torch mode means making EN pin high and FLASH pin low.
Enabling flash mode means making EN pin high and FLASH pin high.

The users of this driver can just use standard v4l2 apis or sysfs so I
wouldn't say this is relevant for the users.

>
> The DT binding did not indicate what the GPIOs are really going to control.

I'm not sure if this is relevant in the dt bindings because how the device
works is described in the datasheet and not really relevant for users of the
binding? I also didn't necessarily want to copy-paste the datasheet into the
dt bindings because of copyright.

>
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > ---
> > Changes since RFC:
> >
> > - address review comments from Jacek Anaszewski:
> > - implement strobe_get op
> > - implement timeout_set op
> > - init v4l2_sd_cfg variable
> > - remove init_data.devicename assignemnt
> > - use devm_ version of led_classdev_flash_register_ext
> > - release child_node in case of success
> >
> > drivers/leds/Kconfig | 9 ++
> > drivers/leds/Makefile | 1 +
> > drivers/leds/leds-sgm3140.c | 260 ++++++++++++++++++++++++++++++++++++
> > 3 files changed, 270 insertions(+)
> > create mode 100644 drivers/leds/leds-sgm3140.c
> >

> SNIP

> > + if (!child_node) {
> > + dev_err(&pdev->dev, "No DT child node found for
connected LED.\n");
> > + return -EINVAL;
> > + }
> > +
> > +
> > + ret = of_property_read_u32(child_node, "flash-max-timeout-us",
> > + &priv->max_timeout);
>
> Please use the device_property api's to retrieve DT settings. Then
> there is no need to release the "of" child node.
>

I'm guessing you mean

device_property_read_u32(&pdev->dev, "flash-max-timeout-us", &priv-
>max_timeout);

?

I still need the child_node for "init_data.fwnode" and v4l2_flash_init so I
still have to call of_node_put, right?

> > + if (ret < 0) {
>
> if (ret)

Ack

> SNIP

> > + /* Create V4L2 Flash subdev */
> > + priv->v4l2_flash = v4l2_flash_init(&pdev->dev,
> > of_fwnode_handle(child_node), +
fled_cdev, NULL,
> > + &v4l2_sd_cfg);
> > + if (IS_ERR(priv->v4l2_flash)) {
> > + ret = PTR_ERR(priv->v4l2_flash);
> > + goto err;
>
> Do you need to jump here? This should just fall out and go through err
> anyway.

Should I just do

if (IS_ERR(priv->v4l2_flash))
ret = PTR_ERR(priv->v4l2_flash);

?

I thought about removing the goto but I decided to keep it in case code is
added below that statement so that the goto wouldn't be forgotten. But I can
change it of course if wanted.

>
> Dan

Regards
Luca


\
 
 \ /
  Last update: 2020-03-15 11:43    [W:0.086 / U:3.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site