Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp1105077pxb; Wed, 16 Feb 2022 11:06:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJxwoRwOAQDleqZzv5ern//lbajoWFY5+djDUe3U4RzBTusSp25B0TlCUaIpunn4w3G+PwwG X-Received: by 2002:a17:90a:3805:b0:1b9:3852:e3de with SMTP id w5-20020a17090a380500b001b93852e3demr3354587pjb.97.1645038394125; Wed, 16 Feb 2022 11:06:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645038394; cv=none; d=google.com; s=arc-20160816; b=afTeuxcaGFLUB/pGF+zBAsoDtmlAz/UElpHhLunY562EDQl/EwVHI7nSmROU57VW3I Z7pNiZhgFQL2uZsFp+OrO3V4flkTsmXo9nBUgy7X5vSBIJCfyFyqjVyPB+PGoRg2ONRG HS/EBVwX7O+vfbTgDhMXtUyr6ZM1hSjhP3ePpyc75X9OYmOiVB64EBhXugjdS9Bu1eib cyVv2suma2C7eJFzwbdLU9QMuwozLhJW2u8qKOCgpsWBGxtWD1bRg4oQIVmToC81A/UY gtUMDhq8PB26GDTgSXMHHU/7sKFRSmujCwigDF0GnkWumWv1i5agIA6o20VacrE1yc44 vczQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:sender:hmm_source_type :hmm_attache_num:hmm_source_ip; bh=iJUrmXTCR2HoOXfxLEOYeg3bXzR06twCaOUBUHHPQ6s=; b=MuBmWaL/CsY1YG0+9MiD2eR0j0dq/6/fP2pPSR6NgEZtNTaQOUjqcmRmjfG16gfrMi zxWNBmscv2JnL2A1mxcmXqRKk3IXBBUQSygpIhEVCUJsSaeYRS72CcAG2QQNxTWtzg9Y rUZQa9c3KMpBa7gBIo8uIW+2e7qziMUsYE46vJ38C0OpZN1RKzW3DLfasvZBHXHFMf3I PXoX2Qy4myQrNwC34TvuQW/5ncv7ZG8W10j7G5sOxbYFjBC+OaNU0bJRhnnEa5+Cp9aA OxN8WU5jOJSdolgliycrhiz8pNEHjyk9OdtIsZ8WPhtOikJmtpOfUnDdzm9FjGsoX6cc Gnjw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a192si6454241pge.213.2022.02.16.11.06.17; Wed, 16 Feb 2022 11:06:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237510AbiBPSRf (ORCPT + 99 others); Wed, 16 Feb 2022 13:17:35 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:35626 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231492AbiBPSRe (ORCPT ); Wed, 16 Feb 2022 13:17:34 -0500 Received: from 189.cn (ptr.189.cn [183.61.185.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C9F711BB730; Wed, 16 Feb 2022 10:17:19 -0800 (PST) HMM_SOURCE_IP: 10.64.8.41:34238.983927469 HMM_ATTACHE_NUM: 0000 HMM_SOURCE_TYPE: SMTP Received: from clientip-114.242.206.180 (unknown [10.64.8.41]) by 189.cn (HERMES) with SMTP id 31E6310019D; Thu, 17 Feb 2022 02:17:16 +0800 (CST) Received: from ([114.242.206.180]) by gateway-151646-dep-b7fbf7d79-9vctg with ESMTP id 2a2237147d534fe0926a8513cf1a3b35 for mripard@kernel.org; Thu, 17 Feb 2022 02:17:18 CST X-Transaction-ID: 2a2237147d534fe0926a8513cf1a3b35 X-Real-From: 15330273260@189.cn X-Receive-IP: 114.242.206.180 X-MEDUSA-Status: 0 Sender: 15330273260@189.cn From: Sui Jingfeng <15330273260@189.cn> To: Maxime Ripard , Thomas Zimmermann , Roland Scheidegger , Zack Rusin , Christian Gmeiner , David Airlie , Daniel Vetter , Rob Herring , Thomas Bogendoerfer , Dan Carpenter , Krzysztof Kozlowski , Andrey Zhizhikin , Sam Ravnborg , "David S . Miller" , Jiaxun Yang , Lucas Stach , Maarten Lankhorst , Ilia Mirkin , Qing Zhang , Li Yi , suijingfeng Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org, Joe Perches , Maxime Ripard , Randy Dunlap , kernel test robot Subject: [PATCH v8 0/3] drm/lsdc: add drm driver for loongson display controller Date: Thu, 17 Feb 2022 02:17:09 +0800 Message-Id: <20220216181712.1493400-1-15330273260@189.cn> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,FROM_LOCAL_DIGITS, FROM_LOCAL_HEX,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There is a display controller in loongson's LS2K1000 SoC and LS7A1000 bridge chip, it is a PCI device in those chips. It has two display pipes but with only one hardware cursor. Each way has a DVO interface which provide RGB888 signals, vertical & horizontal synchronisations, data enable and the pixel clock. Each CRTC is able to scanout from 1920x1080 resolution at 60Hz. The maxmium resolution is 2048x2048 according to the hardware spec. Loongson display controllers are simple which require scanout buffers to be physically contiguous. For LS7A1000/LS7A2000 bridge chip, the DC is equipped with a dedicated video ram which is typically 64MB or more. In this case, VRAM helper based driver is intend to be used. While LS2K1000 is a SoC, only system memory is available. Therefore CMA helper based driver is intend to be used. It is possible to use VRAM helper based solution by carving out part of system memory as VRAM though. 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 don't have such GPIO hardwared, they grab i2c adapter from other module, either general purpose GPIO emulated i2c or hardware i2c adapter. +------+ +-----------------------------------+ | 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 above picture give a simple usage of LS7A1000, note that the encoder is not necessary adv7125 or tfp410, other candicate encoders can be ch7034b, sil9022 and ite66121 lt8618 etc. v2: fixup warnings reported by kernel test robot v3: fix more grammar mistakes in Kconfig reported by Randy Dunlap and give more details about lsdc. v4: 1) Add dts required and explain why device tree is required. 2) Give more description about lsdc and vram helper base driver. 3) Fix warnings reported by kernel test robot. 4) Introduce stride_alignment member into struct lsdc_chip_desc, the stride alignment is 256 bytes for ls7a1000, ls2k1000 and ls2k0500. But ls7a2000 improve it to 32 bytes, for extend the support for the device on coming. v5: 1) using writel and readl replace writeq and readq, to fix kernel test robot report build error on other archtecture 2) set default fb format to XRGB8888 at crtc reset time. 3) fix typos. v6: 1) Explain why we are not switch to drm dridge subsystem on ls2k1000. 2) Explain why tiny drm driver is not suitable for us. 3) Give a short description of the trival dirty uppdate implement based on CMA helper. 4) code clean up v7: 1) Remove select I2C_GPIO and I2C_LS2X in Kconfig, it is not ready now 2) Licensing issues are fixed suggested by Krzysztof Kozlowski. 3) lsdc_pixpll_print() is removed, part of it move to debugfs. 4) Set prefer_shadow to true if vram based driver is in using. 5) Replace double blank lines with single line in all files 6) Verbose cmd line parameter is replaced with drm_dbg() 7) All warnnings reported by ./scripts/checkpatch.pl --strict are fixed 8) Get edid from dtb support is removed as suggested by Maxime Ripard 9) Fix typos and various improvement v8: 1) Drop damage update implement and its command line. 2) Drop DRM_LSDC_VRAM_DRIVER config option as suggested by Maxime. 3) Deduce DC's identification from its compatible property. 4) Drop the indroduction of board specific dts. 5) Add documention about the display controller device node. Below is a brief introduction of loongson's CPU, bridge chip and SoC. LS2K1000 is a double core 1.0Ghz mips64r2 compatible SoC[1]. LS7A1000 is a bridge chip made by Loongson corporation which act as north and/or south bridge of loongson's desktop and server level processor. It is equivalent to AMD RS780E+SB710 or something like that. More details can be read from its user manual[2]. This bridge chip is typically use with LS3A3000, LS3A4000 and LS3A5000 cpu. LS3A3000 is 4 core 1.45gHz mips64r2 compatible cpu. LS3A4000 is 4 core 1.8gHz mips64r5 compatible cpu[3]. LS3A5000 is 4 core 2.5gHz loongarch cpu[4]. Nearly all loongson cpu has the hardware maintain the cache coherency, except for early version of ls2k1000 or ls3a2000. This is the most distinct feature from other Mips cpu. [1] https://wiki.debian.org/InstallingDebianOn/Lemote/Loongson2K1000 [2] https://loongson.github.io/LoongArch-Documentation/Loongson-7A1000-usermanual-EN.html [3] https://ee-paper.com/loongson-3a4000-3b4000-motherboard-products-are-compatible-with-uos-system/ [4] https://loongson.github.io/LoongArch-Documentation/Loongson-3A5000-usermanual-EN.html [5] https://github.com/loongson-community/pmon Reported-by: Joe Perches Reported-by: Dan Carpenter Reported-by: Krzysztof Kozlowski Reported-by: Maxime Ripard Reported-by: Randy Dunlap Reported-by: kernel test robot Signed-off-by: suijingfeng Signed-off-by: Sui Jingfeng <15330273260@189.cn> suijingfeng (3): drm/lsdc: add drm driver for loongson display controller MIPS: Loongson64: dts: update the display controller device node MAINTAINERS: add maintainers for DRM LSDC driver .../loongson/loongson,display-controller.yaml | 114 +++ .../display/loongson/loongson-drm.txt | 16 + MAINTAINERS | 9 + .../boot/dts/loongson/loongson64-2k1000.dtsi | 8 + arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 7 +- drivers/gpu/drm/Kconfig | 2 + drivers/gpu/drm/Makefile | 1 + drivers/gpu/drm/lsdc/Kconfig | 21 + drivers/gpu/drm/lsdc/Makefile | 13 + drivers/gpu/drm/lsdc/lsdc_connector.c | 334 +++++++++ drivers/gpu/drm/lsdc/lsdc_connector.h | 38 + drivers/gpu/drm/lsdc/lsdc_crtc.c | 341 +++++++++ drivers/gpu/drm/lsdc/lsdc_drv.c | 699 ++++++++++++++++++ drivers/gpu/drm/lsdc/lsdc_drv.h | 209 ++++++ drivers/gpu/drm/lsdc/lsdc_encoder.c | 54 ++ drivers/gpu/drm/lsdc/lsdc_i2c.c | 198 +++++ drivers/gpu/drm/lsdc/lsdc_i2c.h | 40 + drivers/gpu/drm/lsdc/lsdc_irq.c | 60 ++ drivers/gpu/drm/lsdc/lsdc_irq.h | 20 + drivers/gpu/drm/lsdc/lsdc_plane.c | 526 +++++++++++++ drivers/gpu/drm/lsdc/lsdc_pll.c | 580 +++++++++++++++ drivers/gpu/drm/lsdc/lsdc_pll.h | 90 +++ drivers/gpu/drm/lsdc/lsdc_regs.h | 202 +++++ 23 files changed, 3577 insertions(+), 5 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml create mode 100644 Documentation/devicetree/bindings/display/loongson/loongson-drm.txt create mode 100644 drivers/gpu/drm/lsdc/Kconfig create mode 100644 drivers/gpu/drm/lsdc/Makefile create mode 100644 drivers/gpu/drm/lsdc/lsdc_connector.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_connector.h create mode 100644 drivers/gpu/drm/lsdc/lsdc_crtc.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_drv.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_drv.h create mode 100644 drivers/gpu/drm/lsdc/lsdc_encoder.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_i2c.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_i2c.h create mode 100644 drivers/gpu/drm/lsdc/lsdc_irq.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_irq.h create mode 100644 drivers/gpu/drm/lsdc/lsdc_plane.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_pll.c create mode 100644 drivers/gpu/drm/lsdc/lsdc_pll.h create mode 100644 drivers/gpu/drm/lsdc/lsdc_regs.h -- 2.25.1