From: Md Shofiqul Islam <shofiqtest@gmail.com>
To: u-boot@lists.denx.de
Cc: ian.ray@gehealthcare.com, HuanWang@gehealthcare.com,
brian.ruley@gehealthcare.com, martyn.welch@collabora.com,
hs@nabladev.com, lukma@denx.de, sbabic@nabladev.com,
festevam@gmail.com, Md Shofiqul Islam <shofiqtest@gmail.com>
Subject: [PATCH v2 0/2] imx6: fix LDB clock guard and clk0/clk1 swap
Date: Tue, 30 Jun 2026 15:39:49 +0300 [thread overview]
Message-ID: <20260630123951.13385-1-shofiqtest@gmail.com> (raw)
This v2 series fixes two issues with LDB display clock initialisation on
NXP i.MX6Q boards.
Changes since v1:
- Squashed original patches 1 and 3 into a single patch. Patch 3 was a
correction to patch 1 based on Brian Ruley's review feedback
(CONFIG_SPL_BUILD is too broad; CONFIG_SPL_VIDEO is the correct guard).
Folding them together makes the intent clearer.
- Fixed Fixes: SHA to meet the 12-character minimum.
Regarding checkpatch IS_ENABLED() warnings in patch 1/2:
The guards in drivers/clk/imx/clk-imx6q.c wrap a static function
definition and its call site. IS_ENABLED() cannot be used for function
definitions, so #if is the only option there. The board-file guards
follow the same established pattern in adjacent code.
Md Shofiqul Islam (2):
clk: imx6q: guard LDB clock init with appropriate video config
imx6: clock: fix clk0/clk1 swap in select_ldb_di_clock_source()
arch/arm/mach-imx/mx6/clock.c | 4 ++--
board/aristainetos/aristainetos.c | 2 ++
board/ge/b1x5v2/b1x5v2.c | 3 ++-
drivers/clk/imx/clk-imx6q.c | 6 +++---
4 files changed, 9 insertions(+), 6 deletions(-)
next reply other threads:[~2026-06-30 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 12:39 Md Shofiqul Islam [this message]
2026-06-30 12:39 ` [PATCH v2 1/2] clk: imx6q: guard LDB clock init with appropriate video config Md Shofiqul Islam
2026-06-30 12:39 ` [PATCH v2 2/2] imx6: clock: fix clk0/clk1 swap in select_ldb_di_clock_source() Md Shofiqul Islam
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=20260630123951.13385-1-shofiqtest@gmail.com \
--to=shofiqtest@gmail.com \
--cc=HuanWang@gehealthcare.com \
--cc=brian.ruley@gehealthcare.com \
--cc=festevam@gmail.com \
--cc=hs@nabladev.com \
--cc=ian.ray@gehealthcare.com \
--cc=lukma@denx.de \
--cc=martyn.welch@collabora.com \
--cc=sbabic@nabladev.com \
--cc=u-boot@lists.denx.de \
/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