From: thor.thayer@linux.intel.com
To: bp@alien8.de, dinguyen@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: mchehab@kernel.org, james.morse@arm.com,
thor.thayer@linux.intel.com, devicetree@vger.kernel.org,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCHv3 0/3] Update Stratix10 EDAC Bindings
Date: Mon, 25 Mar 2019 10:57:53 -0500 [thread overview]
Message-ID: <1553529476-26181-1-git-send-email-thor.thayer@linux.intel.com> (raw)
From: Thor Thayer <thor.thayer@linux.intel.com>
This patch series makes the Stratix10 EDAC Bindings
specific to the Stratix10 ARM64 architecture.
Instead of using the Arria10 (ARM32) EDAC bindings for
Stratix10 (ARM64), create Stratix10 specific EDAC bindings
to capture architecture differences between ARM32 and ARM64.
This requires fixing the previous Stratix10 bindings.
Also add the peripheral bindings for the Stratix10.
V2: Remove Stratix10 compatible check.
V3: Remove patches not related to EDAC bindings so that
this patchset is targeted toward the bindings.
Improve the Stratix10 specific binding description by
adding in descriptions of ARM64 differences.
Thor Thayer (3):
Documentation: dt: edac: Fix Stratix10 IRQ bindings
Documentation: dt: edac: Add Stratix10 Peripheral bindings
arm64: dts: stratix10: Use new Stratix10 EDAC bindings
.../devicetree/bindings/edac/socfpga-eccmgr.txt | 135 +++++++++++++++++++--
arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 25 ++--
2 files changed, 138 insertions(+), 22 deletions(-)
--
2.7.4
next reply other threads:[~2019-03-25 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 15:57 thor.thayer [this message]
2019-03-25 15:57 ` [PATCHv3 1/3] Documentation: dt: edac: Fix Stratix10 IRQ bindings thor.thayer
2019-03-25 15:57 ` [PATCHv3 2/3] Documentation: dt: edac: Add Stratix10 Peripheral bindings thor.thayer
2019-03-28 18:32 ` Rob Herring
2019-03-25 15:57 ` [PATCHv3 3/3] arm64: dts: stratix10: Use new Stratix10 EDAC bindings thor.thayer
2019-03-29 18:03 ` Dinh Nguyen
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=1553529476-26181-1-git-send-email-thor.thayer@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox