From: "André Draszik" <andre.draszik@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Peter Griffin <peter.griffin@linaro.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] clk: samsung: gs101: allow earlycon to work unconditionally
Date: Thu, 25 Jul 2024 08:14:02 +0100 [thread overview]
Message-ID: <90689f490cba6ea4b1bcd18c451630123a923f48.camel@linaro.org> (raw)
In-Reply-To: <c2c2b51d30f551bf8a9c1fb6507301bb.sboyd@kernel.org>
Hi Stephen,
On Thu, 2024-07-18 at 13:46 -0700, Stephen Boyd wrote:
> I don't see anything in here that's driver specific. Please move this to
> the clk framework, hook something like of_clk_add_provider() similar to
> how of_clk_set_defaults(), and have it look at the of_stdout node for
> 'clocks' to munge the clks in the core framework for the serial console.
That makes sense, I'll have a stab at that instead.
Cheers,
Andre'
next prev parent reply other threads:[~2024-07-25 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 17:09 [PATCH v4 0/2] gs101 oriole: UART clock fixes André Draszik
2024-07-12 17:09 ` [PATCH v4 1/2] clk: samsung: gs101: allow earlycon to work unconditionally André Draszik
2024-07-18 20:46 ` Stephen Boyd
2024-07-25 7:14 ` André Draszik [this message]
2024-07-12 17:09 ` [PATCH v4 2/2] clk: samsung: gs101: don't mark non-essential (UART) clocks critical André Draszik
2024-07-18 20:55 ` [PATCH v4 0/2] gs101 oriole: UART clock fixes Stephen Boyd
2024-07-25 7:12 ` André Draszik
2024-07-26 16:44 ` 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=90689f490cba6ea4b1bcd18c451630123a923f48.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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 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®