Re: [PATCH v2 1/3] clk: Introduce a clock request API

Quoting Maxime Ripard (2022-01-14 08:15:56) > On Thu, Jan 13, 2022 at 01:44:25PM -0800, Stephen Boyd wrote: > > > > I don't see a problem with re-evaluating the rate every time we call > > clk_set_rate_range(). That's probably the bug that I can't recall. Can > > you fix the API so it works that wa

Re: [PATCH v2 1/3] clk: Introduce a clock request API

Quoting Maxime Ripard (2022-01-14 08:15:56) > On Thu, Jan 13, 2022 at 01:44:25PM -0800, Stephen Boyd wrote: > > > > > I don't see a problem with re-evaluating the rate every time we call > > clk_set_rate_range(). That's probably the bug that I can't recall. Can > > you fix the API so it works that

Re: [PATCH v2 1/3] clk: Introduce a clock request API

On Thu, Jan 13, 2022 at 01:44:25PM -0800, Stephen Boyd wrote: > Quoting Maxime Ripard (2022-01-12 03:46:52) > > On Tue, Jan 11, 2022 at 07:37:15PM -0800, Stephen Boyd wrote: > > > Sorry for being super delayed on response here. I'm buried in other > > > work. +Jerome for exclusive clk API. > > > >

Re: [PATCH v2 1/3] clk: Introduce a clock request API

Quoting Maxime Ripard (2022-01-12 03:46:52) > Hi Stephen, > > Thanks for your answer > > On Tue, Jan 11, 2022 at 07:37:15PM -0800, Stephen Boyd wrote: > > Sorry for being super delayed on response here. I'm buried in other > > work. +Jerome for exclusive clk API. > > > > Quoting Maxime Ripard (2

Re: [PATCH v2 1/3] clk: Introduce a clock request API

Hi Stephen, Thanks for your answer On Tue, Jan 11, 2022 at 07:37:15PM -0800, Stephen Boyd wrote: > Sorry for being super delayed on response here. I'm buried in other > work. +Jerome for exclusive clk API. > > Quoting Maxime Ripard (2021-09-14 02:35:13) > > It's not unusual to find clocks being

Re: [PATCH v2 1/3] clk: Introduce a clock request API

Sorry for being super delayed on response here. I'm buried in other work. +Jerome for exclusive clk API. Quoting Maxime Ripard (2021-09-14 02:35:13) > It's not unusual to find clocks being shared across multiple devices > that need to change the rate depending on what the device is doing at a > gi

[PATCH v2 1/3] clk: Introduce a clock request API

It's not unusual to find clocks being shared across multiple devices that need to change the rate depending on what the device is doing at a given time. The SoC found on the RaspberryPi4 (BCM2711) is in such a situation between its two HDMI controllers that share a clock that needs to be raised de