From: Krzysztof Kozlowski <krzk@kernel.org>
To: Fabio Aiuto <fabio.aiuto@engicam.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Matteo Lisi <matteo.lisi@engicam.com>,
Mirko Ardinghi <mirko.ardinghi@engicam.com>
Subject: Re: [PATCH v2 1/1] regulator: pca9450: make warm reset on PMIC_RST_B assertion
Date: Thu, 11 Apr 2024 16:46:06 +0200 [thread overview]
Message-ID: <b805ed86-ce3c-4ecb-8a46-59bfa4678c4b@kernel.org> (raw)
In-Reply-To: <20240411100138.366292-2-fabio.aiuto@engicam.com>
On 11/04/2024 12:01, Fabio Aiuto wrote:
> The default configuration of the PMIC behavior makes the PMIC
> power cycle most regulators on PMIC_RST_B assertion. This power
> cycling causes the memory contents of OCRAM to be lost.
> Some systems needs some memory that survives reset and
> reboot, therefore this patch is created.
>
> This patch extends commit 2364a64d0673 ("regulator: pca9450:
> Make warm reset on WDOG_B assertion") to the other reset
> input source PMIC_RST_B as per pmic specs.
>
> CC: Matteo Lisi <matteo.lisi@engicam.com>
> CC: Mirko Ardinghi <mirko.ardinghi@engicam.com>
> Signed-off-by: Fabio Aiuto <fabio.aiuto@engicam.com>
> ---
> .../bindings/regulator/nxp,pca9450-regulator.yaml | 6 ++++++
Please run scripts/checkpatch.pl and fix reported warnings. Then please
run `scripts/checkpatch.pl --strict` and (probably) fix more warnings.
Some warnings can be ignored, especially from --strict run, but the code
here looks like it needs a fix. Feel free to get in touch if the warning
is not clear.
> drivers/regulator/pca9450-regulator.c | 11 ++++++++---
> include/linux/regulator/pca9450.h | 6 ++++++
> 3 files changed, 20 insertions(+), 3 deletions(-)
>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline), work on fork of kernel
(don't, instead use mainline) or you ignore some maintainers (really
don't). Just use b4 and everything should be fine, although remember
about `b4 prep --auto-to-cc` if you added new patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time, thus I will skip this patch entirely till you follow
the process allowing the patch to be tested.
Please kindly resend and include all necessary To/Cc entries.
Also: underscores are not allowed in property names.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-11 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 10:01 [PATCH v2 0/1] regulator: pca9450: make warm reset on PMIC_RST_B assertion Fabio Aiuto
2024-04-11 10:01 ` [PATCH v2 1/1] " Fabio Aiuto
2024-04-11 14:46 ` Krzysztof Kozlowski [this message]
2024-04-11 15:29 ` Fabio Aiuto
2024-04-11 12:37 ` [PATCH v2 0/1] " Mark Brown
2024-04-11 13:22 ` Fabio Aiuto
2024-04-11 13:49 ` Mark Brown
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=b805ed86-ce3c-4ecb-8a46-59bfa4678c4b@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=fabio.aiuto@engicam.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo.lisi@engicam.com \
--cc=mirko.ardinghi@engicam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.