From: Marc Zyngier <maz@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, mark.rutland@arm.com,
jason@lakedaemon.net, robh+dt@kernel.org, tglx@linutronix.de,
joel@jms.id.au, andrew@aj.id.au
Subject: Re: [PATCH v6 00/12] aspeed: Add SCU interrupt controller and XDMA engine drivers
Date: Mon, 20 Jan 2020 09:54:01 +0100 [thread overview]
Message-ID: <1c0315d197ae5b8b01ea5beaaf32fa21@kernel.org> (raw)
In-Reply-To: <1579123790-6894-1-git-send-email-eajames@linux.ibm.com>
On 2020-01-15 22:29, Eddie James wrote:
> This series first adds a driver to control the interrupt controller
> provided by
> the System Control Unit (SCU) on the AST2500 and AST2600 SOCs. The
> interrupts
> made available are necessary for the control of the XDMA engine
> embedded in the
> same Aspeed SOCs.
> This series then adds a driver to control the XDMA engine. This driver
> was
> previously sent to the list without support for the AST2600, and has
> been
> refactored significantly to enable that support. The XDMA engine
> performs
> automatic DMA operations between the Aspeed SOC (acting as a BMC) and a
> host
> processor.
>
> Changes since v5:
> - Rework the XDMA locking completely; thanks Andrew Jeffrey for the
> help.
>
> Changes since v4:
> - Fix dts documentation example for XDMA
> - Add errno in warning for SCU failure in XDMA PCIe config
> - Add a check for in_reset before proceeding in O_NONBLOCK case
> - Add comments to memory sizes in the witherspoon/tacoma XDMA dts
> entries
>
> Changes since v3:
> - See individual patches; just clean-up items
>
> Changes since v2:
> - See individual patches
> - Drop rainier dts patch
> - In summary, remove references to VGA memory as the XDMA driver
> doesn't care
> where it is. Remove SDRAM controller reference. Move user reset
> functionality to a separate patch and make it an ioctl.
>
> Changes since v1:
> - See individual patches
> - In summary, first the irqchip driver switched to use the parent SCU
> regmap
> rather than iomapping it's register. Secondly, the XDMA
> initialization
> switched to use properties from the device tree rather than
> dynamically
> calculate memory spaces, and system config.
>
> Eddie James (12):
> dt-bindings: interrupt-controller: Add Aspeed SCU interrupt
> controller
> irqchip: Add Aspeed SCU interrupt controller
I've now queued these two patches in the irqchip tree.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2020-01-20 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 21:29 [PATCH v6 00/12] aspeed: Add SCU interrupt controller and XDMA engine drivers Eddie James
2020-01-15 21:29 ` [PATCH v6 01/12] dt-bindings: interrupt-controller: Add Aspeed SCU interrupt controller Eddie James
2020-01-15 21:29 ` [PATCH v6 02/12] irqchip: " Eddie James
2020-01-15 21:29 ` [PATCH v6 03/12] ARM: dts: aspeed: ast2500: Add " Eddie James
2020-01-15 21:29 ` [PATCH v6 04/12] ARM: dts: aspeed: ast2600: Add SCU interrupt controllers Eddie James
2020-01-15 21:29 ` [PATCH v6 05/12] dt-bindings: soc: Add Aspeed XDMA Engine Eddie James
2020-01-17 0:01 ` Andrew Jeffery
2020-01-15 21:29 ` [PATCH v6 06/12] soc: aspeed: Add XDMA Engine Driver Eddie James
2020-01-17 0:07 ` Andrew Jeffery
2020-02-10 16:35 ` Arnd Bergmann
2020-02-10 17:10 ` Eddie James
2020-03-16 4:49 ` Joel Stanley
2020-02-16 23:56 ` Andrew Jeffery
2020-01-15 21:29 ` [PATCH v6 07/12] soc: aspeed: xdma: Add user interface Eddie James
2020-01-17 0:09 ` Andrew Jeffery
2020-01-15 21:29 ` [PATCH v6 08/12] soc: aspeed: xdma: Add reset ioctl Eddie James
2020-01-15 21:29 ` [PATCH v6 09/12] ARM: dts: aspeed: ast2500: Add XDMA Engine Eddie James
2020-01-15 21:29 ` [PATCH v6 10/12] ARM: dts: aspeed: ast2600: " Eddie James
2020-01-15 21:29 ` [PATCH v6 11/12] ARM: dts: aspeed: witherspoon: Enable " Eddie James
2020-01-17 0:12 ` Andrew Jeffery
2020-01-15 21:29 ` [PATCH v6 12/12] ARM: dts: aspeed: tacoma: Enable XDMA engine Eddie James
2020-01-17 0:13 ` Andrew Jeffery
2020-01-20 8:54 ` Marc Zyngier [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=1c0315d197ae5b8b01ea5beaaf32fa21@kernel.org \
--to=maz@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jason@lakedaemon.net \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).