From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Samuel Holland <samuel@sholland.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Samuel Holland <samuel@sholland.org>,
Andrew Lunn <andrew@lunn.ch>, Heiko Stuebner <heiko@sntech.de>,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v5 2/4] regulator: sun20i: Add Allwinner D1 LDOs driver
Date: Fri, 13 Jan 2023 06:08:08 +0100 [thread overview]
Message-ID: <5906718.lOV4Wx5bFT@jernej-laptop> (raw)
In-Reply-To: <20221208084127.17443-3-samuel@sholland.org>
Dne četrtek, 08. december 2022 ob 09:41:25 CET je Samuel Holland napisal(a):
> D1 contains two pairs of LDOs, "analog" LDOs and "system" LDOs. They are
> similar and can share a driver, but only the system LDOs have a DT
> binding defined so far.
>
> The system LDOs have a single linear range. The voltage step is not an
> integer, so a custom .list_voltage is needed to get the rounding right.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
next prev parent reply other threads:[~2023-01-13 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 8:41 [PATCH v5 0/4] regulator: Add support for Allwinner D1 system LDOs Samuel Holland
2022-12-08 8:41 ` [PATCH v5 1/4] regulator: dt-bindings: Add " Samuel Holland
2022-12-08 8:41 ` [PATCH v5 2/4] regulator: sun20i: Add Allwinner D1 LDOs driver Samuel Holland
2023-01-12 23:50 ` Andre Przywara
2023-01-13 5:08 ` Jernej Škrabec [this message]
2022-12-08 8:41 ` [PATCH v5 3/4] dt-bindings: sram: sunxi-sram: Add regulators child Samuel Holland
2022-12-08 8:41 ` [PATCH v5 4/4] soc: sunxi: sram: Only iterate over SRAM children Samuel Holland
2023-01-12 17:31 ` Jernej Škrabec
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=5906718.lOV4Wx5bFT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
/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