From: Stephen Boyd <sboyd@kernel.org>
To: "Köry Maincent" <kory.maincent@bootlin.com>,
"Michael Turquette" <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
thomas.petazzoni@bootlin.com, Viresh Kumar <vireshk@kernel.org>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
soc@kernel.org
Subject: Re: [PATCH v3 2/2] clk: spear: Fix SSP clock definition on SPEAr600
Date: Tue, 22 Nov 2022 18:04:14 -0800 [thread overview]
Message-ID: <20221123020416.27EF4C433D6@smtp.kernel.org> (raw)
In-Reply-To: <20221115135814.214388-3-kory.maincent@bootlin.com>
Quoting Köry Maincent (2022-11-15 05:58:13)
> From: Kory Maincent <kory.maincent@bootlin.com>
>
> There is no SPEAr600 device named "ssp-pl022.x". Instead, the description
> of the SSP (Synchronous Serial Port) was recently added to the Device Tree,
> and the device name is "xxx.spi", so we should associate the SSP gateable
> clock to these device names.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-23 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 13:58 [PATCH v3 0/2] Support new features to the SPEAr600 Köry Maincent
2022-11-15 13:58 ` [PATCH v3 1/2] clk: spear: Fix CLCD clock definition on SPEAr600 Köry Maincent
2022-11-23 2:04 ` Stephen Boyd
2022-11-15 13:58 ` [PATCH v3 2/2] clk: spear: Fix SSP " Köry Maincent
2022-11-23 2:04 ` Stephen Boyd [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=20221123020416.27EF4C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=arnd@arndb.de \
--cc=kory.maincent@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=shiraz.linux.kernel@gmail.com \
--cc=soc@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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).