From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clk: mvebu: add AP806 core clock driver
Date: Mon, 22 Feb 2016 10:32:03 -0800 [thread overview]
Message-ID: <20160222183203.2278.60153@quark.deferred.io> (raw)
In-Reply-To: <20160222141617.GA14970@lunn.ch>
Quoting Andrew Lunn (2016-02-22 06:16:17)
> > Such information will come later, and we can rework the drivers and DT
> > bindings accordingly. Those DT bindings cannot be stable, as the
> > platform is under heavy development and we'll probably discover some
> > issues down the road.
>
> Hi Thomas
>
> Maybe add a big fat warning that the bindings are unstable, and the DT
> blob must be kept in sync with the kernel?
+1 and feel free to blame the lack of documentation. No one can expect
bindings to be finalized when the chip topology is not fully understood.
Regards,
Mike
>
> Andrew
next prev parent reply other threads:[~2016-02-22 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:34 [PATCH 0/3] clk: mvebu: initial support for AP806 clocks Thomas Petazzoni
2016-02-15 7:34 ` [PATCH 1/3] clk: unconditionally recurse into clk/mvebu/ Thomas Petazzoni
2016-02-15 8:33 ` Marcin Wojtas
2016-02-15 11:06 ` Gregory CLEMENT
2016-02-15 7:34 ` [PATCH 2/3] clk: mvebu: add AP806 core clock driver Thomas Petazzoni
2016-02-22 2:53 ` Rob Herring
2016-02-22 8:14 ` Thomas Petazzoni
2016-02-22 14:16 ` Andrew Lunn
2016-02-22 18:32 ` Michael Turquette [this message]
2016-02-22 19:42 ` Rob Herring
2016-02-22 20:23 ` Michael Turquette
2016-02-23 9:25 ` Thomas Petazzoni
2016-02-23 15:56 ` Thomas Petazzoni
2016-02-15 7:34 ` [PATCH 3/3] clk: mvebu: add AP806 ring " Thomas Petazzoni
2016-02-22 2:54 ` Rob Herring
2016-02-22 8:15 ` Thomas Petazzoni
2016-02-15 23:31 ` [PATCH 0/3] clk: mvebu: initial support for AP806 clocks Michael Turquette
2016-02-15 23:36 ` Michael Turquette
2016-02-17 14:23 ` Thomas Petazzoni
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=20160222183203.2278.60153@quark.deferred.io \
--to=mturquette@baylibre.com \
--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).