From: Lee Jones <lee@kernel.org>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@tuxon.dev, lee@kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Manikandan Muralidharan <manikandan.m@microchip.com>
Cc: Dharma Balasubiramani <dharma.b@microchip.com>
Subject: Re: (subset) [PATCH v3 1/4] mfd: atmel-hlcdc: fetch LVDS PLL clock for LVDS display
Date: Fri, 06 Mar 2026 12:20:14 +0000 [thread overview]
Message-ID: <177279961448.979425.2188993103584319.b4-ty@kernel.org> (raw)
In-Reply-To: <20260223101920.284697-2-manikandan.m@microchip.com>
On Mon, 23 Feb 2026 15:49:17 +0530, Manikandan Muralidharan wrote:
> The XLCDC IP supports parallel RGB, MIPI DSI and LVDS Display.
> The LCD Generic clock (sys_clk) is used for Parallel RGB and MIPI
> displays, while the LVDS PLL clock (lvds_pll_clk) is used for LVDS
> displays.Since both the clocks cannot co-exist together in the DT
> for a given display, this patch tries sys_clk first (RGB/MIPI),
> fallback to lvds_pll_clk (LVDS).
>
> [...]
Applied, thanks!
[1/4] mfd: atmel-hlcdc: fetch LVDS PLL clock for LVDS display
commit: bd7b76604b3b218d0b5a32bcfaaed9eb4cc0ddb2
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-06 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 10:19 [PATCH v3 0/4] Add LVDS display support and PLL handling Manikandan Muralidharan
2026-02-23 10:19 ` [PATCH v3 1/4] mfd: atmel-hlcdc: fetch LVDS PLL clock for LVDS display Manikandan Muralidharan
2026-03-06 12:20 ` Lee Jones [this message]
2026-02-23 10:19 ` [PATCH v3 2/4] drm: atmel-hlcdc: configure LVDS PLL clock rate for LVDS Displays Manikandan Muralidharan
2026-02-23 10:19 ` [PATCH v3 3/4] drm: atmel-hlcdc: bypass clock divider for LVDS displays Manikandan Muralidharan
2026-02-23 10:19 ` [PATCH v3 4/4] drm: atmel-hlcdc: add support for LVDS output formats Manikandan Muralidharan
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=177279961448.979425.2188993103584319.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dharma.b@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=manikandan.m@microchip.com \
--cc=mripard@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®