devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Vincent Knecht <vincent.knecht@mailoo.org>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v3 4/6] leds: is31fl319x: Use non-wildcard names for vars, structs and defines
Date: Tue, 5 Jul 2022 20:47:05 +0200	[thread overview]
Message-ID: <CAHp75VdHdSkALpgGHGxthq8h1q9Dg3N5jJS6NxTuexvfWJEDjQ@mail.gmail.com> (raw)
In-Reply-To: <20220705163136.2278662-5-vincent.knecht@mailoo.org>

On Tue, Jul 5, 2022 at 6:32 PM Vincent Knecht <vincent.knecht@mailoo.org> wrote:
>
> In order to add real support for is31fl3190, is31fl3191 and is31fl3193,
> rename variant-dependent elements to not use 319X where needed.
>
> 3190 suffix is used for is31fl3190, is31fl3191 and is31fl3193 circuits.
> 3196 suffix is used for is31fl3196 and is31fl3199.
>
> Those two groups have different register maps, current settings and even
> a different interpretation of the software shutdown bit:
> https://lumissil.com/assets/pdf/core/IS31FL3190_DS.pdf
> https://lumissil.com/assets/pdf/core/IS31FL3191_DS.pdf
> https://lumissil.com/assets/pdf/core/IS31FL3193_DS.pdf
> https://lumissil.com/assets/pdf/core/IS31FL3196_DS.pdf
> https://lumissil.com/assets/pdf/core/IS31FL3199_DS.pdf
>
> Rename variables, structures and defines in preparation of the splitting.
> No functional nor behaviour change.

...

> +static bool is31fl3196_volatile_reg(struct device *dev, unsigned int reg)

>  { /* volatile registers are not cached */

This is a rather non-standard place for comments. Are you going to
address this in the future?

>  }

...

> +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},

While at it, add a space before }. This seems in many places like
this. Perhaps address the rest in a separate patch?

>  };

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2022-07-05 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 16:31 [PATCH v3 0/6] leds: Fix/Add is31fl319{0,1,3} support Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 1/6] dt-bindings: leds: Convert is31fl319x to dtschema Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 2/6] dt-bindings: leds: is31fl319x: Document variants specificities Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 3/6] leds: is31fl319x: Add missing si-en compatibles Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 4/6] leds: is31fl319x: Use non-wildcard names for vars, structs and defines Vincent Knecht
2022-07-05 18:47   ` Andy Shevchenko [this message]
2022-07-05 16:31 ` [PATCH v3 5/6] leds: is31fl319x: Move chipset-specific values in chipdef struct Vincent Knecht
2022-07-05 18:51   ` Andy Shevchenko
2022-07-05 16:31 ` [PATCH v3 6/6] leds: is31fl319x: Add support for is31fl319{0,1,3} chips Vincent Knecht
2022-07-05 18:56   ` Andy Shevchenko
2022-07-05 18:57 ` [PATCH v3 0/6] leds: Fix/Add is31fl319{0,1,3} support Andy Shevchenko
2022-07-09  9:51   ` Vincent Knecht
2022-07-11 21:39     ` Andy Shevchenko
2022-07-11 21:40       ` Andy Shevchenko

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=CAHp75VdHdSkALpgGHGxthq8h1q9Dg3N5jJS6NxTuexvfWJEDjQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vincent.knecht@mailoo.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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;
as well as URLs for NNTP newsgroup(s).