From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/7] soc/tegra: Changes for v4.17-rc1
Date: Mon, 19 Mar 2018 09:42:02 +0100 [thread overview]
Message-ID: <20180319084202.GA24307@ulmo> (raw)
In-Reply-To: <20180316141850.4876-4-thierry.reding@gmail.com>
On Fri, Mar 16, 2018 at 03:18:47PM +0100, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.17-soc
>
> for you to fetch changes up to 0cad0983bd3c002e92dff1e9d7f28c2c312c1973:
>
> soc/tegra: pmc: Use the new reset APIs to manage reset controllers (2018-03-09 08:51:07 +0100)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> soc/tegra: Changes for v4.17-rc1
>
> This contains more Tegra194 support as well as an implementation for the
> MBIST workaround needed to avoid some memory-related issues on Tegra210.
>
> ----------------------------------------------------------------
> Mikko Perttunen (2):
> soc/tegra: Add Tegra194 SoC configuration option
> soc/tegra: pmc: Add Tegra194 compatibility string
>
> Peter De Schrijver (1):
> soc/tegra: pmc: MBIST work around for Tegra210
>
> Thierry Reding (1):
> soc/tegra: pmc: Pass PMC to tegra_powergate_power_up()
>
> Vivek Gautam (1):
> soc/tegra: pmc: Use the new reset APIs to manage reset controllers
I'd like to update this pull request with this final patch fixed up. I
had to apply it manually and it looks like I messed it up. This has one
hunk missing that causes a failure to boot on Jetson TX1, but only if
neither DSI nor HDMI are enabled (DSI explicitly disabled in DT, and
HDMI not connected). I only stumbled on this because I was testing some
unrelated display code paths.
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/20180319/0a01a84b/attachment.sig>
next prev parent reply other threads:[~2018-03-19 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:18 [GIT PULL 1/7] ARM: tegra: Miscellaneous changes for v4.17-rc1 Thierry Reding
2018-03-16 14:18 ` [GIT PULL 2/7] dt-bindings: Changes " Thierry Reding
2018-03-27 11:19 ` Arnd Bergmann
2018-03-16 14:18 ` [GIT PULL 3/7] firmware: " Thierry Reding
2018-03-27 13:51 ` Arnd Bergmann
2018-03-16 14:18 ` [GIT PULL 4/7] soc/tegra: " Thierry Reding
2018-03-19 8:42 ` Thierry Reding [this message]
2018-03-19 8:52 ` [GIT PULL v2 " Thierry Reding
2018-03-27 13:52 ` Arnd Bergmann
2018-03-16 14:18 ` [GIT PULL 5/7] ARM: tegra: Device tree changes " Thierry Reding
2018-03-16 14:18 ` [GIT PULL 6/7] arm64: Default configuration updates " Thierry Reding
2018-03-27 13:12 ` Arnd Bergmann
2018-03-16 14:18 ` [GIT PULL 7/7] arm64: tegra: Device tree changes " Thierry Reding
2018-03-27 11:27 ` Arnd Bergmann
2018-03-27 11:10 ` [GIT PULL 1/7] ARM: tegra: Miscellaneous " 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=20180319084202.GA24307@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).