From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: tony@atomide.com, Sebastian Reichel <sre@kernel.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/3] power: supply: initial support for TWL6030/32
Date: Wed, 18 Sep 2024 14:53:19 +0200 [thread overview]
Message-ID: <b4186150-bc96-49c7-8622-0692365acb69@kernel.org> (raw)
In-Reply-To: <20240918144325.0ccca89c@akair>
On 18/09/2024 14:43, Andreas Kemnade wrote:
> Am Wed, 18 Sep 2024 12:43:01 +0200
> schrieb Krzysztof Kozlowski <krzk@kernel.org>:
>
> [...]
>> Drop {}, see checkpatch.
>>
>>> + return dev_err_probe(&pdev->dev, ret,
>>> + "could not request irq %d\n",
>>> + charger->irq_chg);
>>> + }
>>> +
>
> Apparently checkpatch only moans about {} around single *lines*
> not single *statements*, even with --strict.
>
> Coding-style says single statements, so maybe checkpatch should be
> fixed?
>
> Same for other appearance of this pattern.
Hm, could be. I think this still should be without {}, regardless of
checkpatch.
>
>>> + /* turing to charging to configure things */
>>> + twl6030_charger_write(CONTROLLER_CTRL1, 0);
>>> + twl6030_charger_interrupt(0, charger);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static const struct of_device_id twl_charger_of_match[]
>>> __maybe_unused = {
>>> + {.compatible = "ti,twl6030-charger", },
>>> + {.compatible = "ti,twl6032-charger", },
>>
>> So they are compatible? Why two entries in such case?
>>
> There is one device_is_compatible() in the file.
Ah, you should rather use match data. Compatibles inside the code do not
scale.
>
> Regrads,
> Andreas
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-18 12:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:41 [PATCH 0/3] power: supply: twl6030/32 charger Andreas Kemnade
2024-09-18 8:41 ` [PATCH 1/3] dt-bindings: power: supply: Add TI TWL603X charger Andreas Kemnade
2024-09-18 10:46 ` Krzysztof Kozlowski
2024-09-18 8:41 ` [PATCH 2/3] dt-bindings: mfd: twl: add charger node also for TWL603x Andreas Kemnade
2024-09-18 10:47 ` Krzysztof Kozlowski
2024-09-18 11:35 ` Andreas Kemnade
2024-09-21 0:51 ` Rob Herring
2024-09-26 7:26 ` Andreas Kemnade
2024-09-18 8:41 ` [PATCH 3/3] power: supply: initial support for TWL6030/32 Andreas Kemnade
2024-09-18 10:43 ` Krzysztof Kozlowski
2024-09-18 12:43 ` Andreas Kemnade
2024-09-18 12:53 ` Krzysztof Kozlowski [this message]
2024-09-23 16:29 ` Andreas Kemnade
2024-09-24 8:00 ` Krzysztof Kozlowski
2024-09-18 21:11 ` kernel test robot
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=b4186150-bc96-49c7-8622-0692365acb69@kernel.org \
--to=krzk@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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).