From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] clk: tegra: set up proper EMC clock implementation for Tegra114
Date: Fri, 17 Apr 2026 09:52:50 +0300 [thread overview]
Message-ID: <CAPVz0n3SXHdTTE55MvwZeogYaTgg9mD8Jh3Yy3snnSkjgfcyJQ@mail.gmail.com> (raw)
In-Reply-To: <acadwXDbBi4y99e2@orome>
пт, 27 бер. 2026 р. о 17:10 Thierry Reding <thierry.reding@kernel.org> пише:
>
> On Mon, Jan 26, 2026 at 08:58:18PM +0200, Svyatoslav Ryhel wrote:
> > Remove current emc and emc_mux clocks and replace them with the proper EMC
> > clock implementation for correct EMC driver support.
> >
> > Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> > Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
> > ---
> > drivers/clk/tegra/clk-tegra114.c | 39 ++++++++++++++++++++------------
> > 1 file changed, 25 insertions(+), 14 deletions(-)
>
> Acked-by: Thierry Reding <treding@nvidia.com>
Hello clock subsystem maintainers!
May this patch be picked if everyone is fine with it? It is pretty
important for Tegra114 EMC driver to work properly.
Best regards,
Svyatoslav R.
next prev parent reply other threads:[~2026-04-17 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 18:58 [PATCH v1 0/1] " Svyatoslav Ryhel
2026-01-26 18:58 ` [PATCH v1 1/1] " Svyatoslav Ryhel
2026-03-27 15:10 ` Thierry Reding
2026-04-17 6:52 ` Svyatoslav Ryhel [this message]
2026-03-02 7:50 ` [PATCH v1 0/1] " Svyatoslav Ryhel
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=CAPVz0n3SXHdTTE55MvwZeogYaTgg9mD8Jh3Yy3snnSkjgfcyJQ@mail.gmail.com \
--to=clamor95@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@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