From: Peng Fan <peng.fan@oss.nxp.com>
To: Brian Ruley <brian.ruley@gehealthcare.com>
Cc: festevam@gmail.com, Stefano Babic <sbabic@nabladev.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Tom Rini <trini@konsulko.com>, Heiko Schocher <hs@nabladev.com>,
Huan 'Kitty' Wang <HuanWang@gehealthcare.com>,
Ian Ray <ian.ray@gehealthcare.com>,
Martyn Welch <martyn.welch@collabora.com>,
lukma@denx.de, u-boot@lists.denx.de
Subject: Re: [PATCH v2 3/7] imx6: clock: allow different clock sources for ldb
Date: Wed, 29 Apr 2026 10:20:51 +0800 [thread overview]
Message-ID: <afFrA4Dst5lvEVc2@shlinux89> (raw)
In-Reply-To: <20260428085117.402523-3-brian.ruley@gehealthcare.com>
On Tue, Apr 28, 2026 at 11:51:08AM +0300, Brian Ruley wrote:
>The LDB clock sources don't have to be the same, so allow DI1 clock to
>be configured separately.
>
>Unlikely to be significant, but the reason will become apparent in the
>following commit.
>
>Signed-off-by: Brian Ruley <brian.ruley@gehealthcare.com>
I not see other patches in this thread. Have they been sent out to list?
Regards
Peng
next prev parent reply other threads:[~2026-04-29 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:51 [PATCH v2 1/7] clk: imx6q: cosmetic: keep pll definitions together Brian Ruley
2026-04-28 8:51 ` [PATCH v2 2/7] clk: imx6q: add missing pll bypasses Brian Ruley
2026-04-28 8:51 ` [PATCH v2 3/7] imx6: clock: allow different clock sources for ldb Brian Ruley
2026-04-29 2:20 ` Peng Fan [this message]
2026-04-29 11:22 ` Brian Ruley
2026-05-15 2:18 ` Fabio Estevam
2026-05-15 6:05 ` Brian Ruley
2026-04-28 8:51 ` [PATCH v2 4/7] clk: imx6q: configure ldb clock selectors Brian Ruley
2026-04-28 8:51 ` [PATCH v2 5/7] video: imx: ipuv3: enable ipu clk before writing registers in CCF Brian Ruley
2026-04-28 8:51 ` [PATCH v2 6/7] clk: clk-divider: add clk_register_divider_table() Brian Ruley
2026-04-28 8:51 ` [PATCH v2 7/7] clk: imx6q: use clk_divider_table instead of fixed factor for pll5 divs Brian Ruley
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=afFrA4Dst5lvEVc2@shlinux89 \
--to=peng.fan@oss.nxp.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=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.