From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sui jingfeng <suijingfeng@loongson.cn>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] Mips: ls2k1000: dts: add the display controller device node
Date: Thu, 23 Feb 2023 08:58:54 +0100 [thread overview]
Message-ID: <f1cb010c-be28-9b1b-da1f-93d5e2fb213f@kernel.org> (raw)
In-Reply-To: <32a56a81-e9b5-138b-4dff-35c2525cc0b6@loongson.cn>
On 23/02/2023 04:19, Sui jingfeng wrote:
> Hi,
>
> On 2023/2/23 02:32, Krzysztof Kozlowski wrote:
>> On 22/02/2023 17:55, suijingfeng wrote:
>>> The display controller is a pci device, it's pci vendor id is
>>> 0x0014, it's pci device id is 0x7a06.
>>>
>>> Signed-off-by: suijingfeng <suijingfeng@loongson.cn>
>>> ---
>>> .../boot/dts/loongson/loongson64-2k1000.dtsi | 21 +++++++++++++++++++
>>> 1 file changed, 21 insertions(+)
>>>
>>> diff --git a/arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi b/arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi
>>> index 8143a61111e3..a528af3977d9 100644
>>> --- a/arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi
>>> +++ b/arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi
>>> @@ -31,6 +31,18 @@ memory@200000 {
>>> <0x00000001 0x10000000 0x00000001 0xb0000000>; /* 6912 MB at 4352MB */
>>> };
>>>
>>> + reserved-memory {
>>> + #address-cells = <2>;
>>> + #size-cells = <2>;
>>> + ranges;
>>> +
>>> + display_reserved: framebuffer@30000000 {
>>> + compatible = "shared-dma-pool";
>>> + reg = <0x0 0x30000000 0x0 0x04000000>; /* 64M */
>>> + linux,cma-default;
>>> + };
>>> + };
>>> +
>>> cpu_clk: cpu_clk {
>>> #clock-cells = <0>;
>>> compatible = "fixed-clock";
>>> @@ -198,6 +210,15 @@ sata@8,0 {
>>> interrupt-parent = <&liointc0>;
>>> };
>>>
>>> + display-controller@6,0 {
>>> + compatible = "loongson,ls2k1000-dc";
>>> +
>>> + reg = <0x3000 0x0 0x0 0x0 0x0>;
>>> + interrupts = <28 IRQ_TYPE_LEVEL_LOW>;
>>> + interrupt-parent = <&liointc0>;
>>> + memory-region = <&display_reserved>;
>> NAK.
> Err :(, please give me a chance to explain
>> Test your code against the bindings you send.
>
> I can guarantee to you that I test may code more than twice. The code
> used to testing is listed at link [1].
I wrote - test against the bindings. I don't believe that it was tested.
Please paste the output of the testing (dtbs_check).
>
> This patchset mainly used to illustrate how we made the driver in [1]
> usable on our SoC platform.
>
>> It's the same
>> patchset. You basically send something which the same moment is incorrect.
>
> Loongson display controller IP has been integrated in both Loongson
> North Bridge chipset(ls7a1000 and ls7a2000) and Loongson SoCs(ls2k1000
> and ls2k2000 etc), it even has been included in Loongson BMC(ls2k0500 bmc)
> products.
I don't understand how your reply here is relevant to incorrect bindings
or incorrect DTS according to bindings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-23 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 16:55 [PATCH 1/2] Mips: ls2k1000: dts: add the display controller device node suijingfeng
2023-02-22 16:55 ` [PATCH 2/2] dt-bindings: display: Add Loongson display controller suijingfeng
2023-02-22 18:30 ` Krzysztof Kozlowski
2023-02-23 9:51 ` suijingfeng
2023-02-23 10:09 ` Krzysztof Kozlowski
2023-02-22 18:32 ` [PATCH 1/2] Mips: ls2k1000: dts: add the display controller device node Krzysztof Kozlowski
2023-02-23 3:19 ` Sui jingfeng
2023-02-23 7:58 ` Krzysztof Kozlowski [this message]
2023-02-23 8:05 ` Krzysztof Kozlowski
2023-02-23 8:21 ` suijingfeng
2023-02-23 8:38 ` Krzysztof Kozlowski
2023-02-23 8:40 ` suijingfeng
2023-02-23 8:59 ` Krzysztof Kozlowski
2023-02-23 9:17 ` suijingfeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1cb010c-be28-9b1b-da1f-93d5e2fb213f@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=suijingfeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).