linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Trimarchi <michael@amarulasolutions.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	linux-amarula@amarulasolutions.com
Subject: [RFC PATCH 0/3] Enable clk-critical to bd718x7
Date: Sun,  5 Jun 2022 19:02:59 +0200	[thread overview]
Message-ID: <20220605170300.1565632-1-michael@amarulasolutions.com> (raw)

The imx8mn cpu smms2 module is clocked by the pmic that provides
clk32K. If the pmic clk driver is loaded the device can not boot. This
series try to make this configuration possible. We mark the
pmic clock as critical.

Open question:
clock-critical is not documentated as dts properties and could be
clock-critical can be changed as no-int one.
This is a follow up of [1]

[1] https://lore.kernel.org/linux-devicetree/20220604183905.1025201-1-michael@amarulasolutions.com/T/#u

Michael Trimarchi (3):
  clk: bd718x7: Clean up the code, no functional changes
  clk: bd718x7: Enable the possibility to mark the clock as critical
  arm64: dts: imx8mn-bsh-smm-s2/pro: Add pmic clock connection

 .../freescale/imx8mn-bsh-smm-s2-common.dtsi   |  5 ++++
 drivers/clk/clk-bd718x7.c                     | 23 +++++++++++--------
 2 files changed, 19 insertions(+), 9 deletions(-)

-- 
2.25.1


                 reply	other threads:[~2022-06-05 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220605170300.1565632-1-michael@amarulasolutions.com \
    --to=michael@amarulasolutions.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).