All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 0/6] memory: tegra: Miscellaneous Tegra124 improvements
Date: Sun, 22 Dec 2019 12:39:15 +0100	[thread overview]
Message-ID: <20191222113921.1469372-1-thierry.reding@gmail.com> (raw)

From: Thierry Reding <treding@nvidia.com>

Hi,

this set of changes improves the EMC bindings on Tegra124 and Tegra132.
The goal is to bring them up to par with the bindings on Tegra20 and
Tegra30 and future bindings that will be introduced for Tegra210 and
later.

Note that there's a tiny bit of ABI break here in that new device trees
will cause existing debugfs support from working. Since the EMC driver
doesn't do anything other than provide a backend for the debugfs
interface, I think that's something that we can live with.

A new debugfs interface is introduced in this series and it replaces the
existing one, which turns out to be too limited looking forward to plans
to make the EMC act as an interconnect provider.

Thierry

Thierry Reding (6):
  dt-bindings: memory-controller: Convert Tegra124 EMC to json-schema
  memory: tegra: Refashion EMC debugfs interface on Tegra124
  ARM: tegra: Let the EMC hardware use the EMC clock
  arm64: tegra: Let the EMC hardware use the EMC clock
  ARM: tegra: Rename EMC on Tegra124
  arm64: tegra: Rename EMC on Tegra132

 .../nvidia,tegra124-emc.txt                   | 374 -------------
 .../nvidia,tegra124-emc.yaml                  | 528 ++++++++++++++++++
 arch/arm/boot/dts/tegra124-apalis-emc.dtsi    |   2 +-
 .../arm/boot/dts/tegra124-jetson-tk1-emc.dtsi |   2 +-
 arch/arm/boot/dts/tegra124-nyan-big-emc.dtsi  |   2 +-
 .../arm/boot/dts/tegra124-nyan-blaze-emc.dtsi |   2 +-
 arch/arm/boot/dts/tegra124.dtsi               |   4 +-
 arch/arm64/boot/dts/nvidia/tegra132.dtsi      |   4 +-
 drivers/memory/tegra/tegra124-emc.c           | 185 ++++--
 9 files changed, 681 insertions(+), 422 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.txt
 create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml

-- 
2.24.1


             reply	other threads:[~2019-12-22 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22 11:39 Thierry Reding [this message]
2019-12-22 11:39 ` [PATCH 1/6] dt-bindings: memory-controller: Convert Tegra124 EMC to json-schema Thierry Reding
2020-01-08 15:35   ` Rob Herring
     [not found]   ` <20191222113921.1469372-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-13 18:03     ` Rob Herring
2020-01-13 18:03       ` Rob Herring
2019-12-22 11:39 ` [PATCH 2/6] memory: tegra: Refashion EMC debugfs interface on Tegra124 Thierry Reding
2019-12-22 11:39 ` [PATCH 3/6] ARM: tegra: Let the EMC hardware use the EMC clock Thierry Reding
2019-12-22 11:39 ` [PATCH 4/6] arm64: " Thierry Reding
2019-12-22 11:39 ` [PATCH 5/6] ARM: tegra: Rename EMC on Tegra124 Thierry Reding
2019-12-22 11:39 ` [PATCH 6/6] arm64: tegra: Rename EMC on Tegra132 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=20191222113921.1469372-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.