mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master 0/3] clk: imx: composite-8m: fix muxing of core and bus
Date: Mon, 22 Apr 2024 13:26:00 +0200	[thread overview]
Message-ID: <171378516026.1398297.1314384820112926148.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240419061003.2590849-1-a.fatoum@pengutronix.de>


On Fri, 19 Apr 2024 08:10:00 +0200, Ahmad Fatoum wrote:
> The i.MX8M differntiates between three types of composite clocks (called
> slices): Core, Bus and IP (peripheral) clocks. How muxes are configured
> differs between these clocks, so the driver is populating a mux_ops
> variable to point at the correct struct clk_ops.
> 
> Unfortunately, mux_ops wasn't actually used, leading to barebox hangs,
> depending on the assigned-clock-parents properties in the device tree.
> 
> [...]

Applied, thanks!

[1/3] clk: imx: add IMX_COMPOSITE_CLK_FLAGS_DEFAULT macro
      https://git.pengutronix.de/cgit/barebox/commit/?id=fb6c852f5b87 (link may not be stable)
[2/3] clk: imx: composite-8m: fix muxing of core and bus clocks
      https://git.pengutronix.de/cgit/barebox/commit/?id=4ec1f1d2887f (link may not be stable)
[3/3] clk: imx: imx8mp: sync with Linux v6.9-rc3
      https://git.pengutronix.de/cgit/barebox/commit/?id=ed8dad10eac8 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-04-22 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  6:10 Ahmad Fatoum
2024-04-19  6:10 ` [PATCH master 1/3] clk: imx: add IMX_COMPOSITE_CLK_FLAGS_DEFAULT macro Ahmad Fatoum
2024-04-19  6:10 ` [PATCH master 2/3] clk: imx: composite-8m: fix muxing of core and bus clocks Ahmad Fatoum
2024-04-19  6:10 ` [PATCH master 3/3] clk: imx: imx8mp: sync with Linux v6.9-rc3 Ahmad Fatoum
2024-04-22 11:26 ` Sascha Hauer [this message]

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=171378516026.1398297.1314384820112926148.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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