Message-ID: <022e8f64-b414-67a5-722e-bdd7c00230ff@collabora.com>
Date:   Fri, 14 Feb 2020 13:19:26 +0100
From:   Enric Balletbo i Serra <enric.balletbo@...labora.com>
To:     Matthias Brugger <matthias.bgg@...il.com>,
        CK Hu <ck.hu@...iatek.com>, matthias.bgg@...nel.org
Cc:     mark.rutland@....com, airlied@...ux.ie, mturquette@...libre.com,
        dri-devel@...ts.freedesktop.org, laurent.pinchart@...asonboard.com,
        ulrich.hecht+renesas@...il.com, linux-clk@...r.kernel.org,
        drinkcat@...omium.org, Weiyi Lu <weiyi.lu@...iatek.com>,
        wens@...e.org, mtk01761 <wendell.lin@...iatek.com>,
        linux-media@...r.kernel.org, devicetree@...r.kernel.org,
        Daniel Vetter <daniel@...ll.ch>, frank-w@...lic-files.de,
        sean.wang@...iatek.com, robh+dt@...nel.org,
        linux-mediatek@...ts.infradead.org, hsinyi@...omium.org,
        linux-arm-kernel@...ts.infradead.org,
        Matthias Brugger <mbrugger@...e.com>, sboyd@...nel.org,
        rdunlap@...radead.org, linux-kernel@...r.kernel.org,
        p.zabel@...gutronix.de
Subject: Re: [PATCH v7 01/13] dt-bindings: arm: move mmsys description to
 display

Hi CK,

On 14/2/20 11:01, Matthias Brugger wrote:
> 
> 
> On 14/02/2020 07:42, CK Hu wrote:
>> Hi, Matthias:
>>
>> On Thu, 2020-02-13 at 21:19 +0100, matthias.bgg@...nel.org wrote:
>>> From: Matthias Brugger <mbrugger@...e.com>
>>>
>>> The mmsys block provides registers and clocks for the display
>>> subsystem. The binding description should therefore live together with
>>> the rest of the display descriptions. Move it to display/mediatek.
>>>
>>
>> Yes, for the upstreamed driver, only display (DRM) use mmsys clock. For
>> some MDP patches [1] in progress, MDP also use mmsys clock. So we just
>> consider what's upstreamed now?
> 

Let me jump into the discussion, and sorry if my question is silly because I'm
just starting to look at this code.

IMO we should consider all the cases to find a proper fix on all this, and if
MDP uses also mmsys clocks this approach will not work. I think the main problem
here and the big question is what exactly is the MMSYS block, is an independent
clock controller that provides clocks to DRM and other blocks? or is hardly tied
to the DRM block in some way?

Could you give us a block schema on how the things are interconnected?

If is an independent clock controller I think there was a mistake when the first
drm driver was pushed by using the compatible = "mediatek,mt8173-mmsys" as id
for that driver.

Thanks,
 Enric


> I'm not sure if I understand you correctly. Are you proposing to keep the
> binding description in arm/mediatek?
> 
> Regards,
> Matthias
> 
>>
>> [1] https://patchwork.kernel.org/patch/11140747/
>>
>> Regards,
>> CK
>>
>>> Signed-off-by: Matthias Brugger <mbrugger@...e.com>
>>>
>>> ---
>>>
>>> Changes in v7:
>>> - move the binding description
>>>
>>> Changes in v6: None
>>> Changes in v5: None
>>> Changes in v4: None
>>> Changes in v3: None
>>> Changes in v2: None
>>>
>>>  .../bindings/{arm => display}/mediatek/mediatek,mmsys.txt         | 0
>>>  1 file changed, 0 insertions(+), 0 deletions(-)
>>>  rename Documentation/devicetree/bindings/{arm => display}/mediatek/mediatek,mmsys.txt (100%)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,mmsys.txt
>>> similarity index 100%
>>> rename from Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt
>>> rename to Documentation/devicetree/bindings/display/mediatek/mediatek,mmsys.txt
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@...ts.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>

Powered by blists - more mailing lists