From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] Tegra DMA clocks addition / correction
Date: Wed, 4 Oct 2017 02:02:37 +0300 [thread overview]
Message-ID: <cover.1507070638.git.digetx@gmail.com> (raw)
This patchset is factored out from the AHB DMA driver 'introduction' series
as per drivers/dma/ subsystem maintainer request.
Change log:
v2:
- Added patch that corrects parent of the APB DMA clock gate in the
'common' clock gate definition.
- Added patch that makes Tegra20 to utilize the 'common' APB DMA
clock gate definition.
Dmitry Osipenko (4):
clk: tegra: Add AHB DMA clock entry
clk: tegra: Correct parent of the APBDMA clock
clk: tegra20: Use common definition of APBDMA clock gate
clk: tegra20: Bump SCLK clock rate to 216MHz
drivers/clk/tegra/clk-id.h | 1 +
drivers/clk/tegra/clk-tegra-periph.c | 3 ++-
drivers/clk/tegra/clk-tegra20.c | 9 +++------
drivers/clk/tegra/clk-tegra30.c | 1 +
4 files changed, 7 insertions(+), 7 deletions(-)
--
2.14.1
next reply other threads:[~2017-10-03 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 23:02 Dmitry Osipenko [this message]
2017-10-03 23:02 ` [PATCH v2 1/4] clk: tegra: Add AHB DMA clock entry Dmitry Osipenko
2017-10-03 23:02 ` [PATCH v2 2/4] clk: tegra: Correct parent of the APBDMA clock Dmitry Osipenko
2017-10-03 23:02 ` [PATCH v2 3/4] clk: tegra20: Use common definition of APBDMA clock gate Dmitry Osipenko
2017-10-03 23:02 ` [PATCH v2 4/4] clk: tegra20: Bump SCLK clock rate to 216MHz Dmitry Osipenko
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=cover.1507070638.git.digetx@gmail.com \
--to=digetx@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=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@codeaurora.org \
--cc=thierry.reding@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
Powered by JetHome