public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] soc/tegra: Turn on XUSB partitions
Date: Thu, 30 Jun 2016 15:24:18 +0200	[thread overview]
Message-ID: <20160630132418.GC26758@ulmo.ba.sec> (raw)
In-Reply-To: <1467284187-13320-1-git-send-email-jonathanh@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]

On Thu, Jun 30, 2016 at 11:56:23AM +0100, Jon Hunter wrote:
> The Tegra XHCI driver currently assumes the XUSB power partitions have
> been enabled by the bootloader. This is not for the Tegra210 Smaug board
> and so cause the kernel to hang when enabling XHCI support. Although the
> XHCI driver itself needs to manage these partitions, for now enable the
> partitions if the XHCI driver is enabled.
> 
> In order to do this I have made a fundamental change to the PMC driver
> to initialise the power partitions during early init. A benefit of this
> is that if CONFIG_PM_GENERIC_DOMAINS is not enabled, then we can simply
> turn on the partitions early before any devices are probed.
> 
> This is based upon the PMC fixes series [0].
> 
> Changes from initial RFC:
> - Added patch to add more detailed error messages when initialising
>   powergates.
> 
> [0] http://marc.info/?l=linux-tegra&m=146711078013182&w=2
> 
> Jon Hunter (4):
>   soc/tegra: pmc: Add specific error messages for initialising a
>     powergate
>   soc/tegra: pmc: Initialise power partitions early
>   soc/tegra: pmc: Enable XUSB partitions on boot
>   arm64: tegra210: Add XUSB powergates
> 
>  arch/arm64/boot/dts/nvidia/tegra210.dtsi | 24 +++++++++++++
>  drivers/soc/tegra/pmc.c                  | 60 +++++++++++++++++++++++---------
>  2 files changed, 67 insertions(+), 17 deletions(-)

Applied, thanks.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-06-30 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 10:56 [PATCH 0/4] soc/tegra: Turn on XUSB partitions Jon Hunter
2016-06-30 10:56 ` [PATCH 1/4] soc/tegra: pmc: Add specific error messages for initialising a powergate Jon Hunter
2016-06-30 10:56 ` [PATCH 2/4] soc/tegra: pmc: Initialise power partitions early Jon Hunter
2016-06-30 10:56 ` [PATCH 3/4] soc/tegra: pmc: Enable XUSB partitions on boot Jon Hunter
2016-06-30 10:56 ` [PATCH 4/4] arm64: tegra210: Add XUSB powergates Jon Hunter
2016-06-30 13:24 ` Thierry Reding [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=20160630132418.GC26758@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.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