linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel@martin.sperl.org (kernel at martin.sperl.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] reorganize clock initialization and add PCM clock
Date: Mon, 29 Feb 2016 12:51:40 +0000	[thread overview]
Message-ID: <1456750304-2424-1-git-send-email-kernel@martin.sperl.org> (raw)

From: Martin Sperl <kernel@martin.sperl.org>

As changing entries in the dt-bindings header files is frowned upon
and as we would need to change BCM2835_CLOCK_COUNT for every new
clock added, this patchset moves away from the use of
BCM2835_CLOCK_COUNT and removes it from the dt-bindings alltogether.

Instead - as recommended by Michael Turquette, Geert Uytterhoeven
and Remi Pommarel - patch 1 introduces a new initialization
process in probe that simply uses ARRAY_SIZE on a (sparse) array.

With patch 2 the initialization of the array is simplified and
better grouped together.

Patch 3 introduces the pcm clock of the bcm2835 soc and already
shows the simplification at work - the main reason for this patchset.

Martin Sperl (3):
  clk: bcm2835: remove use of BCM2835_CLOCK_COUNT in driver
  clk: bcm2835: reorganize bcm2835_clock_array assignment
  clk: bcm2835: enable management of PCM clock

 drivers/clk/bcm/clk-bcm2835.c       |  918 +++++++++++++++++------------------
 include/dt-bindings/clock/bcm2835.h |    3 +-
 2 files changed, 441 insertions(+), 480 deletions(-)

--
1.7.10.4

             reply	other threads:[~2016-02-29 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 12:51 kernel at martin.sperl.org [this message]
2016-02-29 12:51 ` [PATCH 1/3] clk: bcm2835: remove use of BCM2835_CLOCK_COUNT in driver kernel at martin.sperl.org
2016-02-29 12:51 ` [PATCH 2/3] clk: bcm2835: reorganize bcm2835_clock_array assignment kernel at martin.sperl.org
2016-02-29 12:51 ` [PATCH 3/3] clk: bcm2835: enable management of PCM clock kernel at martin.sperl.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=1456750304-2424-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).