From: Chris Morgan <macroalpha82@gmail.com>
To: devicetree@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
daniel@ffwll.ch, airlied@gmail.com, sam@ravnborg.org,
neil.armstrong@linaro.org, Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH V4 0/2] Support Anbernic RG351V Panel
Date: Tue, 3 Oct 2023 11:33:53 -0500 [thread overview]
Message-ID: <20231003163355.143704-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Add support for the Anbernic RG351V panel. This panel is mostly
identical to the one used in the 353 series, except it has a different
panel ID when queried (0x4000 for the 351V, 0x3052 for the 353 panel)
and will not work without the inclusion of the
MIPI_DSI_CLOCK_NON_CONTINUOUS flag.
Updates from V3:
- Removed need for defined variable in probe function.
Updates from V2:
- Modified the driver so that we only apply the
MIPI_DSI_CLOCK_NON_CONTINUOUS flag when the compatible matches
a panel (the 351v) that needs it.
- Updated the binding documentation to be consistent with existing
panels.
Updates from V1:
- Revised text in devicetree documentation to remove references to
specific hardware.
Chris Morgan (2):
dt-bindings: display: newvision,nv3051d: Add Anbernic 351V
drm/panel: nv3051d: Add Support for Anbernic 351V
.../bindings/display/panel/newvision,nv3051d.yaml | 5 ++---
drivers/gpu/drm/panel/panel-newvision-nv3051d.c | 7 +++++++
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Chris Morgan <macroalpha82@gmail.com>
To: devicetree@vger.kernel.org
Cc: neil.armstrong@linaro.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, sam@ravnborg.org,
Chris Morgan <macromorgan@hotmail.com>,
dri-devel@lists.freedesktop.org, robh+dt@kernel.org
Subject: [PATCH V4 0/2] Support Anbernic RG351V Panel
Date: Tue, 3 Oct 2023 11:33:53 -0500 [thread overview]
Message-ID: <20231003163355.143704-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Add support for the Anbernic RG351V panel. This panel is mostly
identical to the one used in the 353 series, except it has a different
panel ID when queried (0x4000 for the 351V, 0x3052 for the 353 panel)
and will not work without the inclusion of the
MIPI_DSI_CLOCK_NON_CONTINUOUS flag.
Updates from V3:
- Removed need for defined variable in probe function.
Updates from V2:
- Modified the driver so that we only apply the
MIPI_DSI_CLOCK_NON_CONTINUOUS flag when the compatible matches
a panel (the 351v) that needs it.
- Updated the binding documentation to be consistent with existing
panels.
Updates from V1:
- Revised text in devicetree documentation to remove references to
specific hardware.
Chris Morgan (2):
dt-bindings: display: newvision,nv3051d: Add Anbernic 351V
drm/panel: nv3051d: Add Support for Anbernic 351V
.../bindings/display/panel/newvision,nv3051d.yaml | 5 ++---
drivers/gpu/drm/panel/panel-newvision-nv3051d.c | 7 +++++++
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-03 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:33 Chris Morgan [this message]
2023-10-03 16:33 ` [PATCH V4 0/2] Support Anbernic RG351V Panel Chris Morgan
2023-10-03 16:33 ` [PATCH V4 1/2] dt-bindings: display: newvision,nv3051d: Add Anbernic 351V Chris Morgan
2023-10-03 16:33 ` [PATCH V4 1/2] dt-bindings: display: newvision, nv3051d: " Chris Morgan
2023-10-03 16:33 ` [PATCH V4 2/2] drm/panel: nv3051d: Add Support for " Chris Morgan
2023-10-03 16:33 ` Chris Morgan
2023-10-03 20:45 ` Jessica Zhang
2023-10-03 20:45 ` Jessica Zhang
2023-10-05 15:53 ` [PATCH V4 0/2] Support Anbernic RG351V Panel Neil Armstrong
2023-10-05 15:53 ` Neil Armstrong
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=20231003163355.143704-1-macroalpha82@gmail.com \
--to=macroalpha82@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=macromorgan@hotmail.com \
--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 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.