From: Scott Wood <oss@buserror.net>
To: andy.tang@nxp.com, sboyd@kernel.org, mturquette@baylibre.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3 v2] powerpc/fsl: Use new clockgen binding
Date: Wed, 24 Oct 2018 12:41:16 -0500 [thread overview]
Message-ID: <7bceb12756766931772f2ec37f94ad8cdfeb0fd5.camel@buserror.net> (raw)
In-Reply-To: <20181024021122.3942-1-andy.tang@nxp.com>
On Wed, 2018-10-24 at 10:11 +0800, andy.tang@nxp.com wrote:
> From: Scott Wood <oss@buserror.net>
>
> The driver retains compatibility with old device trees, but we don't
> want the old nodes lying around to be copied, or used as a reference
> (some of the mux options are incorrect), or even just being clutter.
>
> We will also need the #clock-cells in the clockgen node in order to
> add fman nodes.
The comment about #clock-cells is no longer relevant to this patch, since that
has already been added.
-Scott
prev parent reply other threads:[~2018-10-24 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 2:11 [PATCH 1/3 v2] powerpc/fsl: Use new clockgen binding andy.tang
2018-10-24 2:11 ` [PATCH 2/3 v2] clk: qoriq: remove legacy bindings and add more compatibles andy.tang
2018-10-24 2:11 ` [PATCH 3/3 v2] clk: qoriq: update clock driver andy.tang
2018-10-24 18:37 ` Scott Wood
2018-10-25 2:40 ` Andy Tang
2018-10-24 22:10 ` [PATCH 2/3 v2] clk: qoriq: remove legacy bindings and add more compatibles Rob Herring
2018-10-25 2:41 ` Andy Tang
2018-10-24 17:41 ` Scott Wood [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=7bceb12756766931772f2ec37f94ad8cdfeb0fd5.camel@buserror.net \
--to=oss@buserror.net \
--cc=andy.tang@nxp.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=mturquette@baylibre.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).