[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <159304595094.62212.14613931379549423607@swboyd.mtv.corp.google.com>
Date: Wed, 24 Jun 2020 17:45:50 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Maxime Ripard <maxime@...no.tech>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: linux-rpi-kernel@...ts.infradead.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Tim Gover <tim.gover@...pberrypi.com>,
Phil Elwell <phil@...pberrypi.com>,
Mike Turquette <mturquette@...libre.com>,
linux-clk@...r.kernel.org, Philipp Zabel <p.zabel@...gutronix.de>,
Maxime Ripard <maxime@...no.tech>
Subject: Re: [PATCH v5 22/27] clk: bcm: rpi: Give firmware clocks a name
Quoting Maxime Ripard (2020-06-15 01:41:02)
> We've registered the firmware clocks using their ID as name, but it's much
> more convenient to register them using their proper name. Since the
> firmware doesn't provide it, we have to duplicate it.
>
> Acked-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
> Tested-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
> Signed-off-by: Maxime Ripard <maxime@...no.tech>
> ---
Applied to clk-next
Powered by blists - more mailing lists