From: Abel Vesa <abel.vesa@linaro.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: imx@lists.linux.dev, NXP Linux Team <linux-imx@nxp.com>,
linux-clk@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] clk: imx: Updates for v6.15
Date: Tue, 11 Mar 2025 11:41:40 +0200 [thread overview]
Message-ID: <20250311094140.722154-1-abel.vesa@linaro.org> (raw)
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/abelvesa/linux.git/ tags/clk-imx-6.15
for you to fetch changes up to 06a61b5cb6a8638fa8823cd09b17233b29696fa2:
clk: imx8mp: inform CCF of maximum frequency of clocks (2025-03-03 19:02:15 +0200)
----------------------------------------------------------------
i.MX clock changes for 6.15
- Add missing AXI clock to the i.MX8MP AUDIOMIX in dt-bindings schema.
- Fix DSP and OCRAM_A parent clocks in i.MX8MP AUDIOMIX clock provider.
- Document vendor specific operating-mode property in i.MX8M clock
provider dt-bindings schema.
- Apply overdrive/nominal constraints based on DT property in i.MX8MP
clock provider.
----------------------------------------------------------------
Ahmad Fatoum (2):
dt-bindings: clock: imx8m: document nominal/overdrive properties
clk: imx8mp: inform CCF of maximum frequency of clocks
Laurentiu Mihalcea (2):
dt-bindings: clock: imx8mp: add axi clock
clk: clk-imx8mp-audiomix: fix dsp/ocram_a clock parents
.../devicetree/bindings/clock/imx8m-clock.yaml | 8 ++
.../devicetree/bindings/clock/imx8mp-audiomix.yaml | 10 +-
drivers/clk/imx/clk-imx8mp-audiomix.c | 6 +-
drivers/clk/imx/clk-imx8mp.c | 151 +++++++++++++++++++++
4 files changed, 168 insertions(+), 7 deletions(-)
next reply other threads:[~2025-03-11 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 9:41 Abel Vesa [this message]
2025-03-11 18:18 ` Stephen Boyd
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=20250311094140.722154-1-abel.vesa@linaro.org \
--to=abel.vesa@linaro.org \
--cc=imx@lists.linux.dev \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®