From: Harigovindan P <harigovi@codeaurora.org> To: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, devicetree@vger.kernel.org Cc: Harigovindan P <harigovi@codeaurora.org>, robdclark@gmail.com, seanpaul@chromium.org, sean@poorly.run Subject: [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Date: Mon, 16 Mar 2020 09:42:59 +0530 [thread overview] Message-ID: <20200316041301.23154-1-harigovi@codeaurora.org> (raw) Adding support for visionox rm69299 panel driver and adding bindings for the same panel. Harigovindan P (2): dt-bindings: display: add visionox rm69299 panel variant drm/panel: add support for rm69299 visionox panel driver .../display/panel/visionox,rm69299.yaml | 81 +++++ drivers/gpu/drm/panel/Kconfig | 8 + drivers/gpu/drm/panel/Makefile | 1 + .../gpu/drm/panel/panel-visionox-rm69299.c | 295 ++++++++++++++++++ 4 files changed, 385 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml create mode 100644 drivers/gpu/drm/panel/panel-visionox-rm69299.c -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Harigovindan P <harigovi@codeaurora.org> To: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, devicetree@vger.kernel.org Cc: sean@poorly.run, seanpaul@chromium.org, Harigovindan P <harigovi@codeaurora.org> Subject: [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Date: Mon, 16 Mar 2020 09:42:59 +0530 [thread overview] Message-ID: <20200316041301.23154-1-harigovi@codeaurora.org> (raw) Adding support for visionox rm69299 panel driver and adding bindings for the same panel. Harigovindan P (2): dt-bindings: display: add visionox rm69299 panel variant drm/panel: add support for rm69299 visionox panel driver .../display/panel/visionox,rm69299.yaml | 81 +++++ drivers/gpu/drm/panel/Kconfig | 8 + drivers/gpu/drm/panel/Makefile | 1 + .../gpu/drm/panel/panel-visionox-rm69299.c | 295 ++++++++++++++++++ 4 files changed, 385 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml create mode 100644 drivers/gpu/drm/panel/panel-visionox-rm69299.c -- 2.25.1 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-03-16 4:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-16 4:12 Harigovindan P [this message] 2020-03-16 4:12 ` [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P 2020-03-16 4:13 ` [PATCH v7 1/2] dt-bindings: display: add visionox rm69299 panel variant Harigovindan P 2020-03-16 4:13 ` Harigovindan P 2020-03-16 4:13 ` [PATCH v7 2/2] drm/panel: add support for rm69299 visionox panel driver Harigovindan P 2020-03-16 4:13 ` Harigovindan P 2020-03-16 4:16 [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P 2020-03-16 4:16 ` Harigovindan P
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=20200316041301.23154-1-harigovi@codeaurora.org \ --to=harigovi@codeaurora.org \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=freedreno@lists.freedesktop.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=robdclark@gmail.com \ --cc=sean@poorly.run \ --cc=seanpaul@chromium.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.