From: Sumit Garg <sumit.garg@kernel.org>
To: Casey Connolly <casey.connolly@linaro.org>
Cc: u-boot-qcom@groups.io, u-boot@lists.denx.de,
Neil Armstrong <neil.armstrong@linaro.org>,
Tom Rini <trini@konsulko.com>,
Andrew Goodbody <andrew.goodbody@linaro.org>,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH 1/2] serial: msm-geni: allow invalid clock
Date: Wed, 8 Apr 2026 17:05:41 +0530 [thread overview]
Message-ID: <adY9jXd1gYJrKsMk@sumit-xelite> (raw)
In-Reply-To: <ac78f01b-7aee-4658-b682-67d4f53cd40f@linaro.org>
On Wed, Apr 08, 2026 at 11:16:24AM +0200, Casey Connolly wrote:
> Hi Sumit,
>
> On 07/04/2026 13:38, Sumit Garg wrote:
> > On Fri, Mar 20, 2026 at 04:45:40PM +0100, Casey Connolly via B4 Relay wrote:
> >> From: Casey Connolly <casey.connolly@linaro.org>
> >>
> >> Pre-relocation we probably won't have a clock but it's usually
> >> been enabled for us already, or worst case we will enable it after
> >> relocation.
> >>
> >
> > Not sure if this is the right approach, since the UART driver might just
> > hang without clock being enabled. What's the motivation for this change?
>
> Hmm, I didn't consider that. The motivation here is to handle CCF, since
> we don't want to support clock pre-relocation. In pretty much all cases
> today the serial clocks are already configured but you're right that we
> ought not to depend on that.
I think this again comes down to that how CCF framework can enable
U-Boot SPL use-cases or where in U-Boot proper you get to work with an
uninitialized UART port for an OEM board variant.
>
> I can't really think of another good solution than hardcoding this clock
> configuration somewhere :/
>
That's true since we rely totally on DT based driver probing in U-Boot.
> Any ideas?
>
Have you tried working with DT properties like bootph-pre-ram etc. that
allows only say UART driver to probe before relocation with CCF?
-Sumit
next prev parent reply other threads:[~2026-04-08 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 15:45 [PATCH 0/2] qcom: gracefully handle some errors better Casey Connolly
2026-03-20 15:45 ` Casey Connolly via B4 Relay
2026-03-20 15:45 ` [PATCH 1/2] serial: msm-geni: allow invalid clock Casey Connolly
2026-03-20 15:45 ` Casey Connolly via B4 Relay
2026-04-07 11:38 ` Sumit Garg
2026-04-08 9:16 ` Casey Connolly
2026-04-08 11:35 ` Sumit Garg [this message]
2026-03-20 15:45 ` [PATCH 2/2] qcom: rpmh: don't error for SLEEP requests Casey Connolly
2026-03-20 15:45 ` Casey Connolly via B4 Relay
2026-03-24 10:59 ` [PATCH 0/2] qcom: gracefully handle some errors better Casey Connolly
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=adY9jXd1gYJrKsMk@sumit-xelite \
--to=sumit.garg@kernel.org \
--cc=andrew.goodbody@linaro.org \
--cc=casey.connolly@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=swboyd@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.