[to Stephen and Mike]
On 03/03/2020 04:18, CK Hu wrote:
> Hi, Matthias:
>
> On Thu, 2020-02-27 at 19:22 +0100, Matthias Brugger wrote:
>>
>> On 27/02/2020 19:21, Matthias Brugger wrote:
>>>
>>>
>>> On 27/02/2020 19:08, Enric Balletbo i Serra wrote:
From: Matthias Brugger
There is
Hi, Matthias:
On Thu, 2020-02-27 at 19:22 +0100, Matthias Brugger wrote:
>
> On 27/02/2020 19:21, Matthias Brugger wrote:
> >
> >
> > On 27/02/2020 19:08, Enric Balletbo i Serra wrote:
> >> From: Matthias Brugger
> >>
> >> There is no strong reason for this to use CLK_OF_DECLARE instead of
>
Hi, Enric:
On Thu, 2020-02-27 at 19:08 +0100, Enric Balletbo i Serra wrote:
> From: Matthias Brugger
>
> There is no strong reason for this to use CLK_OF_DECLARE instead of
> being a platform driver. Plus, this driver provides clocks but also
> a shared register space for the mediatek-drm and
On 27/02/2020 19:08, Enric Balletbo i Serra wrote:
> From: Matthias Brugger
>
> There is no strong reason for this to use CLK_OF_DECLARE instead of
> being a platform driver. Plus, this driver provides clocks but also
> a shared register space for the mediatek-drm and the mediatek-mdp
>
From: Matthias Brugger
There is no strong reason for this to use CLK_OF_DECLARE instead of
being a platform driver. Plus, this driver provides clocks but also
a shared register space for the mediatek-drm and the mediatek-mdp
driver. So move to drivers/soc/mediatek as a platform driver.
On 27/02/2020 19:21, Matthias Brugger wrote:
>
>
> On 27/02/2020 19:08, Enric Balletbo i Serra wrote:
>> From: Matthias Brugger
>>
>> There is no strong reason for this to use CLK_OF_DECLARE instead of
>> being a platform driver. Plus, this driver provides clocks but also
>> a shared
