On Mon, 7 Mar 2022 at 19:05, Vinod Polimera wrote:
>
> > WARNING: This email originated from outside of Qualcomm. Please be wary
> > of any links or attachments, and do not enable macros.
> >
> > On Sat, 5 Mar 2022 at 00:49, Doug Anderson
> > wrote:
> > > On Thu, Mar 3, 2022 at 4:16 PM Dmitry
> WARNING: This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
>
> On Sat, 5 Mar 2022 at 00:49, Doug Anderson
> wrote:
> > On Thu, Mar 3, 2022 at 4:16 PM Dmitry Baryshkov
> > wrote:
> > >
> > > On Fri, 4 Mar 2022 at 02:56,
On Sat, 5 Mar 2022 at 00:49, Doug Anderson wrote:
> On Thu, Mar 3, 2022 at 4:16 PM Dmitry Baryshkov
> wrote:
> >
> > On Fri, 4 Mar 2022 at 02:56, Stephen Boyd wrote:
> > >
> > > Quoting Dmitry Baryshkov (2022-03-03 15:50:50)
> > > > On Thu, 3 Mar 2022 at 12:40, Vinod Polimera
> > > > wrote:
>
Hi,
On Thu, Mar 3, 2022 at 4:16 PM Dmitry Baryshkov
wrote:
>
> On Fri, 4 Mar 2022 at 02:56, Stephen Boyd wrote:
> >
> > Quoting Dmitry Baryshkov (2022-03-03 15:50:50)
> > > On Thu, 3 Mar 2022 at 12:40, Vinod Polimera
> > > wrote:
> > > >
> > > > Kernel clock driver assumes that initial rate
On Fri, 4 Mar 2022 at 02:56, Stephen Boyd wrote:
>
> Quoting Dmitry Baryshkov (2022-03-03 15:50:50)
> > On Thu, 3 Mar 2022 at 12:40, Vinod Polimera
> > wrote:
> > >
> > > Kernel clock driver assumes that initial rate is the
> > > max rate for that clock and was not allowing it to scale
> > >
Quoting Dmitry Baryshkov (2022-03-03 15:50:50)
> On Thu, 3 Mar 2022 at 12:40, Vinod Polimera wrote:
> >
> > Kernel clock driver assumes that initial rate is the
> > max rate for that clock and was not allowing it to scale
> > beyond the assigned clock value.
> >
> > Drop the assigned clock rate
On Thu, 3 Mar 2022 at 12:40, Vinod Polimera wrote:
>
> Kernel clock driver assumes that initial rate is the
> max rate for that clock and was not allowing it to scale
> beyond the assigned clock value.
>
> Drop the assigned clock rate property and vote on the mdp clock as per
> calculated value
Quoting Vinod Polimera (2022-03-03 01:40:01)
> Kernel clock driver assumes that initial rate is the
> max rate for that clock and was not allowing it to scale
> beyond the assigned clock value.
>
> Drop the assigned clock rate property and vote on the mdp clock as per
> calculated value during the
Kernel clock driver assumes that initial rate is the
max rate for that clock and was not allowing it to scale
beyond the assigned clock value.
Drop the assigned clock rate property and vote on the mdp clock as per
calculated value during the usecase.
Fixes: 7c1dffd471("arm64: dts: qcom:
