From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Stephen Boyd <sboyd@kernel.org>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
<claudiu.beznea@microchip.com>, <mturquette@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: <alexandre.belloni@bootlin.com>, <robh+dt@kernel.org>,
<rdunlap@infradead.org>, <unixbhaskar@gmail.com>,
<linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] clk: at91: sama7g5: Allow MCK1 to be exported and referenced in DT
Date: Fri, 25 Feb 2022 11:31:37 +0100 [thread overview]
Message-ID: <deb6ace6-adfc-bbaa-d31f-16d02a5f762b@microchip.com> (raw)
In-Reply-To: <20220125010554.BB92BC340E4@smtp.kernel.org>
On 25/01/2022 at 02:05, Stephen Boyd wrote:
> Quoting Tudor Ambarus (2022-01-11 04:53:10)
>> MCK1 feeds the External Bus Interface (EBI). EBI's clock rate is used
>> to translate EBI's timmings to SMC timings, thus we need to handle MCK1
>> in the EBI driver. Allow MCK1 to be referenced as a PMC_TYPE_CORE clock
>> from phandle in DT.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>> ---
>
> Applied to clk-next
Hi Stephen,
I depend on the PMC_MCK1 definition for some of the DT patches that I
must queue for my pull request to arm-soc, for 5.18.
Would you mind doing an immutable branch for me to pull from, so that
the build doesn't crash while the clock tree is not integrated yet with
my patches?
Tell me if there's a better way, as well.
Thanks, best regards,
Nicolas
--
Nicolas Ferre
next prev parent reply other threads:[~2022-02-25 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 12:53 [PATCH] clk: at91: sama7g5: Allow MCK1 to be exported and referenced in DT Tudor Ambarus
2022-01-11 15:23 ` Claudiu.Beznea
2022-01-25 1:05 ` Stephen Boyd
2022-02-25 10:31 ` Nicolas Ferre [this message]
2022-03-04 18:09 ` Nicolas Ferre
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=deb6ace6-adfc-bbaa-d31f-16d02a5f762b@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tudor.ambarus@microchip.com \
--cc=unixbhaskar@gmail.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).