mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] clk: meson: expose clk ids
Date: Tue, 1 Aug 2017 14:00:22 +0200	[thread overview]
Message-ID: <6494a76f-7282-cc39-c02a-0f1b2a8d83ff@baylibre.com> (raw)
In-Reply-To: <CAK8P3a28nb8QsJC8V4+SJM0gz70BDOv8jAczRWoCF+HfvkwJfA@mail.gmail.com>

On 07/31/2017 04:05 PM, Arnd Bergmann wrote:
> On Mon, Jul 31, 2017 at 1:38 PM, Jerome Brunet <jbrunet@baylibre.com> wrote:
>> In previous cycles, concerns have been raised about the way clocks are
>> exposed for the meson clock controller, only when validated and required
>> in DT.
>>
>> Instead, this patchset expose all the known clocks which may be needed in
>> DT later on. The clocks left out are internal clocks which should never be
>> used directly in DT. These are mostly internal muxes and dividers of
>> composite clocks.
>>
>> While this should reduce the patch flow on the related header files, It
>> won't stop it completely. There are still many clocks we don't know about
>> yet. We tend discover a few in every cycle.
>>
>> This patchset depends on these fixes [0] to avoid issues when adding new
>> clk ids.
>>
>> [0]: https://lkml.kernel.org/r/20170727161755.10393-1-jbrunet at baylibre.com
> 
> Thanks a lot!
> 
>  Acked-by: Arnd Bergmann <arnd@arndb.de>
> 

Applied to clk-meson's next/headers with arnd's ack.

      reply	other threads:[~2017-08-01 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 11:38 Jerome Brunet
2017-07-31 11:38 ` [PATCH 1/2] clk: meson8b: expose every clock in the bindings Jerome Brunet
2017-07-31 11:38 ` [PATCH 2/2] clk: meson-gxbb: expose almost " Jerome Brunet
2017-07-31 12:00 ` [PATCH 0/2] clk: meson: expose clk ids Neil Armstrong
2017-07-31 14:05 ` Arnd Bergmann
2017-08-01 12:00   ` Neil Armstrong [this message]

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=6494a76f-7282-cc39-c02a-0f1b2a8d83ff@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®