From: Shawn Guo <shawnguo@kernel.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Daniel Baluta <daniel.baluta@nxp.com>,
devicetree@vger.kernel.org, baruch@tkos.co.il, abel.vesa@nxp.com,
Anson.Huang@nxp.com, ccaione@baylibre.com,
andrew.smirnov@gmail.com, s.hauer@pengutronix.de, angus@akkea.ca,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
festevam@gmail.com, shengjiu.wang@nxp.com,
linux-arm-kernel@lists.infradead.org, l.stach@pengutronix.de
Subject: Re: [PATCH v4] arm64: dts: imx8mq: Init rates and parents configs for clocks
Date: Fri, 25 Oct 2019 10:31:12 +0800 [thread overview]
Message-ID: <20191025023110.GA30015@dragon> (raw)
In-Reply-To: <20191022161919.GA3727@bogon.m.sigxcpu.org>
On Tue, Oct 22, 2019 at 06:19:19PM +0200, Guido Günther wrote:
> Hi,
> On Sun, Jul 28, 2019 at 06:20:40PM +0300, Daniel Baluta wrote:
> > From: Abel Vesa <abel.vesa@nxp.com>
> >
> > Add the initial configuration for clocks that need default parent and rate
> > setting. This is based on the vendor tree clock provider parents and rates
> > configuration except this is doing the setup in dts rather then using clock
> > consumer API in a clock provider driver.
> >
> > Note that by adding the initial rate setting for audio_pll1/audio_pll
> > setting we need to remove it from imx8mq-librem5-devkit.dts
>
> It seems this never made it into any tree, any particular reason for
> that?
There is some discussion going on and I haven't seen it reaches an
explicit agreement.
Shawn
prev parent reply other threads:[~2019-10-25 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 15:20 [PATCH v4] arm64: dts: imx8mq: Init rates and parents configs for clocks Daniel Baluta
2019-07-29 12:48 ` Guido Günther
2019-08-21 20:39 ` Leonard Crestez
[not found] ` <1571812158.5953.2.camel@nxp.com>
2019-10-23 8:38 ` Leonard Crestez
2019-10-22 16:19 ` Guido Günther
2019-10-25 2:31 ` Shawn Guo [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=20191025023110.GA30015@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=andrew.smirnov@gmail.com \
--cc=angus@akkea.ca \
--cc=baruch@tkos.co.il \
--cc=ccaione@baylibre.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shengjiu.wang@nxp.com \
/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).