From: Markuss Broks <markuss.broks@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Markuss Broks <markuss.broks@gmail.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
soc@kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH v2 0/3] Correct inaccuracies in Exynos5420 and Exynos5800 device trees
Date: Sat, 21 Jan 2023 22:16:47 +0200 [thread overview]
Message-ID: <20230121201650.46560-1-markuss.broks@gmail.com> (raw)
Use the proper compatibles for the DSI host controller and MIPI
video phy, as the current ones are not compatible with the hardware.
While this fixes the kernel panic while trying to use DSI, I was still
unsuccessful to consistently produce image that isn't noise on S6E3FA2
panel of Samsung Galaxy S5. It seems to only work sometimes.
Cc: Mark Brown <broonie@kernel.org>
v1 -> v2:
- squash patch 1 and patch 3, making it one patch for adding the label and
changing the compatible
- use better subject prefixes
Markuss Broks (2):
arm: dts: exynos5420: Use Exynos5420 compatible for the MIPI video phy
arm: dts: exynos5800: Use Exynos5422 compatible for the DSI controller
arch/arm/boot/dts/exynos5420.dtsi | 4 ++--
arch/arm/boot/dts/exynos5800.dtsi | 4 ++++
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-21 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 20:16 Markuss Broks [this message]
2023-01-21 20:16 ` [PATCH 1/2] arm: dts: exynos5420: Use Exynos5420 compatible for the MIPI video phy Markuss Broks
2023-01-21 20:16 ` [PATCH 2/2] arm: dts: exynos5800: Use Exynos5422 compatible for the DSI controller Markuss Broks
-- strict thread matches above, loose matches on Subject: below --
2023-01-21 20:18 [PATCH v2 0/3] Correct inaccuracies in Exynos5420 and Exynos5800 device trees Markuss Broks
2023-01-23 15:37 ` Krzysztof Kozlowski
2023-01-24 10:36 ` Krzysztof Kozlowski
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=20230121201650.46560-1-markuss.broks@gmail.com \
--to=markuss.broks@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@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).