lkml.org 
[lkml]   [2020]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v2 20/91] clk: bcm: rpi: Discover the firmware clocks
    From
    Date
    Hi Maxime, as always, thanks for the series!
    Some extra context, and comments below.

    On Fri, 2020-04-24 at 17:34 +0200, Maxime Ripard wrote:
    > The RaspberryPi4 firmware actually exposes more clocks than are currently
    > handled by the driver and we will need to change some of them directly
    > based on the pixel rate for the display related clocks, or the load for the
    > GPU.
    >
    > This rate change can have a number of side-effects, including adjusting the
    > various PLL voltages or the PLL parents. The firmware will also update
    > those clocks by itself for example if the SoC runs too hot.

    To complete this:

    RPi4's firmware implements DVFS. Clock frequency and SoC voltage are
    correlated, if you can determine all clocks are running below a maximum then it
    should be safe to lower the voltage. Currently, firmware actively monitors arm,
    core, h264, v3d, isp and hevc to determine what voltage can be reduced to, and
    if arm increases any of those clocks behind the firmware's back, when it has a
    lowered voltage, a crash is highly likely.

    As pointed out to me by RPi foundation engineers hsm/pixel aren't currently
    being monitored, as driving a high resolution display also requires a high core
    clock, which already sets an acceptable min voltage threshold. But that might
    change if needed.

    Ultimately, from the DVFS, the safe way to change clocks from arm would be to
    always use the firmware interface, which we're far from doing right now. On the
    other hand, AFAIK not all clocks have a firmware counterpart.

    Note that we could also have a word with the RPi foundation and see if
    disabling DVFS is possible (AFAIK it's not an option right now). Although I
    personally prefer to support this upstream, aside from the obvious benefits to
    battery powered use cases, not consuming power unnecessarily is always big
    plus.

    > In order to make Linux play as nice as possible with those constraints, it
    > makes sense to rely on the firmware clocks as much as possible.

    As I comment above, not as simple as it seems. I suggest, for now, we only
    register the clocks we're going to use and that are likely to be affected by
    DVFS. hsm being a contender here.

    As we'd be settling on a hybrid solution here, which isn't ideal to say the
    least, I'd like to gather some opinions on whether pushing towards a fully
    firmware based solution is something you'd like to see.

    > Fortunately,t he firmware has an interface to discover the clocks it
    > exposes.

    nit: wrongly placed space

    > Let's use it to discover, register the clocks in the clocks framework and
    > then expose them through the device tree for consumers to use them.
    >
    > Cc: Michael Turquette <mturquette@baylibre.com>
    > Cc: Stephen Boyd <sboyd@kernel.org>
    > Cc: linux-clk@vger.kernel.org
    > Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    > ---
    > drivers/clk/bcm/clk-raspberrypi.c | 104 +++++++++++++++++++---

    [...]

    > +static struct clk_hw *raspberrypi_clk_register(struct raspberrypi_clk *rpi,
    > + unsigned int parent,
    > + unsigned int id)
    > +{
    > + struct raspberrypi_clk_data *data;
    > + struct clk_init_data init = {};
    > + int ret;
    > +
    > + if (id == RPI_FIRMWARE_ARM_CLK_ID) {
    > + struct clk_hw *hw;
    > +
    > + hw = raspberrypi_register_pllb(rpi);
    > + if (IS_ERR(hw)) {
    > + dev_err(rpi->dev, "Failed to initialize pllb, %ld\n",
    > + PTR_ERR(hw));
    > + return hw;
    > + }
    > +
    > + return raspberrypi_register_pllb_arm(rpi);
    > + }

    We shouldn't create a special case for pllb. My suggestion here is that we
    revert the commit that removed pllb from the mmio driver, in order to maintain a
    nice view of the clock tree, and register this as a regular fw-clk.

    The only user to this is RPi's the cpufreq driver, which shouldn't mind the
    change as long as you maintain the clk lookup creation.

    On that topic, now that the clocks are available in DT we could even move
    raspberrypi-cpufreq's registration there. But that's out of the scope of this
    series.

    > +
    > + data = devm_kzalloc(rpi->dev, sizeof(*data), GFP_KERNEL);
    > + if (!data)
    > + return ERR_PTR(-ENOMEM);
    > + data->rpi = rpi;
    > + data->id = id;
    > +
    > + init.name = devm_kasprintf(rpi->dev, GFP_KERNEL, "fw-clk-%u", id);

    I'd really like more descriptive names here, sadly the firmware interface
    doesn't provide them, but they are set in stone nonetheless. Something like
    'fw-clk-arm' and 'fw-clk-hsm' comes to mind (SCMI does provide naming BTW).

    See here for a list of all clocks:
    https://github.com/raspberrypi/firmware/wiki/Mailbox-property-interface#clocks

    > + init.ops = &raspberrypi_firmware_clk_ops;
    > + init.flags = CLK_GET_RATE_NOCACHE;
    > +
    > + data->hw.init = &init;
    > +
    > + ret = devm_clk_hw_register(rpi->dev, &data->hw);
    > + if (ret)
    > + return ERR_PTR(ret);
    > +
    > + return &data->hw;
    > +}
    > +
    > +static int raspberrypi_discover_clocks(struct raspberrypi_clk *rpi,
    > + struct clk_hw_onecell_data *data)
    > +{
    > + struct rpi_firmware_get_clocks_response *clks;
    > + int ret;
    > +
    > + clks = devm_kcalloc(rpi->dev, sizeof(*clks), NUM_FW_CLKS, GFP_KERNEL);
    > + if (!clks)
    > + return -ENOMEM;
    > +
    > + ret = rpi_firmware_property(rpi->firmware, RPI_FIRMWARE_GET_CLOCKS,
    > + clks, sizeof(*clks) * NUM_FW_CLKS);
    > + if (ret)
    > + return ret;
    > +
    > + while (clks->id) {
    > + struct clk_hw *hw;

    Se my comment above WRT registering all clocks.

    Regards,
    Nicolas

    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2020-05-04 14:07    [W:3.946 / U:2.000 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site