From: Archit Taneja <architt@codeaurora.org>
To: robh@kernel.org
Cc: devicetree@vger.kernel.org, boris.brezillon@free-electrons.com,
linux-arm-msm@vger.kernel.org, briannorris@chromium.org,
philippe.cornu@st.com, dri-devel@lists.freedesktop.org,
tomi.valkeinen@ti.com, thierry.reding@gmail.com,
laurent.pinchart@ideasonboard.com,
maxime.ripard@free-electrons.com
Subject: [PATCH v3 0/2] dt-bindings: mipi-dsi: dual-channel DSI bindings
Date: Mon, 9 Jul 2018 14:37:49 +0530 [thread overview]
Message-ID: <20180709090751.10221-1-architt@codeaurora.org> (raw)
In-Reply-To: <20171205103356.9917-1-architt@codeaurora.org>
DSI host controllers these days can be ganged together to drive larger
displays. Every SoC vendor supporting this is trying to add their own
DT property so that the corresponding drivers can identify that they
need to operate in the dual DSI mode. If we use the graph bindings, we
don't really need an additional DT property in the DSI host controller
to tell it that it's operating in dual-channel mode. It's something that
can be inferred from the bindings itself.
The first patch adds some explanation on how to deal with peripherals
that do DSI, but have a different control bus. This is something we've
already started using, but didn't have properly documented anywhere.
The second patch proposes bindings for DSI hosts/peripherals that
implement dual-channel DSI.
Changes in v3:
- Fixed a minor typo.
- Added Reviewed-by tags.
- Changed from RFC to PATCH.
Changes in v2:
- Incorported Rob's comments.
Archit Taneja (2):
dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control
bus
dt-bindings: mipi-dsi: Add dual-channel DSI related info
.../devicetree/bindings/display/mipi-dsi-bus.txt | 153 +++++++++++++++++++--
1 file changed, 145 insertions(+), 8 deletions(-)
--
2.16.2
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-09 9:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:33 [RFC 0/2] dt-bindings: mipi-dsi: dual-channel DSI bindings Archit Taneja
2017-12-05 10:33 ` [RFC 1/2] dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control bus Archit Taneja
2017-12-06 21:39 ` Rob Herring
2017-12-07 15:12 ` Archit Taneja
[not found] ` <20171205103356.9917-1-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-12-05 10:33 ` [RFC 2/2] dt-bindings: mipi-dsi: Add dual-channel DSI related info Archit Taneja
[not found] ` <20171205103356.9917-3-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-12-06 21:42 ` Rob Herring
2018-01-18 4:53 ` [RFC v2 0/2] dt-bindings: mipi-dsi: dual-channel DSI bindings Archit Taneja
[not found] ` <20180118045355.8858-1-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-01-18 4:53 ` [RFC v2 1/2] dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control bus Archit Taneja
2018-01-18 14:55 ` Boris Brezillon
2018-01-19 10:22 ` Philippe CORNU
2018-01-29 18:51 ` Rob Herring
2018-01-29 20:09 ` Sean Paul
2018-01-18 4:53 ` [RFC v2 2/2] dt-bindings: mipi-dsi: Add dual-channel DSI related info Archit Taneja
2018-01-19 10:41 ` Philippe CORNU
2018-01-29 20:13 ` Sean Paul
2018-06-04 12:17 ` Heiko Stuebner
2018-06-06 5:59 ` Archit Taneja
2018-06-06 8:30 ` Heiko Stübner
2018-06-06 10:21 ` Archit Taneja
2018-06-06 10:46 ` Heiko Stübner
2018-06-06 16:07 ` Archit Taneja
2018-06-06 23:08 ` Heiko Stuebner
2018-06-07 10:39 ` Andrzej Hajda
2018-06-07 13:25 ` Heiko Stübner
2018-06-07 21:10 ` Brian Norris
2018-06-07 22:50 ` Heiko Stuebner
2018-06-08 8:47 ` Andrzej Hajda
2018-06-11 13:47 ` Heiko Stuebner
2018-07-09 9:07 ` Archit Taneja [this message]
2018-07-09 9:07 ` [PATCH v3 1/2] dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control bus Archit Taneja
2018-07-25 11:29 ` Archit Taneja
2018-07-09 9:07 ` [PATCH v3 2/2] dt-bindings: mipi-dsi: Add dual-channel DSI related info Archit Taneja
2018-07-11 15:48 ` Rob Herring
2018-07-25 11:29 ` Archit Taneja
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=20180709090751.10221-1-architt@codeaurora.org \
--to=architt@codeaurora.org \
--cc=boris.brezillon@free-electrons.com \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=philippe.cornu@st.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
/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).