From: Lubomir Rintel <lkundrak@v3.sk>
To: Russell King <linux@armlinux.org.uk>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] dt-bindings: improve the Armada DRM bindings
Date: Mon, 4 Mar 2019 21:20:01 +0100 [thread overview]
Message-ID: <20190304202006.3863-1-lkundrak@v3.sk> (raw)
Hi,
this is the second spin of a patch set that aims to complete the Armada
DRM binding documentation. Compared to the first version it omits the
display-subsystem node and thus is somewhat simpler. Also, the
reserved-mem property has been moved to a separate documentation file.
The he individual patches are accompanied by more detailed change logs.
What is documented corresponds to the armada-devel branch of
git://git.armlinux.org.uk/~rmk/linux-arm.git with these differencies:
* Documentation of the bus-width property of the LCDC
* The MMP2 compatible strings.
Patches to the driver for the above were sent out separately.
Lubo
next reply other threads:[~2019-03-04 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 20:20 Lubomir Rintel [this message]
2019-03-04 20:20 ` [PATCH v2 1/5] dt-bindings: reserved-memory: Add binding for Armada framebuffer Lubomir Rintel
2019-03-12 18:42 ` Rob Herring
2019-03-04 20:20 ` [PATCH v2 2/5] dt-bindings: display: armada: Rename the binding doc file Lubomir Rintel
2019-03-04 20:20 ` [PATCH v2 3/5] dt-bindings: display: armada: Improve the LCDC documentation Lubomir Rintel
2019-03-12 18:42 ` Rob Herring
2019-03-04 20:20 ` [PATCH v2 4/5] dt-bindings: display: armada: Add more compatible strings Lubomir Rintel
2019-03-12 18:42 ` Rob Herring
2019-03-04 20:20 ` [PATCH v2 5/5] dt-bindings: display: armada: Document bus-width property Lubomir Rintel
2019-03-12 18:43 ` Rob Herring
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=20190304202006.3863-1-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).