From: Stephen Boyd <sboyd@codeaurora.org>
To: Gabriel FERNANDEZ <gabriel.fernandez@st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Michael Turquette <mturquette@baylibre.com>,
Nicolas Pitre <nico@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"andrea.merello@gmail.com" <andrea.merello@gmail.com>,
"radoslaw.pietrzyk@gmail.com" <radoslaw.pietrzyk@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Ludovic BARRE <ludovic.barre@st.com>,
Olivier BIDEAU <olivier.bideau@st.com>,
Amelie DELAUNAY <amelie.delaunay@st.com>,
"gabriel.fernandez.st@gmail.com" <gabriel.fernandez.st@gmail.com>
Subject: Re: [RESEND PATCH v4] clk: stm32h7: Add stm32h743 clock driver
Date: Wed, 28 Jun 2017 08:59:56 -0700 [thread overview]
Message-ID: <20170628155956.GA5316@codeaurora.org> (raw)
In-Reply-To: <110cf67f-e1d6-1f99-953c-6b9639bb4910@st.com>
On 06/27, Gabriel FERNANDEZ wrote:
>
>
> On 06/22/2017 12:07 AM, Stephen Boyd wrote:
> > readl_poll_timeout?
> >
> if i use readl_poll_timeout (wich use 'ktime_get()') it can be
> operational only after the selection of clocksource ? (device_initcall).
> And then if a driver turn on a clock before, it could blocked the linux
> console ?
>
Ok. I wonder if we could add some sort of starting check to
readl_poll_timeout() that tests system_state for booting vs.
scheduling? That should be sufficient to handle this case?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v4] clk: stm32h7: Add stm32h743 clock driver
Date: Wed, 28 Jun 2017 08:59:56 -0700 [thread overview]
Message-ID: <20170628155956.GA5316@codeaurora.org> (raw)
In-Reply-To: <110cf67f-e1d6-1f99-953c-6b9639bb4910@st.com>
On 06/27, Gabriel FERNANDEZ wrote:
>
>
> On 06/22/2017 12:07 AM, Stephen Boyd wrote:
> > readl_poll_timeout?
> >
> if i use readl_poll_timeout (wich use 'ktime_get()') it can be
> operational only after the selection of clocksource ? (device_initcall).
> And then if a driver turn on a clock before, it could blocked the linux
> console ?
>
Ok. I wonder if we could add some sort of starting check to
readl_poll_timeout() that tests system_state for booting vs.
scheduling? That should be sufficient to handle this case?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Gabriel FERNANDEZ <gabriel.fernandez-qxv4g6HH51o@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Maxime Coquelin
<mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre TORGUE <alexandre.torgue-qxv4g6HH51o@public.gmane.org>,
Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Nicolas Pitre <nico-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
"daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"andrea.merello-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<andrea.merello-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"radoslaw.pietrzyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<radoslaw.pietrzyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RESEND PATCH v4] clk: stm32h7: Add stm32h743 clock driver
Date: Wed, 28 Jun 2017 08:59:56 -0700 [thread overview]
Message-ID: <20170628155956.GA5316@codeaurora.org> (raw)
In-Reply-To: <110cf67f-e1d6-1f99-953c-6b9639bb4910-qxv4g6HH51o@public.gmane.org>
On 06/27, Gabriel FERNANDEZ wrote:
>
>
> On 06/22/2017 12:07 AM, Stephen Boyd wrote:
> > readl_poll_timeout?
> >
> if i use readl_poll_timeout (wich use 'ktime_get()') it can be
> operational only after the selection of clocksource ? (device_initcall).
> And then if a driver turn on a clock before, it could blocked the linux
> console ?
>
Ok. I wonder if we could add some sort of starting check to
readl_poll_timeout() that tests system_state for booting vs.
scheduling? That should be sufficient to handle this case?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-28 15:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 6:59 [RESEND PATCH v4] clk: stm32h7: Add stm32h743 clock driver gabriel.fernandez
2017-06-07 6:59 ` gabriel.fernandez
2017-06-07 6:59 ` gabriel.fernandez at st.com
2017-06-21 22:07 ` Stephen Boyd
2017-06-21 22:07 ` Stephen Boyd
2017-06-22 14:20 ` Gabriel FERNANDEZ
2017-06-22 14:20 ` Gabriel FERNANDEZ
2017-06-22 14:20 ` Gabriel FERNANDEZ
2017-06-22 14:20 ` Gabriel FERNANDEZ
2017-06-27 12:17 ` Gabriel FERNANDEZ
2017-06-27 12:17 ` Gabriel FERNANDEZ
2017-06-27 12:17 ` Gabriel FERNANDEZ
2017-06-27 12:17 ` Gabriel FERNANDEZ
2017-06-28 15:59 ` Stephen Boyd [this message]
2017-06-28 15:59 ` Stephen Boyd
2017-06-28 15:59 ` Stephen Boyd
2017-06-29 13:41 ` Gabriel FERNANDEZ
2017-06-29 13:41 ` Gabriel FERNANDEZ
2017-06-29 13:41 ` Gabriel FERNANDEZ
2017-06-29 13:41 ` Gabriel FERNANDEZ
2017-06-30 0:20 ` Stephen Boyd
2017-06-30 0:20 ` Stephen Boyd
2017-06-30 0:20 ` Stephen Boyd
2017-06-30 7:14 ` Gabriel FERNANDEZ
2017-06-30 7:14 ` Gabriel FERNANDEZ
2017-06-30 7:14 ` Gabriel FERNANDEZ
2017-06-30 7:14 ` Gabriel FERNANDEZ
2017-06-30 18:54 ` Stephen Boyd
2017-06-30 18:54 ` Stephen Boyd
2017-06-30 18:54 ` Stephen Boyd
2017-07-05 9:27 ` Gabriel FERNANDEZ
2017-07-05 9:27 ` Gabriel FERNANDEZ
2017-07-05 9:27 ` Gabriel FERNANDEZ
2017-07-05 9:27 ` Gabriel FERNANDEZ
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=20170628155956.GA5316@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=andrea.merello@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez.st@gmail.com \
--cc=gabriel.fernandez@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nico@linaro.org \
--cc=olivier.bideau@st.com \
--cc=radoslaw.pietrzyk@gmail.com \
--cc=robh+dt@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 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.