[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vfsz6KPgHbttumzngkU2BkDS_6FZ3r4eTENCcML3mYD+Q@mail.gmail.com>
Date: Tue, 28 Nov 2023 17:46:28 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Dmitry Rokosov <ddrokosov@...utedevices.com>
Cc: lee@...nel.org, pavel@....cz, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
kernel@...rdevices.ru, rockosov@...il.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v5 02/11] leds: aw200xx: support HWEN hardware control
On Sat, Nov 25, 2023 at 10:05 PM Dmitry Rokosov
<ddrokosov@...utedevices.com> wrote:
>
> HWEN is hardware control, which is used for enable/disable aw200xx chip.
> It's high active, internally pulled down to GND.
>
> After HWEN pin set high the chip begins to load the OTP information,
> which takes 200us to complete. About 200us wait time is needed for
> internal oscillator startup and display SRAM initialization. After
> display SRAM initialization, the registers in page 1 to page 5 can be
> configured via i2c interface.
...
> + chip->hwen = devm_gpiod_get_optional(&client->dev, "enable",
> + GPIOD_OUT_HIGH);
> + if (IS_ERR(chip->hwen))
> + return dev_err_probe(&client->dev, PTR_ERR(chip->hwen),
> + "Cannot get enable GPIO");
You can make it neater with
struct device *dev = &client->dev;
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists