On Mon, Feb 15, 2021 at 06:24:44PM +0100, Jacopo Mondi wrote: > The MAX9286 GMSL deserializer features gpio controller capabilities, > as it provides 2 GPIO lines. > > As establishing a regulator that uses one of the GPIO lines and > enabling/disabling it at run-time in the max9286 won't work due to > a circular dependency on the gpio-controller/regulator creation, allow > the usage of a gpio-hog for that purpose. > > The usage of the gpio-hog is required in designs where the MAX9286 > GPIO lines control the remote cameras power. > > Signed-off-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx> > --- > .../devicetree/bindings/media/i2c/maxim,max9286.yaml | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > index ee16102fdfe7..9d5ecfd2397c 100644 > --- a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > @@ -50,6 +50,15 @@ properties: > '#gpio-cells': > const: 2 > > + camvdd_en: I don't think we want to document all the GPIO hogs, but rather have a pattern we can check. IOW, having node name pattern we match on. I think the core schemas has this now. > + type: object > + properties: > + gpio-hog: true > + gpios: true > + output-low: true > + line-name: > + const: "CAMVDD_EN" > + > maxim,reverse-channel-microvolt: > minimum: 30000 > maximum: 200000 > -- > 2.30.0 >
