linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Timo Alho <talho@nvidia.com>,
	"open list:TEGRA ARCHITECTURE SUPPORT"
	<linux-tegra@vger.kernel.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 4/9] soc/tegra: Changes for v5.1-rc1
Date: Fri, 15 Feb 2019 22:42:07 +0100	[thread overview]
Message-ID: <20190215214207.GA12838@ulmo> (raw)
In-Reply-To: <CAK8P3a2tSaHsAOarZ8NHO-N4ZcLQL2rD2ti1rAe4meidWbVNEw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2064 bytes --]

On Fri, Feb 15, 2019 at 05:25:39PM +0100, Arnd Bergmann wrote:
> On Fri, Feb 8, 2019 at 4:09 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> 
> > ----------------------------------------------------------------
> > soc/tegra: Changes for v5.1-rc1
> >
> > This contains a couple of miscellaneous fixes for minor issues and a
> > largish rework of the PMC driver to make it work on systems where the
> > PMC has been locked down and can only be accessed from secure firmware.
> 
> Pulled into arm/drivers.
> 
> > ----------------------------------------------------------------
> > Jon Hunter (1):
> >       soc/tegra: pmc: Make tegra_powergate_is_powered() a local function
> >
> > Joseph Lo (1):
> >       soc/tegra: fuse: Fix typo in tegra210_init_speedo_data
> >
> > Mikko Perttunen (1):
> >       soc/tegra: pmc: Support systems where PMC is marked secure
> >
> > Thierry Reding (6):
> >       soc/tegra: pmc: Use TEGRA186_ prefix for GPIO names
> >       soc/tegra: pmc: Sort includes alphabetically
> >       soc/tegra: pmc: Add missing kerneldoc
> >       soc/tegra: pmc: Pass struct tegra_pmc * where possible
> >       soc/tegra: pmc: Make alignment consistent
> >       soc/tegra: pmc: Explicitly initialize all fields
> >
> > Timo Alho (1):
> >       soc/tegra: fuse: Fix illegal free of IO base address
> 
> Should that last one have been marked 'Cc:stable' ?

My understanding is that this currently only happens if we boot the
system using a DTB from a downstream build where these FUSE and BPMP
device tree nodes are sorted differently and therefore cause them to
be probed in the wrong order.

Booting an upstream kernel with a downstream DTB isn't known to work
very well in general. It's something that I hope we'll be able to do
in some distant future when the gap between upstream and downstream
DTBs has become sufficiently small, but I don't think we need to
bother fixing this in stable releases.

Adding Timo to clarify whether he thinks this is important enough to
backport.

Thierry

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-15 21:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 15:09 [GIT PULL 0/9] Tegra changes for v5.1-rc1 Thierry Reding
2019-02-08 15:09 ` [GIT PULL 1/9] clk: tegra: Changes " Thierry Reding
2019-02-15 16:30   ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 2/9] cpufreq: tegra: Add support for Tegra210 Thierry Reding
2019-02-15 16:28   ` Arnd Bergmann
2019-02-15 16:29     ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 3/9] dt-bindings: tegra: Changes for v5.1-rc1 Thierry Reding
2019-02-15 14:50   ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 4/9] soc/tegra: " Thierry Reding
2019-02-15 16:25   ` Arnd Bergmann
2019-02-15 21:42     ` Thierry Reding [this message]
2019-02-08 15:09 ` [GIT PULL 5/9] firmware: tegra: " Thierry Reding
2019-02-15 16:23   ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 6/9] ARM: tegra: Core changes " Thierry Reding
2019-02-15 16:48   ` Arnd Bergmann
2019-02-15 21:48     ` Thierry Reding
2019-02-16  0:03       ` Dmitry Osipenko
2019-02-16  1:00         ` Dmitry Osipenko
2019-02-08 15:09 ` [GIT PULL 7/9] ARM: tegra: Device tree " Thierry Reding
2019-02-15 14:51   ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 8/9] arm64: " Thierry Reding
2019-02-15 14:52   ` Arnd Bergmann
2019-02-08 15:09 ` [GIT PULL 9/9] arm64: tegra: Default configuration " Thierry Reding
2019-02-15 15:49   ` Arnd Bergmann

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=20190215214207.GA12838@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=talho@nvidia.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;
as well as URLs for NNTP newsgroup(s).