From: Craig Tatlor <ctatlor97@gmail.com>
To: robh@kernel.org, viresh.kumar@linaro.org, mark.rutland@arm.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux@armlinux.org.uk, andy.gross@linaro.org,
david.brown@linaro.org, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-pm@vger.kernel.org, linux@arm.linux.org.uk
Subject: Re: [v9,04/15] clk: qcom: Add HFPLL driver
Date: Sun, 25 Mar 2018 20:33:41 +0100 [thread overview]
Message-ID: <20180325193341.27845-1-ctatlor97@gmail.com> (raw)
In-Reply-To: <520347148-27852-5-git-send-email-sricharan@codeaurora.org>
This doesn't seem to work correctly with the higher clocks on 8974pro, specifically 2150400000 hz or above, maybe its something to do with being bigger than an unsigned long.
When i try to set any higher frequency it jumps down to 300mhz.
WARNING: multiple messages have this Message-ID (diff)
From: ctatlor97@gmail.com (Craig Tatlor)
To: linux-arm-kernel@lists.infradead.org
Subject: [v9,04/15] clk: qcom: Add HFPLL driver
Date: Sun, 25 Mar 2018 20:33:41 +0100 [thread overview]
Message-ID: <20180325193341.27845-1-ctatlor97@gmail.com> (raw)
In-Reply-To: <520347148-27852-5-git-send-email-sricharan@codeaurora.org>
This doesn't seem to work correctly with the higher clocks on 8974pro, specifically 2150400000 hz or above, maybe its something to do with being bigger than an unsigned long.
When i try to set any higher frequency it jumps down to 300mhz.
next parent reply other threads:[~2018-03-25 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <520347148-27852-5-git-send-email-sricharan@codeaurora.org>
2018-03-25 19:33 ` Craig Tatlor [this message]
2018-03-25 19:33 ` [v9,04/15] clk: qcom: Add HFPLL driver Craig Tatlor
2018-03-26 9:47 ` sricharan
2018-03-26 9:47 ` sricharan at codeaurora.org
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=20180325193341.27845-1-ctatlor97@gmail.com \
--to=ctatlor97@gmail.com \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=viresh.kumar@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.