On 0908, Amit Kucheria wrote:
> On Tue, Sep 8, 2020 at 1:27 PM Manivannan Sadhasivam
> wrote:
> >
> > For preparing the driver to handle further SoC revisions, let's use the
> > of_match data for getting the device specific offsets and row size instead
> > of defining them globally.
> >
> >
On Tue 08 Sep 02:57 CDT 2020, Manivannan Sadhasivam wrote:
> For preparing the driver to handle further SoC revisions, let's use the
> of_match data for getting the device specific offsets and row size instead
> of defining them globally.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
On Tue, Sep 8, 2020 at 8:40 PM Manivannan Sadhasivam
wrote:
>
> On 0908, Amit Kucheria wrote:
> > On Tue, Sep 8, 2020 at 1:27 PM Manivannan Sadhasivam
> > wrote:
> > >
> > > For preparing the driver to handle further SoC revisions, let's use the
> > > of_match data for getting the device
On Tue, Sep 8, 2020 at 1:27 PM Manivannan Sadhasivam
wrote:
>
> For preparing the driver to handle further SoC revisions, let's use the
> of_match data for getting the device specific offsets and row size instead
> of defining them globally.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
For preparing the driver to handle further SoC revisions, let's use the
of_match data for getting the device specific offsets and row size instead
of defining them globally.
Signed-off-by: Manivannan Sadhasivam
---
drivers/cpufreq/qcom-cpufreq-hw.c | 96 +--
1 file
5 matches
Mail list logo