From: kernel@martin.sperl.org (kernel at martin.sperl.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ASOC: bcm2835: move bcm2835-i2s to use clock framework
Date: Sat, 9 Jan 2016 09:25:52 +0000 [thread overview]
Message-ID: <1452331558-2520-1-git-send-email-kernel@martin.sperl.org> (raw)
From: Martin Sperl <kernel@martin.sperl.org>
This patchset enables the bcm2835-i2s driver to use the clock
framework which was introduced with commit 94cb7f76caa0b337
("Switch to using the new clock driver support").
This commit resulted in the fact that the bcm2835-i2s driver was
no longer working due to some register addresses used by 2 drivers
(clk-bcm2835 and bcm2835-i2s).
To make it all possible this also required the introduction
of the PCM clock into the clk-bcm2835 driver. This patchset
relies on the patch by Remi Pommarel <repk@triplefau.lt>
that introduces the ability to set parent clocks
("clk: bcm2835: Support for clock parent selection"), which is
(as far as I understood) in clk-next and slated for 4.5.
Note that there is one regression: the clk-bcm2835 does not yet
support the mash functionality which the SOC-Hw supports, this
may result in slightly more "audiable noise" than the original
driver. But as this is more about making the driver functional
again, this is - I believe - a drawback we can accept for now.
Martin Sperl (5):
ASoC: bcm2835: cleanup includes by ordering them alphabetically
clk: bcm2835: enable management of PCM clock
ASoC: bcm2835: move to use the clock framework
ARM: bcm2835: I2S: use new register-range and clock framework
dt-bindings: bsm2835: fix bindings documentation to use new clock
framework
.../devicetree/bindings/sound/brcm,bcm2835-i2s.txt | 7 +-
arch/arm/boot/dts/bcm2835.dtsi | 5 +-
drivers/clk/bcm/clk-bcm2835.c | 15 +
include/dt-bindings/clock/bcm2835.h | 3 +-
sound/soc/bcm/bcm2835-i2s.c | 293 +++++---------------
5 files changed, 91 insertions(+), 232 deletions(-)
--
1.7.10.4
next reply other threads:[~2016-01-09 9:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 9:25 kernel at martin.sperl.org [this message]
2016-01-09 9:25 ` [PATCH 1/5] ASoC: bcm2835: cleanup includes by ordering them alphabetically kernel at martin.sperl.org
2016-01-09 9:25 ` [PATCH 2/5] clk: bcm2835: enable management of PCM clock kernel at martin.sperl.org
2016-01-09 20:56 ` Arnd Bergmann
2016-01-10 9:30 ` Geert Uytterhoeven
2016-01-10 10:55 ` Martin Sperl
2016-01-10 11:58 ` Mark Brown
2016-01-10 12:17 ` Martin Sperl
2016-01-10 12:30 ` Remi Pommarel
2016-01-10 13:02 ` Geert Uytterhoeven
2016-01-10 18:01 ` Martin Sperl
2016-01-10 18:56 ` Geert Uytterhoeven
2016-01-10 19:07 ` Martin Sperl
2016-01-10 19:13 ` Geert Uytterhoeven
2016-01-11 13:38 ` Arnd Bergmann
2016-01-11 13:53 ` Martin Sperl
2016-01-09 9:25 ` [PATCH 3/5] ASoC: bcm2835: move to use the clock framework kernel at martin.sperl.org
2016-01-09 9:25 ` [PATCH 4/5] ARM: bcm2835: I2S: use new register-range and " kernel at martin.sperl.org
2016-01-09 9:25 ` [PATCH 5/5] dt-bindings: bsm2835: fix bindings documentation to use new " kernel at martin.sperl.org
2016-01-09 22:45 ` Rob Herring
2016-01-10 11:05 ` 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=1452331558-2520-1-git-send-email-kernel@martin.sperl.org \
--to=kernel@martin.sperl.org \
--cc=linux-arm-kernel@lists.infradead.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).