[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VexCGKRVovaMhfzonFkju6vh_TR6_A3vLtZVox3AhAvYg@mail.gmail.com>
Date: Tue, 5 Jul 2022 20:51:52 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Vincent Knecht <vincent.knecht@...loo.org>
Cc: Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org,
"H. Nikolaus Schaller" <hns@...delico.com>
Subject: Re: [PATCH v3 5/6] leds: is31fl319x: Move chipset-specific values in
chipdef struct
On Tue, Jul 5, 2022 at 6:33 PM Vincent Knecht <vincent.knecht@...loo.org> wrote:
>
> Allow setting chips' specifics in chipdef struct by adding fields for:
> - the reset register address
> - a pointer to a regmap_config struct
> - a pointer to a brightness_set function
> - current default, min and max values
> - a boolean to distinguish 319{0,1,3} and 319{6,9} chips
> and use those fields in places where distinction has to be made.
>
> The fields for 319{0,1,3} still point to 319{6,9} values.
> No functional change.
...
> +static bool is31fl319x_readable_reg(struct device *dev, unsigned int reg)
> +{ /* we have no readable registers */
Non-standard place for comments.
> + return false;
> +}
...
> +static const struct reg_default is31fl3196_reg_defaults[] = {
> + { IS31FL3196_CONFIG1, 0x00},
> + { IS31FL3196_CONFIG2, 0x00},
> + { IS31FL3196_PWM(0), 0x00},
> + { IS31FL3196_PWM(1), 0x00},
> + { IS31FL3196_PWM(2), 0x00},
> + { IS31FL3196_PWM(3), 0x00},
> + { IS31FL3196_PWM(4), 0x00},
> + { IS31FL3196_PWM(5), 0x00},
> + { IS31FL3196_PWM(6), 0x00},
> + { IS31FL3196_PWM(7), 0x00},
> + { IS31FL3196_PWM(8), 0x00},
Missed space before }.
> };
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists