From: Georgi Djakov <georgi.djakov@linaro.org>
To: Andy Gross <andy.gross@linaro.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH] arm64: dts: msm8916: Move smem below hwlock
Date: Wed, 24 Feb 2016 12:31:48 +0200 [thread overview]
Message-ID: <56CD8694.1070009@linaro.org> (raw)
In-Reply-To: <20160223190356.GA17346@hector.attlocal.net>
On 02/23/2016 09:03 PM, Andy Gross wrote:
> On Tue, Feb 23, 2016 at 08:47:56PM +0200, Georgi Djakov wrote:
>> On 23.02.16 г. 19:29, Srinivas Kandagatla wrote:
>>>
>>>
>>> On 23/02/16 17:21, Georgi Djakov wrote:
>>>> When the SMEM is probed it defers as it depends on the hardware lock, which
>>>> is not available yet. But the SMD bus and RPM regulators and clocks depend
>>>> on SMEM and they defer too. The problem with this is that the order of
>>>> registering the devices is not optimal and also we may end with messed
>>>> up serial console as the RPM clocks are not registered yet..
>>> I noticed the same issue but was wondering why would we end up with messed up serial console?
>>>
>>> Could you add more details on why serial console is messed up?
>>>
>>> I thought, serial driver has nothing to do with the rpm clocks directly!
>>>
>>
>> If we don't have the rpm clocks registered, the uart clock is an orphan
>> and when clk_get_rate() is called on orphan clocks it returns 0 as rate.
>> In our case the msm_serial driver calls clk_get_rate() and gets 0 rate
>> as the parent rpm clock has not registered yet. The result is that the
>> baudrate is set incorrectly.
>
> This isn't a probe defer issue w/ the SMEM and hwspinlock. That works properly.
Ok, agree.
> This is an issue with the msm_serial either not probe deferring to wait for the
> rpm clocks or not handling the case of the clk framework giving us a 'bogus'
> clock. Can we queue off the clk_get_rate being 0 to probe defer for the rpm
> clocks? (although that is hacky).
The proper solution would be to handle this in the clock framework.
next prev parent reply other threads:[~2016-02-24 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 17:21 [PATCH] arm64: dts: msm8916: Move smem below hwlock Georgi Djakov
2016-02-23 17:29 ` Srinivas Kandagatla
2016-02-23 18:47 ` Georgi Djakov
[not found] ` <56CCA95C.9070207-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-02-23 19:03 ` Andy Gross
2016-02-23 19:03 ` Andy Gross
2016-02-24 10:31 ` Georgi Djakov [this message]
2016-02-23 19:28 ` Srinivas Kandagatla
2016-02-23 20:18 ` Georgi Djakov
2016-02-23 17:39 ` Mark Rutland
2016-02-24 6:00 ` Bjorn Andersson
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=56CD8694.1070009@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=srinivas.kandagatla@linaro.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.