From: Remi Pommarel <repk@triplefau.lt>
To: Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-rpi-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Remi Pommarel <repk@triplefau.lt>
Subject: [PATCH 0/2] Add PWM clock support for bcm2835
Date: Thu, 5 Nov 2015 00:08:20 +0100 [thread overview]
Message-ID: <1446678502-16243-1-git-send-email-repk@triplefau.lt> (raw)
Hi,
This patchset add support for pwm clock. At boot, this clock does not have a
default parent nor a default rate set. Thus we should be able to change its
parent to get this clock working. The current clock implementation is using a
mux to select the parent, but these clocks need to add a password (0x5a) in
higher register bits when changing parent. So a generic mux cannot be used
here.
The first patch fix the clock parent selection, while the second one is actually
adding the pwm clock registration.
Remi Pommarel (2):
clk: bcm2835: Support for clock parent selection
clk: bcm2835: Add PWM clock support
arch/arm/boot/dts/bcm2835.dtsi | 8 ++
drivers/clk/bcm/clk-bcm2835.c | 144 ++++++++++++++++++++++++------------
include/dt-bindings/clock/bcm2835.h | 3 +-
3 files changed, 108 insertions(+), 47 deletions(-)
--
2.0.1
next reply other threads:[~2015-11-04 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 23:08 Remi Pommarel [this message]
2015-11-04 23:08 ` [PATCH 1/2] clk: bcm2835: Support for clock parent selection Remi Pommarel
2015-11-05 2:03 ` Eric Anholt
2015-11-05 18:53 ` Remi Pommarel
2015-11-09 16:38 ` Eric Anholt
2015-11-04 23:08 ` [PATCH 2/2] clk: bcm2835: Add PWM clock support Remi Pommarel
2015-11-05 2:17 ` Eric Anholt
2015-11-05 18:59 ` Remi Pommarel
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=1446678502-16243-1-git-send-email-repk@triplefau.lt \
--to=repk@triplefau.lt \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox