From: Maxime Jourdan <mjourdan@baylibre.com>
To: devicetree@vger.kernel.org
Cc: Maxime Jourdan <mjourdan@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: dts: meson: add simple-framebuffer nodes
Date: Mon, 7 Jan 2019 10:53:05 +0100 [thread overview]
Message-ID: <20190107095307.15233-1-mjourdan@baylibre.com> (raw)
This patch series adds support for simplefb for the GXBB and GXL chips.
simple-framebuffer allows sharing a framebuffer already setup by the
firmware to the kernel for a seamless boot transition.
It goes along with a u-boot patch series adding display support to
GXBB & GXL that is not sent yet.
Changes since v1 [1]:
- added cover letter
- added simple-framebuffer compatible fallback to the bindings
- Updated node names and removed the unit-address
- Consolidated base nodes in meson-gx.dtsi
[1] https://patchwork.kernel.org/patch/10720879/
Maxime Jourdan (2):
dt-bindings: meson: add specific simplefb bindings
arm64: dts: meson-gx: add support for simplefb
.../display/simple-framebuffer-meson.txt | 33 +++++++++++++++++++
arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 22 +++++++++++++
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++++
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 6 ++++
4 files changed, 67 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer-meson.txt
--
2.20.1
next reply other threads:[~2019-01-07 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 9:53 Maxime Jourdan [this message]
2019-01-07 9:53 ` [PATCH v2 1/2] dt-bindings: meson: add specific simplefb bindings Maxime Jourdan
2019-01-11 22:25 ` Rob Herring
2019-01-16 12:27 ` Maxime Jourdan
2019-01-07 9:53 ` [PATCH v2 2/2] arm64: dts: meson-gx: add support for simplefb Maxime Jourdan
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=20190107095307.15233-1-mjourdan@baylibre.com \
--to=mjourdan@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh@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