public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: thierry.reding@gmail•com (Thierry Reding)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V3 2/6] soc/tegra: Move Tegra flowctrl driver
Date: Tue, 4 Apr 2017 16:01:03 +0200	[thread overview]
Message-ID: <20170404140103.GE843@ulmo.ba.sec> (raw)
In-Reply-To: <1490704978-22906-3-git-send-email-jonathanh@nvidia.com>

On Tue, Mar 28, 2017 at 01:42:54PM +0100, Jon Hunter wrote:
> The flowctrl driver is required for both ARM and ARM64 Tegra devices
> and in order to enable support for it for ARM64, move the Tegra flowctrl
> driver into drivers/soc/tegra.
> 
> By moving the flowctrl driver, tegra_flowctrl_init() is now called by
> via an early initcall and to prevent this function from attempting to
> mapping IO space for a non-Tegra device, a test for 'soc_is_tegra()'
> is also added.
> 
> Signed-off-by: Jon Hunter <jonathanh@nvidia•com>
> ---
>  arch/arm/mach-tegra/Makefile          |   1 -
>  arch/arm/mach-tegra/cpuidle-tegra20.c |   3 +-
>  arch/arm/mach-tegra/flowctrl.c        | 179 --------------------------------
>  arch/arm/mach-tegra/flowctrl.h        |  66 ------------
>  arch/arm/mach-tegra/platsmp.c         |   2 +-
>  arch/arm/mach-tegra/pm.c              |   2 +-
>  arch/arm/mach-tegra/reset-handler.S   |   2 +-
>  arch/arm/mach-tegra/sleep-tegra20.S   |   3 +-
>  arch/arm/mach-tegra/sleep-tegra30.S   |   2 +-
>  arch/arm/mach-tegra/tegra.c           |   2 -
>  drivers/soc/tegra/Kconfig             |   7 ++
>  drivers/soc/tegra/Makefile            |   1 +
>  drivers/soc/tegra/flowctrl.c          | 187 ++++++++++++++++++++++++++++++++++
>  include/soc/tegra/flowctrl.h          |  82 +++++++++++++++
>  14 files changed, 285 insertions(+), 254 deletions(-)
>  delete mode 100644 arch/arm/mach-tegra/flowctrl.c
>  delete mode 100644 arch/arm/mach-tegra/flowctrl.h
>  create mode 100644 drivers/soc/tegra/flowctrl.c
>  create mode 100644 include/soc/tegra/flowctrl.h

Applied to for-4.12/soc, thanks.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170404/53dd5447/attachment.sig>

  reply	other threads:[~2017-04-04 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 12:42 [PATCH V3 0/6] soc/tegra: Enable flowctrl support for Tegra132/210 Jon Hunter
2017-03-28 12:42 ` [PATCH V3 1/6] ARM: tegra: Remove unnecessary inclusion of flowctrl header Jon Hunter
2017-04-04 13:41   ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 2/6] soc/tegra: Move Tegra flowctrl driver Jon Hunter
2017-04-04 14:01   ` Thierry Reding [this message]
2017-03-28 12:42 ` [PATCH V3 3/6] soc/tegra: flowctrl: Add basic platform driver Jon Hunter
2017-04-04 14:01   ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 4/6] dt-bindings: tegra: Update compatible strings for Tegra flowctrl Jon Hunter
2017-04-03 14:29   ` Rob Herring
2017-04-04 14:01   ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 5/6] arm64: tegra: Update the Tegra132 flowctrl compatible string Jon Hunter
2017-04-04 14:01   ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 6/6] soc/tegra: Add initial flowctrl support for Tegra132/210 Jon Hunter
2017-04-04 14:02   ` Thierry Reding

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=20170404140103.GE843@ulmo.ba.sec \
    --to=thierry.reding@gmail$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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