linux-kernel - Re: [PATCH v6 2/3] dt-bindings: ls2k1000: add the display controller device node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3e34a508-3969-80d9-4ef7-7cb358c0147d@189.cn>
Date:   Wed, 16 Feb 2022 22:01:13 +0800
From:   Sui Jingfeng <15330273260@....cn>
To:     Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Dan Carpenter <dan.carpenter@...cle.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Maxime Ripard <mripard@...nel.org>,
        Roland Scheidegger <sroland@...are.com>,
        Zack Rusin <zackr@...are.com>,
        Christian Gmeiner <christian.gmeiner@...il.com>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Rob Herring <robh+dt@...nel.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Andrey Zhizhikin <andrey.zhizhikin@...ca-geosystems.com>,
        Sam Ravnborg <sam@...nborg.org>,
        suijingfeng <suijingfeng@...ngson.cn>,
        linux-mips@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v6 2/3] dt-bindings: ls2k1000: add the display controller
 device node


On 2022/2/3 16:50, Krzysztof Kozlowski wrote:
> On Thu, 3 Feb 2022 at 09:26, Sui Jingfeng <15330273260@....cn> wrote:
>> From: suijingfeng <suijingfeng@...ngson.cn>
>>
>> The display controller is a pci device, its vendor id is 0x0014
>> its device id is 0x7a06.
> The same as your patch 3 - these are not bindings.
>
> Best regards,
> Krzysztof

Yes, you are right. As there is no compatible string in my driver to match against the compatible
in the dc@6,1 device node.

I don't know how to write YAML document now, it seems no similar case can be reference?