dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Pavacic <pavacic.p@gmail.com>
To: neil.armstrong@linaro.org, sam@ravnborg.org, airlied@gmail.com,
	daniel@ffwll.ch, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Paulo Pavacic <pavacic.p@gmail.com>
Subject: [PATCH v4 0/3] drm/panel: add fannal c3004 panel
Date: Wed,  7 Jun 2023 17:11:24 +0200	[thread overview]
Message-ID: <20230607151127.1542024-1-pavacic.p@gmail.com> (raw)

Fannal C3004 is a 2 lane MIPI DSI 480x800 panel which requires initialization with DSI DCS
commands. After few initialization commands delay is required.

Paulo Pavacic (3):
  dt-bindings: add fannal vendor prefix
  dt-bindings: display: panel: add fannal,c3004
  drm/panel-fannal-c3004: Add fannal c3004 DSI panel

 .../bindings/display/panel/fannal,c3004.yaml  |  78 +++++
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 MAINTAINERS                                   |   6 +
 drivers/gpu/drm/panel/Kconfig                 |  11 +
 drivers/gpu/drm/panel/Makefile                |   1 +
 drivers/gpu/drm/panel/panel-fannal-c3004.c    | 314 ++++++++++++++++++
 6 files changed, 412 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/display/panel/fannal,c3004.yaml
 create mode 100644 drivers/gpu/drm/panel/panel-fannal-c3004.c

-- 
2.40.1


             reply	other threads:[~2023-06-07 15:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 15:11 Paulo Pavacic [this message]
2023-06-07 15:11 ` [PATCH v4 1/3] dt-bindings: add fannal vendor prefix Paulo Pavacic
2023-06-07 15:11 ` [PATCH v4 2/3] dt-bindings: display: panel: add fannal,c3004 Paulo Pavacic
2023-06-07 15:11 ` [PATCH v4 3/3] drm/panel-fannal-c3004: Add fannal c3004 DSI panel Paulo Pavacic
2023-06-15 19:54   ` Linus Walleij
2023-06-16  9:57     ` Paulo Pavacic
2023-06-16 11:43       ` Linus Walleij
2023-06-16 12:31         ` Paulo Pavacic
2023-06-16 12:52           ` Linus Walleij
2023-06-21 15:08             ` Paulo Pavacic
2023-06-22  8:22               ` Linus Walleij
2023-07-06 15:18                 ` Paulo Pavacic
2023-07-06 15:26                   ` Marek Vasut
2023-07-07 15:26                     ` Paulo Pavacic
2023-07-08 11:07                       ` Marek Vasut
2023-07-12 12:07                         ` Paulo Pavacic
2023-07-12 13:42                           ` Marek Vasut
2023-07-12 15:10                             ` Paulo Pavacic
2023-07-12 17:25                               ` Marek Vasut
2023-09-05  8:32                                 ` Paulo
2023-07-08  7:11                     ` Paulo Pavačić
2023-07-08  8:22                 ` Jagan Teki

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=20230607151127.1542024-1-pavacic.p@gmail.com \
    --to=pavacic.p@gmail.com \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    /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).