From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: jacopo@jmondi.org, magnus.damm@gmail.com,
dri-devel@lists.freedesktop.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v2 0/8] Acer Chromebook R13 support
Date: Tue, 17 Oct 2017 19:38:15 +0300 [thread overview]
Message-ID: <3437221.yAhrl0lKkh@avalon> (raw)
In-Reply-To: <1508167900-27415-1-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Ulrich,
(CC'ing Matthias Brugger and Daniel Kurtz)
On Monday, 16 October 2017 18:31:32 EEST Ulrich Hecht wrote:
> Hi!
>
> This is a new revision of the Acer Chromebook R13 support series. It does
> not offer anything new in terms of functionality, but eliminates three out
> of four ugly hacks and adds a few minor cleanups; see below for details.
> Thanks to Robin Murphy and CK Hu for their comments and suggestions!
>
> I'm still looking for advice on how to implement the dual-role mmsys device
> correctly; see "hack: mediatek: get mmsys to register as both DRM and clock
> device" for details on this.
What I'd really like to find out is what the mmsys device is. Its DT binding
documents it as "The Mediatek mmsys controller provides various clocks to the
system". Even if it provides clocks to the display engine, it shouldn't be
used as the root device in the display complex. There could of course be
information I'm lacking as the datasheet isn't public. Hopefully someone from
Mediatek and/or Google will be able to comment on this.
> Like the previous revision, you can find this series at
> https://github.com/uli/kernel/tree/elm-working, which also contains a config
> file and several ancillary bits that are required to build a kernel
> partition for the Chromebook. Instructions on how to do so (and various
> other things that have to be done to get it running on your device) are
> available at
> https://www.elinux.org/User:Uli/Acer_Chromebook_R13_GPU_test_system (These
> instructions have been written for the vendor kernel, but apply to mainline
> as well, except that you won't need any extra patches.)
>
> CU
> Uli
>
> Changes since RFC v1:
> - cmdq: remove obsolete driver; not currently used anyway
> - dt: remove CD GPIO from mmc1, does not seem to be correct
> - mmc: remove mtk-sd.c revert hack (works fine without the CD pin)
> - dsi: fix port number for drm_of_find_panel_or_bridge(), remove hack
> - fbdev: add missing Signed-off-bys
> - iommu: remove io-pgtable sanity check hack, has been properly fixed
> - minor style fixes
>
>
> Ulrich Hecht (8):
> drm/bridge: GPIO-controlled display multiplexer driver
> platform/chrome: ChromeOS firmware interface driver
> drm/bridge: Parade PS8640 MIPI DSI -> eDP converter driver
> drm/bridge: Analogix ANX7688 HDMI -> DP bridge driver
> arm64: dts: mediatek: Add Elm Rev. 3 device tree
> hack: mediatek: get mmsys to register as both DRM and clock device
> drm/mediatek: Add DRM-based framebuffer device
> drm: mediatek: Fix drm_of_find_panel_or_bridge conversion
>
> arch/arm64/boot/dts/mediatek/Makefile | 1 +
> arch/arm64/boot/dts/mediatek/mt8173-elm-rev3.dts | 21 +
> arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi | 210 ++++
> arch/arm64/boot/dts/mediatek/mt8173-oak.dtsi | 1013 +++++++++++++++++++
> drivers/clk/mediatek/clk-mt8173.c | 4 +-
> drivers/gpu/drm/bridge/Kconfig | 32 +
> drivers/gpu/drm/bridge/Makefile | 5 +
> drivers/gpu/drm/bridge/analogix-anx7688.c | 233 +++++
> drivers/gpu/drm/bridge/generic-gpio-mux.c | 316 +++++++
> drivers/gpu/drm/bridge/parade-ps8640.c | 1104 +++++++++++++++++++
> drivers/gpu/drm/mediatek/Makefile | 2 +
> drivers/gpu/drm/mediatek/mtk_dpi.c | 5 +-
> drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 5 +-
> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 15 +
> drivers/gpu/drm/mediatek/mtk_drm_drv.h | 4 +-
> drivers/gpu/drm/mediatek/mtk_drm_fb.c | 13 +
> drivers/gpu/drm/mediatek/mtk_drm_fb.h | 3 +
> drivers/gpu/drm/mediatek/mtk_drm_fbdev.c | 181 ++++
> drivers/gpu/drm/mediatek/mtk_drm_fbdev.h | 32 +
> drivers/gpu/drm/mediatek/mtk_dsi.c | 2 +-
> drivers/gpu/drm/mediatek/mtk_hdmi.c | 5 +-
> drivers/platform/chrome/Kconfig | 18 +
> drivers/platform/chrome/Makefile | 2 +
> drivers/platform/chrome/chromeos.c | 120 +++
> drivers/platform/chrome/chromeos.h | 61 ++
> drivers/platform/chrome/chromeos_arm.c | 264 ++++++
> drivers/platform/chrome/elog.h | 186 ++++
> include/linux/chromeos_platform.h | 27 +
> 28 files changed, 3874 insertions(+), 10 deletions(-)
> create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm-rev3.dts
> create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi
> create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-oak.dtsi
> create mode 100644 drivers/gpu/drm/bridge/analogix-anx7688.c
> create mode 100644 drivers/gpu/drm/bridge/generic-gpio-mux.c
> create mode 100644 drivers/gpu/drm/bridge/parade-ps8640.c
> create mode 100644 drivers/gpu/drm/mediatek/mtk_drm_fbdev.c
> create mode 100644 drivers/gpu/drm/mediatek/mtk_drm_fbdev.h
> create mode 100644 drivers/platform/chrome/chromeos.c
> create mode 100644 drivers/platform/chrome/chromeos.h
> create mode 100644 drivers/platform/chrome/chromeos_arm.c
> create mode 100644 drivers/platform/chrome/elog.h
> create mode 100644 include/linux/chromeos_platform.h
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-17 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:31 [RFC v2 0/8] Acer Chromebook R13 support Ulrich Hecht
[not found] ` <1508167900-27415-1-git-send-email-ulrich.hecht+renesas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-16 15:31 ` [RFC v2 1/8] drm/bridge: GPIO-controlled display multiplexer driver Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 2/8] platform/chrome: ChromeOS firmware interface driver Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 3/8] drm/bridge: Parade PS8640 MIPI DSI -> eDP converter driver Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 4/8] drm/bridge: Analogix ANX7688 HDMI -> DP bridge driver Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 5/8] arm64: dts: mediatek: Add Elm Rev. 3 device tree Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 6/8] hack: mediatek: get mmsys to register as both DRM and clock device Ulrich Hecht
2017-10-16 15:31 ` [RFC v2 7/8] drm/mediatek: Add DRM-based framebuffer device Ulrich Hecht
[not found] ` <1508167900-27415-8-git-send-email-ulrich.hecht+renesas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-17 9:04 ` Philipp Zabel
2017-10-16 15:31 ` [RFC v2 8/8] drm: mediatek: Fix drm_of_find_panel_or_bridge conversion Ulrich Hecht
2017-10-17 10:33 ` [RFC v2 0/8] Acer Chromebook R13 support Matthias Brugger
2017-10-17 16:05 ` Sean Paul
2017-10-18 14:53 ` Ulrich Hecht
2017-10-18 15:57 ` Laurent Pinchart
2017-10-18 16:07 ` Laurent Pinchart
2017-10-18 15:58 ` Matthias Brugger
2017-10-17 16:38 ` Laurent Pinchart [this message]
2017-10-18 14:20 ` Matthias Brugger
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=3437221.yAhrl0lKkh@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo@jmondi.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=robin.murphy@arm.com \
--cc=ulrich.hecht+renesas@gmail.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).