[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1bebedb9-644f-783d-492c-84a5de91720d@canonical.com>
Date: Sun, 6 Feb 2022 18:39:47 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Chanwoo Choi <cw00.choi@...sung.com>
Subject: Re: [PATCH v2 0/5] mfd/extcon/regulators: max77843: add
dtschema/bindings
On 11/01/2022 18:48, Krzysztof Kozlowski wrote:
> Hi,
>
> The max77843 shares some parts with max77693 but it lacked bindings. All
> its compatibles were undocumented. Add basic bindings for max77843,
> matching existing devicetree. These are not complete bindings, but
> rather reverse-engineered to match current state.
>
> I do not have access to device with MAX77843, so if anyone else
> volunteers to be the bindings maintainer, please join.
>
> Changes since v1
> ================
> 1. MFD: Use absolute path to schemas.
> 2. Regulator: mention all allowed properties,
> additionalProperties=false, add min/max values for voltages and
> current, don't use patternProperties when not needed.
> 3. extcon: Use absolute path to schemas.
>
> Dependencies
> ============
> 1. Patch 1/5 (dts): nothing depends on it, sending here so Rob's automatic
> checker won't complain about DTS.
> I will take it via Samsung SoC tree.
>
> 2. The patch 4/5 (mfd bindings) depends on regulator and extcon, so they
> should come together (2+3+4+5).
>
Dear Lee,
This patchset was reviewed and there are no outstanding issues. Could
you pick up patches 2-5 (skipping DTS patch) via MFD tree?
Best regards,
Krzysztof
Powered by blists - more mailing lists