From: Heiko Stuebner <heiko@sntech.de>
To: linux-kernel@vger.kernel.org, Andrzej Hajda <a.hajda@samsung.com>,
Nickey Yang <nickey.yang@rock-chips.com>,
Thomas Hebb <tommyhebb@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Brian Norris <briannorris@chromium.org>,
linux-rockchip@lists.infradead.org,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>, Sandy Huang <hjc@rock-chips.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH] drm/rockchip: dsi: move all lane config except LCDC mux to bind()
Date: Fri, 28 May 2021 20:09:44 +0200 [thread overview]
Message-ID: <162222530163.2887132.15086890641493370565.b4-ty@sntech.de> (raw)
In-Reply-To: <55fe7f3454d8c91dc3837ba5aa741d4a0e67378f.1618797813.git.tommyhebb@gmail.com>
On Sun, 18 Apr 2021 19:04:10 -0700, Thomas Hebb wrote:
> When we first enable the DSI encoder, we currently program some per-chip
> configuration that we look up in rk3399_chip_data based on the device
> tree compatible we match. This data configures various parameters of the
> MIPI lanes, including on RK3399 whether DSI1 is slaved to DSI0 in a
> dual-mode configuration. It also selects which LCDC (i.e. VOP) to scan
> out from.
>
> [...]
Applied, thanks!
[1/1] drm/rockchip: dsi: move all lane config except LCDC mux to bind()
commit: 43c2de1002d2b70fb5941fa14e97a34e3dc214d4
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2021-05-28 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 2:04 [RESEND PATCH] drm/rockchip: dsi: move all lane config except LCDC mux to bind() Thomas Hebb
2021-05-05 13:53 ` Jonathan Liu
2021-05-28 18:09 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 20:58 Thomas Hebb
2021-01-21 11:13 ` aleksandr.o.makarov
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=162222530163.2887132.15086890641493370565.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=briannorris@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nickey.yang@rock-chips.com \
--cc=seanpaul@chromium.org \
--cc=tommyhebb@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).