All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-remoteproc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Suman Anna <s-anna@ti.com>,
	"Andrew F. Davis" <afd@ti.com>, Sam Nelson <sam.nelson@ti.com>
Subject: [PATCH 0/3] Add Keystone2 Remoteproc driver
Date: Fri, 26 May 2017 11:53:14 -0500	[thread overview]
Message-ID: <20170526165317.23164-1-s-anna@ti.com> (raw)

Hi,

This series adds the DT binding and the driver for loading and booting
the DSP devices present on various Keystone2 SoC families. The current
series supports the 66AK2H/K, 66AK2L and 66AK2E SoC families. Support
for the remaining 66AK2G SoC family will be added later as it is
awaiting the dependent clock and reset drivers to be merged into
mainline.

Supported features include basic load/boot using DSP internal memory
regions and error recovery. IPC based on the virtio-rpmsg transport
with vrings in external DDR memory and interrupts supported through
MMRs.

The DTS nodes will be posted separately once the binding is accepted.
The virtio-rpmsg based IPC stack would require some support in the
virtio_rpmsg driver (first 2 patches from Loic's "virtio_rpmsg: make
rpmsg channel configurable" series [1] to begin with) if using CMA
pools from HighMem area.

regards
Suman

[1] https://lkml.org/lkml/2017/3/28/349

Andrew F. Davis (1):
  remoteproc/keystone: ensure the DSPs are in reset in probe

Suman Anna (2):
  Documentation: DT: add Keystone DSP remoteproc binding
  remoteproc/keystone: add a remoteproc driver for Keystone 2 DSPs

 .../bindings/remoteproc/ti,keystone-rproc.txt      | 132 ++++++
 drivers/remoteproc/Kconfig                         |  13 +
 drivers/remoteproc/Makefile                        |   1 +
 drivers/remoteproc/keystone_remoteproc.c           | 525 +++++++++++++++++++++
 4 files changed, 671 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
 create mode 100644 drivers/remoteproc/keystone_remoteproc.c

-- 
2.12.0

WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	<linux-remoteproc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Suman Anna <s-anna@ti.com>, "Andrew F. Davis" <afd@ti.com>,
	Sam Nelson <sam.nelson@ti.com>
Subject: [PATCH 0/3] Add Keystone2 Remoteproc driver
Date: Fri, 26 May 2017 11:53:14 -0500	[thread overview]
Message-ID: <20170526165317.23164-1-s-anna@ti.com> (raw)

Hi,

This series adds the DT binding and the driver for loading and booting
the DSP devices present on various Keystone2 SoC families. The current
series supports the 66AK2H/K, 66AK2L and 66AK2E SoC families. Support
for the remaining 66AK2G SoC family will be added later as it is
awaiting the dependent clock and reset drivers to be merged into
mainline.

Supported features include basic load/boot using DSP internal memory
regions and error recovery. IPC based on the virtio-rpmsg transport
with vrings in external DDR memory and interrupts supported through
MMRs.

The DTS nodes will be posted separately once the binding is accepted.
The virtio-rpmsg based IPC stack would require some support in the
virtio_rpmsg driver (first 2 patches from Loic's "virtio_rpmsg: make
rpmsg channel configurable" series [1] to begin with) if using CMA
pools from HighMem area.

regards
Suman

[1] https://lkml.org/lkml/2017/3/28/349

Andrew F. Davis (1):
  remoteproc/keystone: ensure the DSPs are in reset in probe

Suman Anna (2):
  Documentation: DT: add Keystone DSP remoteproc binding
  remoteproc/keystone: add a remoteproc driver for Keystone 2 DSPs

 .../bindings/remoteproc/ti,keystone-rproc.txt      | 132 ++++++
 drivers/remoteproc/Kconfig                         |  13 +
 drivers/remoteproc/Makefile                        |   1 +
 drivers/remoteproc/keystone_remoteproc.c           | 525 +++++++++++++++++++++
 4 files changed, 671 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
 create mode 100644 drivers/remoteproc/keystone_remoteproc.c

-- 
2.12.0

WARNING: multiple messages have this Message-ID (diff)
From: s-anna@ti.com (Suman Anna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add Keystone2 Remoteproc driver
Date: Fri, 26 May 2017 11:53:14 -0500	[thread overview]
Message-ID: <20170526165317.23164-1-s-anna@ti.com> (raw)

Hi,

This series adds the DT binding and the driver for loading and booting
the DSP devices present on various Keystone2 SoC families. The current
series supports the 66AK2H/K, 66AK2L and 66AK2E SoC families. Support
for the remaining 66AK2G SoC family will be added later as it is
awaiting the dependent clock and reset drivers to be merged into
mainline.

Supported features include basic load/boot using DSP internal memory
regions and error recovery. IPC based on the virtio-rpmsg transport
with vrings in external DDR memory and interrupts supported through
MMRs.

The DTS nodes will be posted separately once the binding is accepted.
The virtio-rpmsg based IPC stack would require some support in the
virtio_rpmsg driver (first 2 patches from Loic's "virtio_rpmsg: make
rpmsg channel configurable" series [1] to begin with) if using CMA
pools from HighMem area.

regards
Suman

[1] https://lkml.org/lkml/2017/3/28/349

Andrew F. Davis (1):
  remoteproc/keystone: ensure the DSPs are in reset in probe

Suman Anna (2):
  Documentation: DT: add Keystone DSP remoteproc binding
  remoteproc/keystone: add a remoteproc driver for Keystone 2 DSPs

 .../bindings/remoteproc/ti,keystone-rproc.txt      | 132 ++++++
 drivers/remoteproc/Kconfig                         |  13 +
 drivers/remoteproc/Makefile                        |   1 +
 drivers/remoteproc/keystone_remoteproc.c           | 525 +++++++++++++++++++++
 4 files changed, 671 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
 create mode 100644 drivers/remoteproc/keystone_remoteproc.c

-- 
2.12.0

             reply	other threads:[~2017-05-26 16:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 16:53 Suman Anna [this message]
2017-05-26 16:53 ` [PATCH 0/3] Add Keystone2 Remoteproc driver Suman Anna
2017-05-26 16:53 ` Suman Anna
2017-05-26 16:53 ` [PATCH 1/3] Documentation: DT: add Keystone DSP remoteproc binding Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-31 19:12   ` Rob Herring
2017-05-31 19:12     ` Rob Herring
2017-05-31 20:05     ` Suman Anna
2017-05-31 20:05       ` Suman Anna
2017-05-31 20:05       ` Suman Anna
2017-05-31 20:05       ` Suman Anna
2017-06-05 17:26       ` Rob Herring
2017-06-05 17:26         ` Rob Herring
2017-06-05 18:21         ` Suman Anna
2017-06-05 18:21           ` Suman Anna
2017-06-05 18:21           ` Suman Anna
2017-06-05 18:21           ` Suman Anna
2017-06-05 19:10           ` Rob Herring
2017-06-05 19:10             ` Rob Herring
2017-06-05 19:10             ` Rob Herring
2017-06-05 19:10             ` Rob Herring
2017-06-05 20:05             ` Suman Anna
2017-06-05 20:05               ` Suman Anna
2017-06-05 20:05               ` Suman Anna
2017-06-05 20:05               ` Suman Anna
2017-05-26 16:53 ` [PATCH 2/3] remoteproc/keystone: add a remoteproc driver for Keystone 2 DSPs Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53 ` [PATCH 3/3] remoteproc/keystone: ensure the DSPs are in reset in probe Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna
2017-05-26 16:53   ` Suman Anna

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=20170526165317.23164-1-s-anna@ti.com \
    --to=s-anna@ti.com \
    --cc=afd@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    --cc=sam.nelson@ti.com \
    --cc=ssantosh@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.