From: Eric Anholt <eric@anholt.net>
To: linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Stephen Boyd <sboyd@codeaurora.org>,
Mike Turquette <mturquette@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider
Date: Mon, 24 Aug 2015 17:31:38 -0700 [thread overview]
Message-ID: <87vbc4us2d.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1439507142-2965-2-git-send-email-eric@anholt.net>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Eric Anholt <eric@anholt.net> writes:
> The hardware clocks are not controllable by the ARM, so we have to
> make requests to the firmware to do so from the VPU side. This will
> let us replace fixed clocks in our DT with actual clock control (and
> correct frequency information).
Gordon from the Raspberry Pi Foundation just asked me "what do you mean,
you can't access the clocks from the ARM?" I'd been assured I couldn't
by another developer (who was originally going to write a Linux driver
for this), and my own testing had also indicated I couldn't, but after a
new round of hacking together some tests, I see things that look a lot
like clockman registers.
Looks like we're going to get a native driver, instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider
Date: Mon, 24 Aug 2015 17:31:38 -0700 [thread overview]
Message-ID: <87vbc4us2d.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1439507142-2965-2-git-send-email-eric@anholt.net>
Eric Anholt <eric@anholt.net> writes:
> The hardware clocks are not controllable by the ARM, so we have to
> make requests to the firmware to do so from the VPU side. This will
> let us replace fixed clocks in our DT with actual clock control (and
> correct frequency information).
Gordon from the Raspberry Pi Foundation just asked me "what do you mean,
you can't access the clocks from the ARM?" I'd been assured I couldn't
by another developer (who was originally going to write a Linux driver
for this), and my own testing had also indicated I couldn't, but after a
new round of hacking together some tests, I see things that look a lot
like clockman registers.
Looks like we're going to get a native driver, instead.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150824/8ff89ce0/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
To: linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Lee Jones <lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Mike Turquette
<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider
Date: Mon, 24 Aug 2015 17:31:38 -0700 [thread overview]
Message-ID: <87vbc4us2d.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1439507142-2965-2-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org> writes:
> The hardware clocks are not controllable by the ARM, so we have to
> make requests to the firmware to do so from the VPU side. This will
> let us replace fixed clocks in our DT with actual clock control (and
> correct frequency information).
Gordon from the Raspberry Pi Foundation just asked me "what do you mean,
you can't access the clocks from the ARM?" I'd been assured I couldn't
by another developer (who was originally going to write a Linux driver
for this), and my own testing had also indicated I couldn't, but after a
new round of hacking together some tests, I see things that look a lot
like clockman registers.
Looks like we're going to get a native driver, instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-08-25 0:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 23:05 Rasperry Pi clock support Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-13 23:05 ` [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-25 0:31 ` Eric Anholt [this message]
2015-08-25 0:31 ` Eric Anholt
2015-08-25 0:31 ` Eric Anholt
2015-08-13 23:05 ` [PATCH v5 2/3] clk: Add a Raspberry Pi-specific clock driver Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-15 4:28 ` Stephen Warren
2015-08-15 4:28 ` Stephen Warren
2015-08-15 4:28 ` Stephen Warren
2015-08-13 23:05 ` [PATCH v5 3/3] ARM: bcm2835: Add DT for the firmware clocks driver Eric Anholt
2015-08-13 23:05 ` Eric Anholt
2015-08-15 4:13 ` Stephen Warren
2015-08-15 4:13 ` Stephen Warren
2015-08-27 10:48 ` Lee Jones
2015-08-27 10:48 ` Lee Jones
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=87vbc4us2d.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.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.