[RFC/RFT v3 04/14] clk: meson: eeclk: add setup callback
martin.blumenstingl at googlemail.com
Wed Jul 3 05:57:16 PDT 2019
On Wed, Jul 3, 2019 at 2:40 PM Jerome Brunet <jbrunet at baylibre.com> wrote:
> On Wed 03 Jul 2019 at 13:45, Neil Armstrong <narmstrong at baylibre.com> wrote:
> > On 03/07/2019 01:16, Martin Blumenstingl wrote:
> >> +Cc Alexandre Mergnat
> >> On Mon, Jul 1, 2019 at 11:13 AM Neil Armstrong <narmstrong at baylibre.com> wrote:
> >>> Add a setup() callback in the eeclk structure, to call an optional
> >>> call() function at end of eeclk probe to setup clocks.
> >>> It's used for the G12A clock controller to setup the CPU clock notifiers.
> >>> Signed-off-by: Neil Armstrong <narmstrong at baylibre.com>
> >> this will probably work fine, but I want do double check first
> >> are we planning to get rid of meson-eeclk (mid-term)?
> > AFAIK no, but maybe I'm not aware of it !
> > Neil
> >> Alex has some patches to get rid of all these IN_PREFIX logic.
> The prefix logic will go away with Alex's rework, so are the input clock
> But meson-eeclk, which is just a common probe function do avoid
> repeating the same things over and over, will stay
OK, thank you for clarifying this
> >> I'm asking because if we want to get rid of meson-eeclk it may be the
> May I ask why ?
I only remember that Stephen asked us to get rid of something in our clock code
I was under the impression that it was meson-eeclk, but I cannot find
it anymore (that means I'm mixing it up with some other topic)
More information about the linux-amlogic