devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Devicetree List <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"Lendacky, Thomas" <thomas.lendacky@amd.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	brijeshkumar.singh@amd.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/6] dt: amd-seattle: update SMMU and PCIe descriptions
Date: Tue, 26 Nov 2019 09:46:01 +0100	[thread overview]
Message-ID: <CAKv+Gu-h5X4bamP=Fy2kEpeqTtUNz=TU3AUpGtHY5caBpdVxeA@mail.gmail.com> (raw)
In-Reply-To: <20191125225110.10924-1-ardb@kernel.org>

On Mon, 25 Nov 2019 at 23:51, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> Bring the DT descriptions for AMD Seattle up to date:
> - upgrade the existing SMMU descriptions to the new binding, and add the
>   missing descriptions of the PCIe and SATA SMMUs
> - fix the description of the PCIe legacy interrupt routing
> - remove the obsolete A0 Overdrive and Husky
>
> Ard Biesheuvel (6):
>   dt: amd-seattle: remove Husky platform
>   dt: amd-seattle: remove Overdrive revision A0 support
>   dt: amd-seattle: upgrade AMD Seattle XGBE to new SMMU binding
>   dt: amd-seattle: fix PCIe legacy interrupt routing
>   dt: amd-seattle: add a description of the PCIe SMMU
>   dt: amd-seattle: add description of the SATA/CCP SMMUs
>

I'll need to respin this - please disregard for now.

>  arch/arm64/boot/dts/amd/Makefile              |  4 +-
>  .../boot/dts/amd/amd-overdrive-rev-b0.dts     |  4 +
>  .../boot/dts/amd/amd-overdrive-rev-b1.dts     |  5 ++
>  arch/arm64/boot/dts/amd/amd-overdrive.dts     | 66 ---------------
>  arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi  | 53 ++++++++++--
>  .../boot/dts/amd/amd-seattle-xgbe-b.dtsi      | 16 +---
>  arch/arm64/boot/dts/amd/husky.dts             | 84 -------------------
>  7 files changed, 61 insertions(+), 171 deletions(-)
>  delete mode 100644 arch/arm64/boot/dts/amd/amd-overdrive.dts
>  delete mode 100644 arch/arm64/boot/dts/amd/husky.dts
>
> --
> 2.17.1
>

      parent reply	other threads:[~2019-11-26  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 22:51 [PATCH 0/6] dt: amd-seattle: update SMMU and PCIe descriptions Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 1/6] dt: amd-seattle: remove Husky platform Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 2/6] dt: amd-seattle: remove Overdrive revision A0 support Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 3/6] dt: amd-seattle: upgrade AMD Seattle XGBE to new SMMU binding Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 4/6] dt: amd-seattle: fix PCIe legacy interrupt routing Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 5/6] dt: amd-seattle: add a description of the PCIe SMMU Ard Biesheuvel
2019-11-25 22:51 ` [PATCH 6/6] dt: amd-seattle: add description of the SATA/CCP SMMUs Ard Biesheuvel
2019-11-26  8:46 ` Ard Biesheuvel [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='CAKv+Gu-h5X4bamP=Fy2kEpeqTtUNz=TU3AUpGtHY5caBpdVxeA@mail.gmail.com' \
    --to=ard.biesheuvel@linaro.org \
    --cc=ardb@kernel.org \
    --cc=brijeshkumar.singh@amd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=will@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).