Hi Nikolaus,
On 06/23/2017 10:22 AM, H. Nikolaus Schaller wrote:
> Hi,
>
>> Am 23.06.2017 um 16:57 schrieb Andreas Färber :
>>
>> Am 23.06.2017 um 16:53 schrieb H. Nikolaus Schaller:
>>> Hi Laurent,
>>>
Am 23.06.2017 um 13:58 schrieb Laurent Pinchart
:
Hi Nikolaus,
Hi Oleksij,
On 06/19/2017 02:43 AM, Oleksij Rempel wrote:
> Hi,
>
> Thank you for your review!
>
> On 15.06.2017 21:01, Suman Anna wrote:
>> Hi Oleksij,
>>
>> On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
>>> From: Oleksij Rempel <li...@rempel-pri
Hi Oleksij,
On 06/19/2017 02:43 AM, Oleksij Rempel wrote:
> Hi,
>
> Thank you for your review!
>
> On 15.06.2017 21:01, Suman Anna wrote:
>> Hi Oleksij,
>>
>> On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
>>> From: Oleksij Rempel
>>>
>
Hi Sarang,
> Thanks for reviewing the patch.> >>
>> On 06/14/2017 01:06 PM, Sarangdhar Joshi wrote:
>>> The remoteproc framework shuts down and immediately restarts the
>>> remote processor after fatal events (such as when remote crashes)
>>> during the recovery path.
>>
>> This is the case in
Hi Sarang,
> Thanks for reviewing the patch.> >>
>> On 06/14/2017 01:06 PM, Sarangdhar Joshi wrote:
>>> The remoteproc framework shuts down and immediately restarts the
>>> remote processor after fatal events (such as when remote crashes)
>>> during the recovery path.
>>
>> This is the case in
On 06/15/2017 02:01 PM, Suman Anna wrote:
> Hi Oleksij,
>
> On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
>> From: Oleksij Rempel <li...@rempel-privat.de>
>>
>> this driver was tested on NXP imx7d but should work on
>> imx6sx as well.
>> It will
On 06/15/2017 02:01 PM, Suman Anna wrote:
> Hi Oleksij,
>
> On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
>> From: Oleksij Rempel
>>
>> this driver was tested on NXP imx7d but should work on
>> imx6sx as well.
>> It will upload firmware to OCRAM, w
Hi Oleksij,
On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
From: Oleksij Rempel
this driver was tested on NXP imx7d but should work on
imx6sx as well.
It will upload firmware to OCRAM, which shared memory between
Cortex A7 and Cortex M4, then turn M4 on.
Mostly looks
Hi Oleksij,
On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
From: Oleksij Rempel
this driver was tested on NXP imx7d but should work on
imx6sx as well.
It will upload firmware to OCRAM, which shared memory between
Cortex A7 and Cortex M4, then turn M4 on.
Mostly looks fine, need to address
Hi Sarangdhar,
On 06/14/2017 01:06 PM, Sarangdhar Joshi wrote:
The remoteproc framework shuts down and immediately restarts the
remote processor after fatal events (such as when remote crashes)
during the recovery path.
This is the case in production systems, but your statement is not
Hi Sarangdhar,
On 06/14/2017 01:06 PM, Sarangdhar Joshi wrote:
The remoteproc framework shuts down and immediately restarts the
remote processor after fatal events (such as when remote crashes)
during the recovery path.
This is the case in production systems, but your statement is not
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna <s-a...@ti.com>
Signed-off-by: Sam Nelson <sam.nel...@ti.com>
Acked-by: Rob Herring <r...@kernel.org>
Acked-by: Santosh Shilimkar <ssant...@kernel.o
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna
Signed-off-by: Sam Nelson
Acked-by: Rob Herring
Acked-by: Santosh Shilimkar
---
v3:
- Picked up the Acks from Rob and Santosh, and addressed
the one minor comment
row a eye-catchy warning and assert the
resets specifically.
Signed-off-by: Andrew F. Davis <a...@ti.com>
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna <s-a...@ti.com>
Acked-by: Santosh Shilimkar <ssant...@kernel.org>
---
v3: No code changes,
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna <
and assert the
resets specifically.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna
Acked-by: Santosh Shilimkar
---
v3: No code changes, picked up Santosh's Ack
v2: https://patchwork.kernel.org/patch/9773679/
drivers/remoteproc/keystone_re
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna
Signed-o
://marc.info/?t=14958180254=1=2
regards
Suman
Andrew F. Davis (1):
remoteproc/keystone: Ensure the DSPs are in reset in probe
Suman Anna (2):
dt-bindings: remoteproc: Add Keystone DSP remoteproc binding
remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs
.../bindings
://marc.info/?t=14958180254=1=2
regards
Suman
Andrew F. Davis (1):
remoteproc/keystone: Ensure the DSPs are in reset in probe
Suman Anna (2):
dt-bindings: remoteproc: Add Keystone DSP remoteproc binding
remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs
.../bindings
Bjorn,
On 05/18/2017 05:08 PM, Suman Anna wrote:
> Hi Bjorn,
>
> The following series includes various fixes and cleanups for the TI's
> Davinci DSP remoteproc driver. Patches are based on 4.12-rc1. Following
> is the patch summary:
>
> - Patch1 updates/fixes the build
Bjorn,
On 05/18/2017 05:08 PM, Suman Anna wrote:
> Hi Bjorn,
>
> The following series includes various fixes and cleanups for the TI's
> Davinci DSP remoteproc driver. Patches are based on 4.12-rc1. Following
> is the patch summary:
>
> - Patch1 updates/fixes the build
row a eye-catchy warning and assert the
resets specifically.
Signed-off-by: Andrew F. Davis <a...@ti.com>
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna <s-a...@ti.com>
---
v2: No code changes
drivers/remoteproc/keystone_remoteproc.c | 10 ++
1 file changed,
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna <s-a...@ti.com>
Signed-off-by: Sam Nelson <sam.nel...@ti.com>
---
v2 Changes:
- Modified the patch title
- Dropped unstable binding status
- Droppe
and assert the
resets specifically.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna
---
v2: No code changes
drivers/remoteproc/keystone_remoteproc.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna
Signed-off-by: Sam Nelson
---
v2 Changes:
- Modified the patch title
- Dropped unstable binding status
- Dropped the 'label' property and replaced the device node
/?t=14958180254=1=2
regards
Suman
Andrew F. Davis (1):
remoteproc/keystone: Ensure the DSPs are in reset in probe
Suman Anna (2):
dt-bindings: remoteproc: Add Keystone DSP remoteproc binding
remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs
.../bindings/remoteproc/ti
/?t=14958180254=1=2
regards
Suman
Andrew F. Davis (1):
remoteproc/keystone: Ensure the DSPs are in reset in probe
Suman Anna (2):
dt-bindings: remoteproc: Add Keystone DSP remoteproc binding
remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs
.../bindings/remoteproc/ti
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna <
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna
Signed-o
Hi Rob,
On 06/05/2017 02:10 PM, Rob Herring wrote:
> On Mon, Jun 5, 2017 at 1:21 PM, Suman Anna <s-a...@ti.com> wrote:
>> Hi Rob,
>>
>>>>
>>>> On 05/31/2017 02:12 PM, Rob Herring wrote:
>>>>> On Fri, May 26, 2017 at 11:53:15AM -0500, Su
Hi Rob,
On 06/05/2017 02:10 PM, Rob Herring wrote:
> On Mon, Jun 5, 2017 at 1:21 PM, Suman Anna wrote:
>> Hi Rob,
>>
>>>>
>>>> On 05/31/2017 02:12 PM, Rob Herring wrote:
>>>>> On Fri, May 26, 2017 at 11:53:15AM -0500, Suman Anna wrote:
>
Hi Rob,
>>
>> On 05/31/2017 02:12 PM, Rob Herring wrote:
>>> On Fri, May 26, 2017 at 11:53:15AM -0500, Suman Anna wrote:
>>>> Add the device tree bindings document for the Texas Instrument's
>>>> Keystone 2 DSP remoteproc devices.
>>>>
&
Hi Rob,
>>
>> On 05/31/2017 02:12 PM, Rob Herring wrote:
>>> On Fri, May 26, 2017 at 11:53:15AM -0500, Suman Anna wrote:
>>>> Add the device tree bindings document for the Texas Instrument's
>>>> Keystone 2 DSP remoteproc devices.
>>>>
Hi Bjorn,
On 06/02/2017 05:07 AM, Henri Roosen wrote:
>> The rpmsg devices are allocated in the backends and as such must be
>> freed there as well.
>>
>> Signed-off-by: Bjorn Andersson
>> ---
>> drivers/rpmsg/qcom_smd.c | 11 +++
>>
Hi Bjorn,
On 06/02/2017 05:07 AM, Henri Roosen wrote:
>> The rpmsg devices are allocated in the backends and as such must be
>> freed there as well.
>>
>> Signed-off-by: Bjorn Andersson
>> ---
>> drivers/rpmsg/qcom_smd.c | 11 +++
>> drivers/rpmsg/virtio_rpmsg_bus.c | 9
Hi Henri,
On 06/02/2017 06:35 AM, Henri Roosen wrote:
> A device might not have an ops structure registered. This
The rpmsg devices are registered from the respective backends, which are
supposed to plug in their ops. What is the scenario where you think
these ops might not be populated? We
Hi Henri,
On 06/02/2017 06:35 AM, Henri Roosen wrote:
> A device might not have an ops structure registered. This
The rpmsg devices are registered from the respective backends, which are
supposed to plug in their ops. What is the scenario where you think
these ops might not be populated? We
On 06/02/2017 06:36 AM, Henri Roosen wrote:
> Trivial cleanup: the .ops pointer is assigned twice. This patch removes the
> first assignment.
>
> Signed-off-by: Henri Roosen <henri.roo...@ginzinger.com>
Acked-by: Suman Anna <s-a...@ti.com>
> ---
> drivers/rpmsg/v
On 06/02/2017 06:36 AM, Henri Roosen wrote:
> Trivial cleanup: the .ops pointer is assigned twice. This patch removes the
> first assignment.
>
> Signed-off-by: Henri Roosen
Acked-by: Suman Anna
> ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 3 ---
> 1 file changed, 3 d
Hi Philipp,
On 05/24/2017 01:09 PM, Suman Anna wrote:
> Hi Philipp,
>
> This series adds a reset controller driver that uses the TI SCI protocol
> to manage resets on some TI SoCs. It is a repost of the previous v4 [1]
> submission that has already been acked by Rob and Santosh
Hi Philipp,
On 05/24/2017 01:09 PM, Suman Anna wrote:
> Hi Philipp,
>
> This series adds a reset controller driver that uses the TI SCI protocol
> to manage resets on some TI SoCs. It is a repost of the previous v4 [1]
> submission that has already been acked by Rob and Santosh
Hi Rob,
On 05/31/2017 02:12 PM, Rob Herring wrote:
> On Fri, May 26, 2017 at 11:53:15AM -0500, Suman Anna wrote:
>> Add the device tree bindings document for the Texas Instrument's
>> Keystone 2 DSP remoteproc devices.
>>
>> Signed-off-by: Suman Anna <s-a...@ti.com
Hi Rob,
On 05/31/2017 02:12 PM, Rob Herring wrote:
> On Fri, May 26, 2017 at 11:53:15AM -0500, Suman Anna wrote:
>> Add the device tree bindings document for the Texas Instrument's
>> Keystone 2 DSP remoteproc devices.
>>
>> Signed-off-by: Suman Anna
&
Hi Rob,
On 05/31/2017 02:22 PM, Rob Herring wrote:
> On Fri, May 26, 2017 at 03:21:39PM -0500, Suman Anna wrote:
>> Add the device tree bindings document for the DSP processor
>> subsystem devices on TI Davinci DA8xx/OMAP-L13x SoCs.
>
> "dt-bindings: remoteproc:
Hi Rob,
On 05/31/2017 02:22 PM, Rob Herring wrote:
> On Fri, May 26, 2017 at 03:21:39PM -0500, Suman Anna wrote:
>> Add the device tree bindings document for the DSP processor
>> subsystem devices on TI Davinci DA8xx/OMAP-L13x SoCs.
>
> "dt-bindings: remoteproc:
12869=2
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git/?h=v4.13/soc
Suman Anna (4):
remoteproc/davinci: Switch to platform_get_resource_byname()
remoteproc/davinci: add support to parse internal memories
Documentation: dt: Add bindings for Davinci DSP
12869=2
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git/?h=v4.13/soc
Suman Anna (4):
remoteproc/davinci: Switch to platform_get_resource_byname()
remoteproc/davinci: add support to parse internal memories
Documentation: dt: Add bindings for Davinci DSP
SoCs.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/da8xx_remoteproc.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/remoteproc/da8xx_remoteproc.c
b/drivers/remoteproc/da8xx_remoteproc.c
index 5250cc494775..02a492
SoCs.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/remoteproc/da8xx_remoteproc.c
b/drivers/remoteproc/da8xx_remoteproc.c
index 5250cc494775..02a4920d1af2 100644
Add the device tree bindings document for the DSP processor
subsystem devices on TI Davinci DA8xx/OMAP-L13x SoCs.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
.../bindings/remoteproc/ti,davinci-rproc.txt | 92 ++
1 file changed, 92 insertions(+)
create mode
.
These mappings can then be used to support direct loading of
text/data into these memories from the remoteproc driver.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/da8xx_remoteproc.c | 62 +++
1 file changed, 62 insertions(+)
diff --git a/d
Add the device tree bindings document for the DSP processor
subsystem devices on TI Davinci DA8xx/OMAP-L13x SoCs.
Signed-off-by: Suman Anna
---
.../bindings/remoteproc/ti,davinci-rproc.txt | 92 ++
1 file changed, 92 insertions(+)
create mode 100644
Documentation
.
These mappings can then be used to support direct loading of
text/data into these memories from the remoteproc driver.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 62 +++
1 file changed, 62 insertions(+)
diff --git a/drivers/remoteproc
.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/da8xx_remoteproc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/remoteproc/da8xx_remoteproc.c
b/drivers/remoteproc/da8xx_remoteproc.c
index c7ad818f7a48..0919176b52c1 100644
--- a/drivers/remo
.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/remoteproc/da8xx_remoteproc.c
b/drivers/remoteproc/da8xx_remoteproc.c
index c7ad818f7a48..0919176b52c1 100644
--- a/drivers/remoteproc
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna <
l memories at the moment. This
remoteproc driver is also designed to work with virtio, and uses the
IPC Generation registers for performing the virtio signalling and
getting notified of exceptions.
The driver currently supports the 66AK2H/66AK2K, 66AK2L and 66AK2E
SoCs.
Signed-off-by: Suman Anna
Signed-o
[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
[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
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna <s-a...@ti.com>
Signed-off-by: Sam Nelson <sam.nel...@ti.com>
---
.../bindings/remoteproc/ti,keystone-rproc.txt | 132 +
1 file
Add the device tree bindings document for the Texas Instrument's
Keystone 2 DSP remoteproc devices.
Signed-off-by: Suman Anna
Signed-off-by: Sam Nelson
---
.../bindings/remoteproc/ti,keystone-rproc.txt | 132 +
1 file changed, 132 insertions(+)
create mode 100644
row a eye-catchy warning and assert the
resets specifically.
Signed-off-by: Andrew F. Davis <a...@ti.com>
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/keystone_remoteproc.c | 10 ++
1 file changed, 10 insertions(+)
dif
and assert the
resets specifically.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com: replace warning with a WARN]
Signed-off-by: Suman Anna
---
drivers/remoteproc/keystone_remoteproc.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/remoteproc/keystone_remoteproc.c
llardy <loic.palla...@st.com>
Acked-by: Suman Anna <s-a...@ti.com>
regards
Suman
On 03/28/2017 06:49 AM, Loic Pallardy wrote:
> Rpmsg buffer size is currently fixed to 512 bytes.
> This patch introduces a new capability in struct virtproc_info
> to tune shared buffer size between host and coprocessor
> according to the needs.
>
> Signed-off-by: Loic Pallardy
various devices present on the SoC. Various reset functionalities
are achieved by the means of different TI SCI device operations
provided by the TI SCI framework.
Signed-off-by: Andrew F. Davis <a...@ti.com>
[s-a...@ti.com: documentation changes, revised commit message]
Signed-off-by: Sum
es present on the SoC. Various reset functionalities
are achieved by the means of different TI SCI device operations
provided by the TI SCI framework.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com: documentation changes, revised commit message]
Signed-off-by: Suman Anna
Signed-off-by: Nishanth Me
TI SCI) protocol to communicate to a system controller
block present on the SoC.
Signed-off-by: Andrew F. Davis <a...@ti.com>
[s-a...@ti.com: revise the binding format]
Signed-off-by: Suman Anna <s-a...@ti.com>
Signed-off-by: Nishanth Menon <n...@ti.com>
Acked-by: Santosh Shilimkar <ssant
Hi Philipp,
This series adds a reset controller driver that uses the TI SCI protocol
to manage resets on some TI SoCs. It is a repost of the previous v4 [1]
submission that has already been acked by Rob and Santosh, but with some
minor changes. This series has been waiting for the
ommunicate to a system controller
block present on the SoC.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com: revise the binding format]
Signed-off-by: Suman Anna
Signed-off-by: Nishanth Menon
Acked-by: Santosh Shilimkar
Acked-by: Rob Herring
---
Changes in v5:
- Dropped the include/dt-bindings/reset/
Hi Philipp,
This series adds a reset controller driver that uses the TI SCI protocol
to manage resets on some TI SoCs. It is a repost of the previous v4 [1]
submission that has already been acked by Rob and Santosh, but with some
minor changes. This series has been waiting for the
Rename the current Kconfig name used for the TI SYSCON Reset
driver from TI_SYSCON_RESET to RESET_TI_SYSCON to match the
convention used for all the reset drivers present at the
base reset folder.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/reset/Kconfig | 2 +-
drivers/reset/Ma
Rename the current Kconfig name used for the TI SYSCON Reset
driver from TI_SYSCON_RESET to RESET_TI_SYSCON to match the
convention used for all the reset drivers present at the
base reset folder.
Signed-off-by: Suman Anna
---
drivers/reset/Kconfig | 2 +-
drivers/reset/Makefile | 2 +-
2
will be invoked
during the remove due to the enabled 'auto-boot' support. The probe
already has support for asserting the reset in case the DSP is not
in reset for some reason.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/da8xx_remoteproc.c | 11 +--
1 file chan
and is not essential. Streamline the interrupt request
and freeing operations instead alongside the boot and shutdown of
the remote processor.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remoteproc/da8xx_remoteproc.c | 28 +++-
1 file changed, 11 insertions(+), 17 del
will be invoked
during the remove due to the enabled 'auto-boot' support. The probe
already has support for asserting the reset in case the DSP is not
in reset for some reason.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 11 +--
1 file changed, 1 insertion(+), 10
and is not essential. Streamline the interrupt request
and freeing operations instead alongside the boot and shutdown of
the remote processor.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 28 +++-
1 file changed, 11 insertions(+), 17 deletions(-)
diff --git
.
- Patch 3 fixes a DSP boot/functionality issue with repeated 'start'
and 'stop' commands using the sysfs 'state' variable.
- Patch 2 and 4 are cleanups/code simplifications.
regards
Suman
Suman Anna (4):
remoteproc/davinci: Update Kconfig to depend on DMA_CMA
remoteproc/davinci: simplify
() cycle to
acquire the clock handle to use with this function. This is
totally unnecessary and the code can be simplified to use
the clock acquired during probe and directly use the reset
functions, so simplify this logic.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/remo
this to a saner depends on dependency
convention. The dependency is also updated to use the DMA_CMA kconfig
symbol that is used for CMA allocations using the DMA API, the CMA
dependency is inherited implicitly.
Cc: Arnd Bergmann <a...@arndb.de>
Signed-off-by: Suman Anna <s-a...@ti.com>
.
- Patch 3 fixes a DSP boot/functionality issue with repeated 'start'
and 'stop' commands using the sysfs 'state' variable.
- Patch 2 and 4 are cleanups/code simplifications.
regards
Suman
Suman Anna (4):
remoteproc/davinci: Update Kconfig to depend on DMA_CMA
remoteproc/davinci: simplify
() cycle to
acquire the clock handle to use with this function. This is
totally unnecessary and the code can be simplified to use
the clock acquired during probe and directly use the reset
functions, so simplify this logic.
Signed-off-by: Suman Anna
---
drivers/remoteproc/da8xx_remoteproc.c | 23
this to a saner depends on dependency
convention. The dependency is also updated to use the DMA_CMA kconfig
symbol that is used for CMA allocations using the DMA API, the CMA
dependency is inherited implicitly.
Cc: Arnd Bergmann
Signed-off-by: Suman Anna
---
drivers/remoteproc/Kconfig | 2 +-
1
Hi Sekhar,
On 05/18/2017 01:10 AM, Sekhar Nori wrote:
> On Wednesday 17 May 2017 03:43 AM, Suman Anna wrote:
>> The DSP device on Davinci platforms does not have an MMU and requires
>> specific DDR memory to boot. This memory is reserved using the rproc_mem
>>
Hi Sekhar,
On 05/18/2017 01:10 AM, Sekhar Nori wrote:
> On Wednesday 17 May 2017 03:43 AM, Suman Anna wrote:
>> The DSP device on Davinci platforms does not have an MMU and requires
>> specific DDR memory to boot. This memory is reserved using the rproc_mem
>>
Add names to the IOMEM resources for the DSP device present on
DA8xx SoCs. This will facilitate the driver to use the names and
be agnostic of the resource order, and facilitate scalable DT
support in follow-up patches.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
arch/arm/mach-davinci/d
based on memory supplied to the remoteproc device, and adds resource
names and additional resources for publishing the DSP internal memory
regions to the davinci remoteproc driver.
Patches tested on OMAP-L138 LCDK board by booting it in legacy-mode.
regards
Suman
Suman Anna (3):
ARM: davinci
Add names to the IOMEM resources for the DSP device present on
DA8xx SoCs. This will facilitate the driver to use the names and
be agnostic of the resource order, and facilitate scalable DT
support in follow-up patches.
Signed-off-by: Suman Anna
---
arch/arm/mach-davinci/devices-da8xx.c | 2
based on memory supplied to the remoteproc device, and adds resource
names and additional resources for publishing the DSP internal memory
regions to the davinci remoteproc driver.
Patches tested on OMAP-L138 LCDK board by booting it in legacy-mode.
regards
Suman
Suman Anna (3):
ARM: davinci
if this memory is not assigned to the device, but the DSP
remote processor boot will not be successful in such cases. So, check
that memory has been reserved and assigned to the device specifically
before even creating the DSP device.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
arch/ar
if this memory is not assigned to the device, but the DSP
remote processor boot will not be successful in such cases. So, check
that memory has been reserved and assigned to the device specifically
before even creating the DSP device.
Signed-off-by: Suman Anna
---
arch/arm/mach-davinci/devices
.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
arch/arm/mach-davinci/devices-da8xx.c | 18 ++
arch/arm/mach-davinci/include/mach/da8xx.h | 5 +
2 files changed, 23 insertions(+)
diff --git a/arch/arm/mach-davinci/devices-da8xx.c
b/arch/arm/mach-davinci/devices-da8xx.c
.
Signed-off-by: Suman Anna
---
arch/arm/mach-davinci/devices-da8xx.c | 18 ++
arch/arm/mach-davinci/include/mach/da8xx.h | 5 +
2 files changed, 23 insertions(+)
diff --git a/arch/arm/mach-davinci/devices-da8xx.c
b/arch/arm/mach-davinci/devices-da8xx.c
index 74c76538cda3
ure before the kobject_init() doesn't
need a kobject_put(). Fix this properly.
Fixes: 75f0aef6220d ("uio: fix memory leak")
Signed-off-by: Suman Anna <s-a...@ti.com>
---
drivers/uio/uio.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/uio/uio.c
ure before the kobject_init() doesn't
need a kobject_put(). Fix this properly.
Fixes: 75f0aef6220d ("uio: fix memory leak")
Signed-off-by: Suman Anna
---
drivers/uio/uio.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 1c196f
From: Joerg Roedel <jroe...@suse.de>
Modify the driver to register individual iommus and
establish links between devices and iommus in sysfs.
Signed-off-by: Joerg Roedel <jroe...@suse.de>
[s-a...@ti.com: fix some cleanup issues during failures]
Signed-off-by: Suman Anna <s-a...
From: Joerg Roedel
Modify the driver to register individual iommus and
establish links between devices and iommus in sysfs.
Signed-off-by: Joerg Roedel
[s-a...@ti.com: fix some cleanup issues during failures]
Signed-off-by: Suman Anna
---
v3 w.r.t v1:
- moved the iommu_device calls in probe
driver.
While at this, also check for the return status from bus_set_iommu.
Signed-off-by: Suman Anna <s-a...@ti.com>
---
v3: New patch
drivers/iommu/omap-iommu.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/omap-iommu.c b/d
driver.
While at this, also check for the return status from bus_set_iommu.
Signed-off-by: Suman Anna
---
v3: New patch
drivers/iommu/omap-iommu.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
Roedel <jroe...@suse.de>
[s-a...@ti.com: revise kerneldoc comments]
Signed-off-by: Suman Anna <s-a...@ti.com>
---
v3 w.r.t v2:
- added kerneldoc comment for @domain
- renamed iommu_arch_data to omap_iommu_arch_data in comments
drivers/iommu/omap-iommu.c | 16 -
701 - 800 of 1689 matches
Mail list logo