ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Rob Herring <robh@kernel.org>, Samuel Holland <samuel@sholland.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Maxime Ripard <mripard@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2 3/4] regulator: dt-bindings: Add Allwinner D1 LDOs
Date: Thu, 04 Aug 2022 07:11:39 +0200	[thread overview]
Message-ID: <5588658.DvuYhMxLoT@jernej-laptop> (raw)
In-Reply-To: <918a83a7-1b8d-04b1-4f7b-386fc800e653@sholland.org>

Dne četrtek, 04. avgust 2022 ob 05:03:07 CEST je Samuel Holland napisal(a):
> Hi Rob,
> 
> Thanks again for your review.
> 
> On 8/2/22 10:04 AM, Rob Herring wrote:
> > On Tue, Aug 02, 2022 at 12:32:12AM -0500, Samuel Holland wrote:
> >> The Allwinner D1 SoC contains two pairs of in-package LDOs. One pair is
> >> for general purpose use. LDOA generally powers the board's 1.8 V rail.
> >> LDOB generally powers the in-package DRAM, where applicable.
> >> 
> >> The other pair of LDOs powers the analog power domains inside the SoC,
> >> including the audio codec, thermal sensor, and ADCs. These LDOs require
> >> a 0.9 V bandgap voltage reference. The calibration value for the voltage
> >> reference is stored in an eFuse, accessed via an NVMEM cell.
> >> 
> >> Neither LDO control register is in its own MMIO range; instead, each
> >> regulator device relies on a regmap/syscon exported by its parent.
> >> 
> >> Signed-off-by: Samuel Holland <samuel@sholland.org>
> >> ---
> >> 
> >> Changes in v2:
> >>  - Remove syscon property from bindings
> >>  - Update binding examples to fix warnings and provide context
> >>  
> >>  .../allwinner,sun20i-d1-analog-ldos.yaml      | 65 +++++++++++++++++++
> >>  .../allwinner,sun20i-d1-system-ldos.yaml      | 57 ++++++++++++++++
> >>  2 files changed, 122 insertions(+)
> >>  create mode 100644
> >>  Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-analog-
> >>  ldos.yaml create mode 100644
> >>  Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system-
> >>  ldos.yaml>> 
> >> diff --git
> >> a/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-analog
> >> -ldos.yaml
> >> b/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-analog
> >> -ldos.yaml new file mode 100644
> >> index 000000000000..19c984ef4e53
> >> --- /dev/null
> >> +++
> >> b/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-analog
> >> -ldos.yaml @@ -0,0 +1,65 @@
> >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> >> +%YAML 1.2
> >> +---
> >> +$id:
> >> http://devicetree.org/schemas/regulator/allwinner,sun20i-d1-analog-ldos.
> >> yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: Allwinner D1 Analog LDOs
> >> +
> >> +description:
> >> +  Allwinner D1 contains a set of LDOs which are designed to supply
> >> analog power +  inside and outside the SoC. They are controlled by a
> >> register within the audio +  codec MMIO space, but which is not part of
> >> the audio codec clock/reset domain. +
> >> +maintainers:
> >> +  - Samuel Holland <samuel@sholland.org>
> >> +
> >> +properties:
> >> +  compatible:
> >> +    enum:
> >> +      - allwinner,sun20i-d1-analog-ldos
> >> +
> >> +  nvmem-cells:
> >> +    items:
> >> +      - description: NVMEM cell for the calibrated bandgap reference
> >> trim value +
> >> +  nvmem-cell-names:
> >> +    items:
> >> +      - const: bg_trim
> >> +
> >> +patternProperties:
> > 
> >> +  "^(aldo|hpldo)$":
> > '^(a|hp)ldo$'
> > 
> >> +    type: object
> >> +    $ref: regulator.yaml#
> >> 
> >        unevaluatedProperties: false
> >> 
> >> +
> >> +required:
> >> +  - compatible
> >> +  - nvmem-cells
> >> +  - nvmem-cell-names
> >> +
> >> +unevaluatedProperties: false
> >> +
> >> +examples:
> >> +  - |
> >> +    audio-codec@2030000 {
> >> +        compatible = "simple-mfd", "syscon";
> > 
> > Needs a specific compatible. Obviously there's some other functionality
> > here if this is an 'audio-codec'.
> 
> I am not yet ready to submit the binding or driver for the audio codec, as I
> still need to work out the details for jack detection (and some other
> issues). If I added the specific audio codec compatible now, without the
> properties required for the sound driver, that would create backward
> compatibility issues, right?
> 
> My intention is to add the specific compatible along with the ASoC support.
> 
> > 'simple-mfd' also means the child nodes have zero dependence on the
> > parent node and its resources.
> 
> That is correct. The regulators have zero dependencies on the audio codec
> resources (clocks/resets/etc.). The _only_ relationship is the overlapping
> address of the MMIO register.

LDO registers are at the end of analogue codec MMIO space, right? We can 
easily split that to separate device, like it's been done for A20 timer & 
watchdog.

Best regards,
Jernej

> 
> >> +        reg = <0x2030000 0x1000>;
> >> +
> >> +        regulators {
> >> +            compatible = "allwinner,sun20i-d1-analog-ldos";
> > 
> > Is there a defined set of registers for these regulators? If so, put
> > them into 'reg'.
> 
> What do you suggest for 'ranges' in the parent device? I ask because the
> SRAM/system controller binding requires an empty 'ranges' property.
> 
> With empty 'ranges', the child has to compute the relative address for use
> with the parent's regmap, but maybe that is okay?
> 
> >> +            nvmem-cells = <&bg_trim>;
> >> +            nvmem-cell-names = "bg_trim";
> >> +
> >> +            reg_aldo: aldo {
> >> +                regulator-min-microvolt = <1800000>;
> >> +                regulator-max-microvolt = <1800000>;
> >> +            };
> >> +
> >> +            reg_hpldo: hpldo {
> >> +                regulator-min-microvolt = <1800000>;
> >> +                regulator-max-microvolt = <1800000>;
> >> +            };
> >> +        };
> >> +    };
> >> +
> >> +...
> >> diff --git
> >> a/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system
> >> -ldos.yaml
> >> b/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system
> >> -ldos.yaml new file mode 100644
> >> index 000000000000..c95030a827d6
> >> --- /dev/null
> >> +++
> >> b/Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system
> >> -ldos.yaml @@ -0,0 +1,57 @@
> >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> >> +%YAML 1.2
> >> +---
> >> +$id:
> >> http://devicetree.org/schemas/regulator/allwinner,sun20i-d1-system-ldos.
> >> yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: Allwinner D1 System LDOs
> >> +
> >> +description:
> >> +  Allwinner D1 contains a pair of general-purpose LDOs which are
> >> designed to +  supply power inside and outside the SoC. They are
> >> controlled by a register +  within the system control MMIO space.
> >> +
> >> +maintainers:
> >> +  - Samuel Holland <samuel@sholland.org>
> >> +
> >> +properties:
> >> +  compatible:
> >> +    enum:
> >> +      - allwinner,sun20i-d1-system-ldos
> >> +
> >> +patternProperties:
> > 
> >> +  "^(ldoa|ldob)$":
> > '^ldo[ab]$'
> > 
> > Any reason the naming is not consistent with 'ldo' as the prefix or
> > suffix?
> 
> All four names match the pin names from the SoC datasheet.
> 
> >> +    type: object
> >> +    $ref: regulator.yaml#
> >> 
> >        unevaluatedProperties: false
> 
> I will fix these for v3.
> 
> Regards,
> Samuel
> 
> >> +
> >> +required:
> >> +  - compatible
> >> +
> >> +unevaluatedProperties: false
> >> +
> >> +examples:
> >> +  - |
> >> +    syscon@3000000 {
> >> +        compatible = "allwinner,sun20i-d1-system-control";
> >> +        reg = <0x3000000 0x1000>;
> >> +        ranges;
> >> +        #address-cells = <1>;
> >> +        #size-cells = <1>;
> >> +
> >> +        regulators {
> >> +            compatible = "allwinner,sun20i-d1-system-ldos";
> >> +
> >> +            reg_ldoa: ldoa {
> >> +                regulator-min-microvolt = <1800000>;
> >> +                regulator-max-microvolt = <1800000>;
> >> +            };
> >> +
> >> +            reg_ldob: ldob {
> >> +                regulator-name = "vcc-dram";
> >> +                regulator-min-microvolt = <1500000>;
> >> +                regulator-max-microvolt = <1500000>;
> >> +            };
> >> +        };
> >> +    };
> >> +
> >> +...





  reply	other threads:[~2022-08-04  5:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  5:32 [PATCH v2 0/4] regulator: Add support for Allwinner D1 LDOs Samuel Holland
2022-08-02  5:32 ` [PATCH v2 1/4] dt-bindings: sram: sunxi-sram: Add optional regulators child Samuel Holland
2022-08-02 15:06   ` Rob Herring
2022-08-02  5:32 ` [PATCH v2 2/4] soc: sunxi: sram: Only iterate over SRAM children Samuel Holland
2022-08-02  5:32 ` [PATCH v2 3/4] regulator: dt-bindings: Add Allwinner D1 LDOs Samuel Holland
2022-08-02 14:01   ` Rob Herring
2022-08-02 15:04   ` Rob Herring
2022-08-04  3:03     ` Samuel Holland
2022-08-04  5:11       ` Jernej Škrabec [this message]
2022-08-04 14:01         ` Samuel Holland
2022-08-04 20:25       ` Rob Herring
2022-08-02  5:32 ` [PATCH v2 4/4] regulator: sun20i: Add support for " Samuel Holland

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=5588658.DvuYhMxLoT@jernej-laptop \
    --to=jernej.skrabec@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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@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