[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190905180615.GG4053@sirena.co.uk>
Date: Thu, 5 Sep 2019 19:06:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Philippe Schenker <philippe.schenker@...adex.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Liam Girdwood <lgirdwood@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Max Krummenacher <max.krummenacher@...adex.com>,
Rob Herring <robh+dt@...nel.org>,
Stefan Agner <stefan.agner@...adex.com>,
Marcel Ziswiler <marcel.ziswiler@...adex.com>,
Mark Rutland <mark.rutland@....com>,
Luka Pivk <luka.pivk@...adex.com>
Subject: Re: [PATCH 1/3] regulator: fixed: add possibility to enable by clock
On Tue, Sep 03, 2019 at 08:03:46AM +0000, Philippe Schenker wrote:
> This commit adds the possibility to choose the compatible
> "regulator-fixed-clock" in devicetree.
>
> This is a special regulator-fixed that has to have a clock, from which
> the regulator gets switched on and off.
This seems conceptually fine. Minor issues though:
> +static int reg_clock_is_enabled(struct regulator_dev *rdev)
> +{
> + struct fixed_voltage_data *priv = rdev_get_drvdata(rdev);
> +
> + if (priv->clk_enable_counter > 0)
> + return 1;
> +
> + return 0;
> +}
This could just be return priv->clk_enable_counter > 0 - ideally the
clock API would let us query if the clock is enabled but that might be a
bit confused anyway given that it's possibly shared.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists