From: Stefan Wahren <info@lategoodbye.de>
To: Martin Sperl <kernel@martin.sperl.org>, Eric Anholt <eric@anholt.net>
Cc: linux-clk@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel <linux-rpi-kernel@lists.infradead.org>,
Remi Pommarel <repk@triplefau.lt>
Subject: Re: [PATCH 4/4] ARM: bcm2835: Switch to using the new clock driver support.
Date: Mon, 21 Dec 2015 19:08:56 +0100 [thread overview]
Message-ID: <56784038.402@lategoodbye.de> (raw)
In-Reply-To: <03BE10FE-D743-4CD3-8825-112D0F6B2D43@martin.sperl.org>
Hi,
[fix Michael's address and add Remi]
Am 21.12.2015 um 16:17 schrieb Martin Sperl:
>
> I started looking and found that drivers/clk/bcm/clk-bcm2835.c
> does not include the PWM clock either.
yes but please look at Remi's patch series first:
http://lists.infradead.org/pipermail/linux-rpi-kernel/2015-December/002672.html
Regards
Stefan
next prev parent reply other threads:[~2015-12-21 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 17:57 Raspberry Pi native clock driver Eric Anholt
2015-09-06 17:57 ` [PATCH 1/4] clk: bcm2835: Move under bcm/ with other Broadcom SoC clk drivers Eric Anholt
2015-09-07 6:48 ` Lee Jones
2015-09-08 19:22 ` Stephen Boyd
2015-10-01 14:43 ` Lee Jones
[not found] ` <1441562263-19888-1-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-09-06 17:57 ` [PATCH 2/4] clk: bcm2835: Add binding docs for the new platform clock driver Eric Anholt
2015-09-06 17:57 ` [PATCH 3/4] clk: bcm2835: Add support for programming the audio domain clocks Eric Anholt
2015-09-10 21:35 ` Eric Anholt
2015-09-06 17:57 ` [PATCH 4/4] ARM: bcm2835: Switch to using the new clock driver support Eric Anholt
2015-12-21 11:51 ` Martin Sperl
2015-12-21 12:42 ` Stefan Wahren
[not found] ` <5677F3C8.5000600-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
2015-12-21 15:17 ` Martin Sperl
2015-12-21 18:08 ` Stefan Wahren [this message]
2015-12-21 18:32 ` Martin Sperl
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=56784038.402@lategoodbye.de \
--to=info@lategoodbye.de \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=kernel@martin.sperl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=repk@triplefau.lt \
--cc=sboyd@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).