linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 9/9] arm64: tegra: Default configuration changes for v5.1-rc1
Date: Fri,  8 Feb 2019 16:09:35 +0100	[thread overview]
Message-ID: <20190208150935.32108-10-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190208150935.32108-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:

  Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.1-arm64-defconfig

for you to fetch changes up to bc72bed682a9502f5c8f5adf15107aef6237895e:

  arm64: defconfig: Enable Tegra TCU (2019-02-06 14:38:35 +0100)

Thanks,
Thierry

----------------------------------------------------------------
arm64: tegra: Default configuration changes for v5.1-rc1

Enables the TCU driver to be built into the kernel, so that the TCU can
be used as debug serial on Jetson Xavier. This also enables the MAX8973
regulator driver that is required for CPU frequency scaling on Tegra210.

----------------------------------------------------------------
Joseph Lo (1):
      arm64: defconfig: Enable MAX8973 regulator

Thierry Reding (1):
      arm64: defconfig: Enable Tegra TCU

 arch/arm64/configs/defconfig | 2 ++
 1 file changed, 2 insertions(+)

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

  parent reply	other threads:[~2019-02-08 15:11 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
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 ` Thierry Reding [this message]
2019-02-15 15:49   ` [GIT PULL 9/9] arm64: tegra: Default configuration " 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=20190208150935.32108-10-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.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).