devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Sui Jingfeng" <15330273260@189.cn>, "Rob Herring" <robh+dt@kernel.org>
Cc: "Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Roland Scheidegger" <sroland@vmware.com>,
	"Zack Rusin" <zackr@vmware.com>,
	"Christian Gmeiner" <christian.gmeiner@gmail.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Dan Carpenter" <dan.carpenter@oracle.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Andrey Zhizhikin" <andrey.zhizhikin@leica-geosystems.com>,
	"Sam Ravnborg" <sam@ravnborg.org>,
	"David S . Miller" <davem@davemloft.net>,
	"Lucas Stach" <l.stach@pengutronix.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Ilia Mirkin" <imirkin@alum.mit.edu>,
	"Qing Zhang" <zhangqing@loongson.cn>,
	suijingfeng <suijingfeng@loongson.cn>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v13 3/6] dt-bindings: display: Add Loongson display controller
Date: Wed, 30 Mar 2022 10:01:51 +0100	[thread overview]
Message-ID: <a777b827-32a2-46f8-9074-3f43c0bd87ba@www.fastmail.com> (raw)
In-Reply-To: <0a3a29af-ad2f-9ccc-3a56-3e5b7e4c7c83@189.cn>



在2022年3月30日三月 上午4:46,Sui Jingfeng写道:
> On 2022/3/29 21:27, Rob Herring wrote:
>> On Sun, Mar 27, 2022 at 9:29 PM Sui Jingfeng <15330273260@189.cn> wrote:
>>> Add DT bindings and simple usages for Loongson display controller
>>> found in LS7A1000 bridge chip and LS2k1000 SoC.
>>>
>>> Signed-off-by: Sui Jingfeng <15330273260@189.cn>
>>> ---
>>>   .../loongson/loongson,display-controller.yaml | 321 ++++++++++++++++++
>>>   1 file changed, 321 insertions(+)
>>>   create mode 100644 Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml b/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
>>> new file mode 100644
>>> index 000000000000..34060ed55a25
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
>>> @@ -0,0 +1,321 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/display/loongson/loongson,display-controller.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Loongson LS7A1000/LS2K1000/LS2K0500 Display Controller Device Tree Bindings
>>> +
>>> +maintainers:
>>> +  - Sui Jingfeng <suijingfeng@loongson.cn>
>>> +
>>> +description: |+
>>> +
>>> +  Loongson display controllers are simple which require scanout buffers
>>> +  to be physically contiguous. LS2K1000/LS2K0500 is a SOC, only system
>>> +  memory is available. LS7A1000/LS7A2000 is bridge chip which is equipped
>>> +  with a dedicated video RAM which is 64MB or more, precise size can be
>>> +  read from the PCI BAR 2 of the GPU device(0x0014:0x7A15) in the bridge
>>> +  chip.
>>> +
>>> +  LSDC has two display pipes, each way has a DVO interface which provide
>>> +  RGB888 signals, vertical & horizontal synchronisations, data enable and
>>> +  the pixel clock. LSDC has two CRTC, each CRTC is able to scanout from
>>> +  1920x1080 resolution at 60Hz. Each CRTC has two FB address registers.
>>> +
>>> +  For LS7A1000, there are 4 dedicated GPIOs whose control register is
>>> +  located at the DC register space. They are used to emulate two way i2c,
>>> +  One for DVO0, another for DVO1.
>>> +
>>> +  LS2K1000 and LS2K0500 SoC grab i2c adapter from other module, either
>>> +  general purpose GPIO emulated i2c or hardware i2c in the SoC.
>>> +
>>> +  LSDC's display pipeline have several components as below description,
>>> +
>>> +  The display controller in LS7A1000:
>>> +     ___________________                                     _________
>>> +    |            -------|                                   |         |
>>> +    |  CRTC0 --> | DVO0 ----> Encoder0 ---> Connector0 ---> | Monitor |
>>> +    |  _   _     -------|        ^             ^            |_________|
>>> +    | | | | |    -------|        |             |
>>> +    | |_| |_|    | i2c0 <--------+-------------+
>>> +    |            -------|
>>> +    |   DC IN LS7A1000  |
>>> +    |  _   _     -------|
>>> +    | | | | |    | i2c1 <--------+-------------+
>>> +    | |_| |_|    -------|        |             |             _________
>>> +    |            -------|        |             |            |         |
>>> +    |  CRTC1 --> | DVO1 ----> Encoder1 ---> Connector1 ---> |  Panel  |
>>> +    |            -------|                                   |_________|
>>> +    |___________________|
>>> +
>>> +  Simple usage of LS7A1000 with LS3A4000 CPU:
>>> +
>>> +    +------+            +------------------------------------+
>>> +    | DDR4 |            |  +-------------------+             |
>>> +    +------+            |  | PCIe Root complex |   LS7A1000  |
>>> +       || MC0           |  +--++---------++----+             |
>>> +  +----------+  HT 3.0  |     ||         ||                  |
>>> +  | LS3A4000 |<-------->| +---++---+  +--++--+     +---------+   +------+
>>> +  |   CPU    |<-------->| | GC1000 |  | LSDC |<--->| DDR3 MC |<->| VRAM |
>>> +  +----------+          | +--------+  +-+--+-+     +---------+   +------+
>>> +       || MC1           +---------------|--|-----------------+
>>> +    +------+                            |  |
>>> +    | DDR4 |          +-------+   DVO0  |  |  DVO1   +------+
>>> +    +------+   VGA <--|ADV7125|<--------+  +-------->|TFP410|--> DVI/HDMI
>>> +                      +-------+                      +------+
>>> +
>>> +  The display controller in LS2K1000/LS2K0500:
>>> +     ___________________                                     _________
>>> +    |            -------|                                   |         |
>>> +    |  CRTC0 --> | DVO0 ----> Encoder0 ---> Connector0 ---> | Monitor |
>>> +    |  _   _     -------|        ^              ^           |_________|
>>> +    | | | | |           |        |              |
>>> +    | |_| |_|           |     +------+          |
>>> +    |                   <---->| i2c0 |<---------+
>>> +    |   DC IN LS2K1000  |     +------+
>>> +    |  _   _            |     +------+
>>> +    | | | | |           <---->| i2c1 |----------+
>>> +    | |_| |_|           |     +------+          |            _________
>>> +    |            -------|        |              |           |         |
>>> +    |  CRTC1 --> | DVO1 ----> Encoder1 ---> Connector1 ---> |  Panel  |
>>> +    |            -------|                                   |_________|
>>> +    |___________________|
>>> +
>>> +properties:
>>> +  $nodename:
>>> +    pattern: "^display-controller@[0-9a-f],[0-9a-f]$"
>>> +
>>> +  compatible:
>>> +    oneOf:
>>> +      - items:
>>> +          - enum:
>>> +              - loongson,ls7a1000-dc
>>> +              - loongson,ls2k1000-dc
>>> +              - loongson,ls2k0500-dc
>>> +
>>> +  reg:
>>> +    maxItems: 1
>>> +
>>> +  interrupts:
>>> +    maxItems: 1
>>> +
>>> +  '#address-cells':
>>> +    const: 1
>>> +
>>> +  '#size-cells':
>>> +    const: 0
>>> +
>>> +  i2c@6:
>> NAK on made-up bus numbers. See v11 discussion for details.
>>
>> Rob
>
> I am worry about when this driver is loaded before the hardware i2c(on 
> the ls7a1000 bridge) driver,

That’s the problem that EPROBE_DEFER addressed.

>
> and when there is no DT support. in such a case, if i2c bus number is 
> dynamically assigned,
>
> it may incurring troubles.  Made the bus number fixed is benefit to the 
> whole system.
>
> DT  serve as a purpose to passing parameters to the kernel.  bus numbers 
> just a kind of parameters.
>
> this is my understanding toward DT. why you are so disagree about this?  
> what's the benefits of
>
> disallow put bus numbers it DT? to the whole world of developers who is 
> using DT?

There is nothing more to discuss.
You lack understanding to the fundamentals of the DT because you didn’t work
on thousands of platforms and being trapped by previous design failures.

Just follow the instructions from Rob, he is the expert. Is it that hard?

Thanks
-- 
- Jiaxun

  reply	other threads:[~2022-03-30  9:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  2:28 [PATCH v13 1/6] MIPS: Loongson64: dts: update the display controller device node Sui Jingfeng
2022-03-28  2:28 ` [PATCH v13 2/6] MIPS: Loongson64: introduce board specific dts and add model property Sui Jingfeng
2022-03-28  2:28 ` [PATCH v13 3/6] dt-bindings: display: Add Loongson display controller Sui Jingfeng
2022-03-29 13:27   ` Rob Herring
2022-03-30  3:46     ` Sui Jingfeng
2022-03-30  9:01       ` Jiaxun Yang [this message]
2022-03-28  2:28 ` [PATCH v13 4/6] MIPS: Loongson64: defconfig: enable display bridge drivers Sui Jingfeng
2022-03-28  2:28 ` [PATCH v13 5/6] drm/loongson: add drm driver for loongson display controller Sui Jingfeng
2022-03-28  8:51   ` kernel test robot
2022-03-28  9:01     ` Sui Jingfeng
2022-03-28 10:01       ` Jiaxun Yang
2022-03-28  2:28 ` [PATCH v13 6/6] MAINTAINERS: add maintainers for DRM LSDC driver Sui Jingfeng
  -- strict thread matches above, loose matches on Subject: below --
2022-03-27 14:40 [PATCH v13 0/6] drm/loongson: add drm driver for loongson display controller Sui Jingfeng
2022-03-27 14:40 ` [PATCH v13 3/6] dt-bindings: display: Add Loongson " Sui Jingfeng

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=a777b827-32a2-46f8-9074-3f43c0bd87ba@www.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=15330273260@189.cn \
    --cc=airlied@linux.ie \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel@ffwll.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=krzk@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sroland@vmware.com \
    --cc=suijingfeng@loongson.cn \
    --cc=tsbogend@alpha.franken.de \
    --cc=tzimmermann@suse.de \
    --cc=zackr@vmware.com \
    --cc=zhangqing@loongson.cn \
    /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).