Re: [PATCH v1 1/6] DT bindings: add bindings for ov965x camera module

On 06/23/2017 01:59 PM, H. Nikolaus Schaller wrote: > Hi Suman, > >> Am 23.06.2017 um 20:05 schrieb Suman Anna <s-a...@ti.com>: >> >>>>> >>>>> Or does it just mean that it defines the property name? >>>> >>>> Please rea

Re: [PATCH v3 0/3] Add Keystone2 Remoteproc driver

On 06/13/2017 06:45 PM, Suman Anna wrote: > Hi Bjorn, > > This is v3 of the patchset that adds the DT binding and the driver for > loading and booting the DSP devices present on various Keystone2 SoC families. > The binding and driver patches have already been acked by Rob Herring

Re: [PATCH 0/4] Davinci remoteproc cleanups/fixes

On 06/08/2017 03:47 PM, Suman Anna wrote: > 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.

Re: [RFC PATCH 2/3] remoteproc: imx_rproc: add a NXP/Freescale imx rproc driver

On 06/23/2017 09:35 AM, Oleksij Rempel wrote: > On Wed, Jun 21, 2017 at 04:09:26PM -0500, Suman Anna wrote: >> Hi Oleksij, >> >> On 06/19/2017 02:43 AM, Oleksij Rempel wrote: >>> Hi, >>> >>> Thank you for your review! >>> >>> On 15

Re: [PATCH v1 1/6] DT bindings: add bindings for ov965x camera module

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

Re: [PATCH 4/4] remoteproc/davinci: streamline the interrupt management

Hi Bjorn, On 06/25/2017 04:19 PM, Bjorn Andersson wrote: > On Thu 18 May 15:09 PDT 2017, Suman Anna wrote: > >> The davinci remoteproc driver is currently requesting its interrupt >> that deals with the virtio kicks in probe, and that too before all >> the a

Re: [PATCH v3 2/3] remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs

Hi Bjorn, On 06/25/2017 03:15 PM, Bjorn Andersson wrote: > On Tue 13 Jun 16:45 PDT 2017, Suman Anna wrote: > >> +static int keystone_rproc_start(struct rproc *rproc) >> +{ >> +struct keystone_rproc *ksproc = rproc->priv; >> +int ret; >> + >

Re: [PATCH v3 2/3] remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs

On 06/26/2017 03:06 PM, Bjorn Andersson wrote: > On Mon 26 Jun 08:54 PDT 2017, Suman Anna wrote: > >> Hi Bjorn, >> >> On 06/25/2017 03:15 PM, Bjorn Andersson wrote: >>> On Tue 13 Jun 16:45 PDT 2017, Suman Anna wrote: >>> >>>>

Re: [PATCH 1/3] ARM: davinci: da8xx: Create DSP device only when assigned memory

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 >>

[PATCH v5 1/2] Documentation: dt: reset: Add TI SCI reset binding

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

[PATCH v5 0/2] Add TI SCI Reset Driver

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

[PATCH v5 2/2] reset: Add the TI SCI reset driver

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

[PATCH] reset: ti_syscon: Rename TI_SYSCON_RESET to RESET_TI_SYSCON

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

[PATCH 3/3] remoteproc/keystone: ensure the DSPs are in reset in probe

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

Re: [PATCH v4 1/5] rpmsg: virtio_rpmsg: set rpmsg_buf_size customizable

llardy <loic.palla...@st.com> Acked-by: Suman Anna <s-a...@ti.com> regards Suman

[PATCH 1/3] Documentation: DT: add Keystone DSP remoteproc binding

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

[PATCH 0/3] Add Keystone2 Remoteproc driver

[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

[PATCH 2/3] remoteproc/keystone: add a remoteproc driver for Keystone 2 DSPs

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 <

[PATCH 1/4] remoteproc/davinci: Switch to platform_get_resource_byname()

. 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

[PATCH 3/4] Documentation: dt: Add bindings for Davinci DSP processors

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

[PATCH 2/4] remoteproc/davinci: add support to parse internal memories

. 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

[PATCH 4/4] remoteproc/davinci: Add device tree support for OMAP-L138 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

[PATCH 0/4] Add DT support for davinci remoteproc driver

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

[PATCH 3/4] remoteproc/davinci: fix unbalanced reset between start and stop ops

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

[PATCH 4/4] remoteproc/davinci: streamline the interrupt management

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

[PATCH 0/4] Davinci remoteproc cleanups/fixes

. - 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

[PATCH 2/4] remoteproc/davinci: simplify the reset function

() 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

[PATCH 1/4] remoteproc/davinci: Update Kconfig to depend on DMA_CMA

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/3] ARM: davinci: da8xx: Add DSP internal RAM memories as IOMEM resources

. 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

[PATCH 1/3] ARM: davinci: da8xx: Create DSP device only when assigned memory

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

[PATCH 2/3] ARM: davinci: da8xx: Add names to DSP IOMEM resources

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

[PATCH 0/3] Davinci DSP remoteproc device improvements

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

Re: [PATCH v5 0/2] Add TI SCI Reset Driver

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

Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops

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

Re: [PATCH] rpmsg: virtio_rpmsg_bus: cleanup multiple assignment to ops

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

Re: [PATCH] rpmsg: Release rpmsg devices in backends

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 +++ >>

[PATCH v2 2/3] remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs

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 <

[PATCH v2 3/3] remoteproc/keystone: Ensure the DSPs are in reset in probe

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,

[PATCH v2 1/3] dt-bindings: remoteproc: Add Keystone DSP remoteproc binding

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

[PATCH v2 0/3] Add Keystone2 Remoteproc driver

/?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

Re: [PATCH 3/4] Documentation: dt: Add bindings for Davinci DSP processors

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:

Re: [PATCH 1/3] Documentation: DT: add Keystone DSP remoteproc binding

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

Re: [PATCH 0/4] Davinci remoteproc cleanups/fixes

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

Re: [PATCH 1/3] Documentation: DT: add Keystone DSP remoteproc binding

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. >>>> &

Re: [PATCH 1/2] remoteproc: Add remote processor coredump support

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

Re: [RFC PATCH 2/3] remoteproc: imx_rproc: add a NXP/Freescale imx rproc driver

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

[PATCH v3 3/3] remoteproc/keystone: Ensure the DSPs are in reset in probe

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,

[PATCH v3 2/3] remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs

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 <

[PATCH v3 0/3] Add Keystone2 Remoteproc driver

://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

[PATCH v3 1/3] dt-bindings: remoteproc: Add Keystone DSP remoteproc binding

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

Re: [RFC PATCH 2/3] remoteproc: imx_rproc: add a NXP/Freescale imx rproc driver

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

Re: [PATCH 1/3] Documentation: DT: add Keystone DSP remoteproc binding

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

[PATCH] ARM: davinci_all_defconfig: enable CMA options

Enable the CMA and DMA_CMA Kconfig options by default for Davinci platforms. Davinci remoteproc driver is one of the modules that depends on these options, and this allows the driver to be made visible for selection with menuconfig. Signed-off-by: Suman Anna <s-a...@ti.com> --- Hi Sekhar,

Re: [PATCH 0/3] Add and enable DSP device on OMAPL138 LCDK board

On 09/20/2017 10:14 AM, Sekhar Nori wrote: > Hi Suman, > > On Tuesday 19 September 2017 05:58 AM, Suman Anna wrote: >> Hi Sekhar, >> >> The following series adds the DT node for the DSP device present on >> on DA850/OMAPL138 SoCs. The node is disabled in

Re: [PATCH] ARM: davinci_all_defconfig: enable CMA options

On 09/21/2017 09:43 AM, Sekhar Nori wrote: > On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote: >> Enable the CMA and DMA_CMA Kconfig options by default for >> Davinci platforms. Davinci remoteproc driver is one of the >> modules that depends on these options, and this

Re: [PATCH] ARM: davinci_all_defconfig: enable CMA options

Hi Sekhar, > > On Thursday 21 September 2017 08:41 PM, Suman Anna wrote: >> On 09/21/2017 09:43 AM, Sekhar Nori wrote: >>> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote: >>>> Enable the CMA and DMA_CMA Kconfig options by default for >>>>

[PATCH 2/3] ARM: dts: da850-lcdk: Add and enable CMA reserved pool for DSP

on the OMAP-L138 LCDK board. Signed-off-by: Suman Anna <s-a...@ti.com> --- arch/arm/boot/dts/da850-lcdk.dts | 18 ++ 1 file changed, 18 insertions(+) diff --git a/arch/arm/boot/dts/da850-lcdk.dts b/arch/arm/boot/dts/da850-lcdk.dts index a0f0916156e6..eed89e659143 100644 --- a/ar

[PATCH 3/3] ARM: davinci: da8xx-dt: Add OF_DEV_AUXDATA entry for DSP clock matching

y. Signed-off-by: Suman Anna <s-a...@ti.com> --- arch/arm/mach-davinci/da8xx-dt.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-davinci/da8xx-dt.c b/arch/arm/mach-davinci/da8xx-dt.c index 5699ce39e64f..f06db6700ab2 100644 --- a/arch/arm/mach-davinci/da8xx-dt.c +++ b/arch/

[PATCH 0/3] Add and enable DSP device on OMAPL138 LCDK board

board. Supported features include basic load/boot (tested with rpmsg_client_sample) using external memory from the CMA pool. regards Suman Suman Anna (3): ARM: dts: da850: Add DSP node ARM: dts: da850-lcdk: Add and enable CMA reserved pool for DSP ARM: davinci: da8xx-dt: Add OF_DEV_AUXDATA

[PATCH 1/3] ARM: dts: da850: Add DSP node

signalling register and shared memory for inter-processor communication with the ARM core. The node has been added in disabled state, and can be enabled in the respective board dts file with an associated reserved memory block. Signed-off-by: Suman Anna <s-a...@ti.com> --- arch/arm/boot/dts/da85

[PATCH v2 1/2] iommu/omap: Change the attach detection logic

multiple iommu devices to be bound to a single iommu domain, and thereby to a client device. Signed-off-by: Suman Anna <s-a...@ti.com> --- v2: No changes drivers/iommu/omap-iommu.c | 17 +++-- 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/drivers/iommu/omap-iom

[PATCH v2 2/2] iommu/omap: Add support to program multiple iommus

. Signed-off-by: Suman Anna <s-a...@ti.com> [t-kri...@ti.com: ported support to 4.13 based kernel] Signed-off-by: Tero Kristo <t-kri...@ti.com> --- v2: - Added a new helper omap_iommu_can_register() function which is used in probe to selectively register the probed IOMMU platfor

[PATCH v2 0/2] Dual MMU support for TI DRA7xx DSPs

Aug 8 03:59 subsystem -> ../../../../bus/platform -rw-r--r--1 root root 4096 Aug 8 03:59 uevent Suman Anna (2): iommu/omap: Change the attach detection logic iommu/omap: Add support to program multiple iommus drivers/iommu/omap-iommu.c | 375 ++---

Re: [PATCH v4 2/5] rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address

off-by: Ludovic Barre <ludovic.ba...@st.com> > Signed-off-by: Loic Pallardy <loic.palla...@st.com> > Acked-by: Patrice Chotard <patrice.chot...@st.com> > Tested-by: Suman Anna <s-a...@ti.com> Can you pick up the first 2 patches from this series for v4.14? This does enab

Re: [PATCH 071/102] remoteproc/keystone: explicitly request exclusive reset control

Hi Bjorn, On 07/19/2017 11:59 AM, Suman Anna wrote: > On 07/19/2017 10:26 AM, Philipp Zabel wrote: >> Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting >> reset lines") started to transition the reset control request API calls >> to explicitly

[PATCH 0/2] Dual MMU support for TI DRA7xx DSPs

3 root root 0 Aug 8 04:03 remoteproc lrwxrwxrwx1 root root 0 Aug 8 03:59 subsystem -> ../../../../bus/platform -rw-r--r--1 root root 4096 Aug 8 03:59 uevent Suman Anna (2): iommu/omap: Change the attach detection logic

[PATCH 2/2] iommu/omap: Add support to program multiple iommus

still continues to operate on individual IOMMU objects. Signed-off-by: Suman Anna <s-a...@ti.com> [t-kri...@ti.com: ported support to 4.13 based kernel] Signed-off-by: Tero Kristo <t-kri...@ti.com> --- drivers/iommu/omap-iommu.c | 307 ++--- d

[PATCH 1/2] iommu/omap: Change the attach detection logic

multiple iommu devices to be bound to a single iommu domain, and thereby to a client device. Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/iommu/omap-iommu.c | 17 +++-- 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/drivers/iommu/omap-iommu.c b/drivers/iomm

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

On 09/01/2017 11:33 AM, Joerg Roedel wrote: > Hi Suman, > On Fri, Sep 01, 2017 at 11:21:45AM -0500, Suman Anna wrote: >> It's primarily a question of whether each iommu platform device need to >> be represented as a unique iommu_device or not. If you still think that

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Joerg, On 09/01/2017 05:01 AM, Joerg Roedel wrote: > Hi Suman, > > On Thu, Aug 31, 2017 at 08:14:02AM -0500, Suman Anna wrote: >> The OMAP IOMMU driver has been enhanced to support allowing >> multiple IOMMUs to be programmed by a single client user. This >> su

Re: [PATCH] remoteproc: Introduce rproc handle accessor for children

Hi Bjorn, On 08/28/2017 12:34 AM, Bjorn Andersson wrote: > In certain circumstances rpmsg devices needs to acquire a handle to the > ancestor remoteproc instance, e.g. to invoke rproc_report_crash() when a > fatal error is detected. Introduce an interface that walks the device > tree in search

Re: [PATCH] mailbox/omap: unregister mbox class

On 11/11/2017 12:09 PM, Arvind Yadav wrote: > platform_driver_register() can fail here and we must unregister mbox > class. > > Signed-off-by: Arvind Yadav <arvind.yadav...@gmail.com> Acked-by: Suman Anna <s-a...@ti.com> regards Suman > --- > drivers/mailbox/

Re: [PATCH v6 5/7] remoteproc/davinci: use octal permissions for module_param()

Acked-by from v3, so adding it back Acked-by: Suman Anna <s-a...@ti.com> regards Suman > --- > drivers/remoteproc/da8xx_remoteproc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/remoteproc/da8xx_remoteproc.c > b/drivers/remoteproc/da

[PATCH 2/6] hwspinlock/omap: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the OMAP hwspinlock driver source file and drop the previous boilerplate license text. Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/hwspinlock/omap_hwspinlock.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff

[PATCH 3/6] hwspinlock: qcom: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the Qualcomm Hwspinlock driver source file and drop the previous boilerplate license text. Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/hwspinlock/qcom_hwspinlock.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff

[PATCH 5/6] hwspinlock/u8500: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the U8500 HWSEM driver source file and drop the previous boilerplate license text. Cc: Mathieu J. Poirier <mathieu.poir...@linaro.org> Cc: Linus Walleij <linus.wall...@linaro.org> Signed-off-by: Suman Anna <s-a...@ti.com> ---

[PATCH 6/6] hwspinlock: sprd: Switch to SPDX license identifier

Use the appropriate SPDX license identifiers in the Spreadtrum hardware spinlock driver source file and drop the previous boilerplate license text. Cc: Baolin Wang <baolin.w...@spreadtrum.com> Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/hwspinlock/sprd_hwspinlock.c | 10 +

[PATCH 0/6] hwspinlock: Convert to use SPDX license identifiers

at the earliest so that they can be picked up for 4.18. regards Suman Suman Anna (6): hwspinlock/core: Switch to SPDX license identifier hwspinlock/omap: Switch to SPDX license identifier hwspinlock: qcom: Switch to SPDX license identifier hwspinlock/sirf: Switch to SPDX license identifier

[PATCH 1/6] hwspinlock/core: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the Hwspinlock core driver source files and drop the previous boilerplate license text. Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/hwspinlock/Kconfig | 1 + drivers/hwspinlock/hwspinlock_core.c | 10 +- d

[PATCH 4/6] hwspinlock/sirf: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the CSR's SIRF hardware spinlock driver source file and drop the previous boilerplate license text. Cc: Wei Chen <wei.c...@csr.com> Cc: Barry Song <bao...@kernel.org> Signed-off-by: Suman Anna <s-a...@ti.com> --- drivers/hwspinlock

Re: Nokia N900: refcount_t underflow, use after free

Pavel > >> regards >> Suman >> >>> >>> (Camera still does not work in -next... kills system. Oh well. Lets >>> debug that some other day.) >>> >>>> 8<

Re: [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups

On 04/02/2018 11:49 AM, Suman Anna wrote: > Hi Viresh, > > Please find the updated series replacing the previous patch [1] fixing > couple of issues in the TI CPUFreq driver. I have split up the patches > as per your comments on v1. Final code diff remains the same as before. >

[PATCH 0/5] rpmsg: Convert to use SPDX license identifiers

. Patches done on top of latest upstream kernel. regards Suman Suman Anna (5): rpmsg: Switch to SPDX license identifier rpmsg: virtio_rpmsg_bus: Switch to SPDX license identifier rpmsg: smd: Switch to SPDX license identifier rpmsg: glink: Switch to SPDX license identifier rpmsg: char: Switch

[PATCH 1/5] rpmsg: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the rpmsg core source files and drop the previous boilerplate license text. Signed-off-by: Suman Anna --- drivers/rpmsg/Kconfig | 2 ++ drivers/rpmsg/rpmsg_core.c | 10 +- drivers/rpmsg/rpmsg_internal.h | 10

[PATCH 3/5] rpmsg: smd: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the rpmsg SMD backend driver source file and drop the previous boilerplate license text. Signed-off-by: Suman Anna --- drivers/rpmsg/qcom_smd.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/drivers/rpmsg/qcom_smd.c b

[PATCH 5/5] rpmsg: char: Switch to SPDX license identifier

the same. Signed-off-by: Suman Anna --- drivers/rpmsg/rpmsg_char.c | 10 +- include/uapi/linux/rpmsg.h | 9 - 2 files changed, 1 insertion(+), 18 deletions(-) diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c index 1efdf9ff8679..76a4477c6364 100644 --- a/drivers

[PATCH 4/5] rpmsg: glink: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in various rpmsg glink driver source files and drop the previous boilerplate license text. Signed-off-by: Suman Anna --- drivers/rpmsg/qcom_glink_native.c | 10 +- drivers/rpmsg/qcom_glink_native.h | 10 +- drivers/rpmsg

[PATCH 2/5] rpmsg: virtio_rpmsg_bus: Switch to SPDX license identifier

Use the appropriate SPDX license identifier in the virtio rpmsg bus driver source file and drop the previous boilerplate license text. Signed-off-by: Suman Anna --- drivers/rpmsg/virtio_rpmsg_bus.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/drivers/rpmsg

[PATCH v3 0/2] ti-cpufreq: minor fixes/cleanups

://patchwork.kernel.org/patch/10308925/ Suman Anna (2): cpufreq: ti-cpufreq: Fix an incorrect error return value cpufreq: ti-cpufreq: Use devres managed API in probe() drivers/cpufreq/ti-cpufreq.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) -- 2.17.0

[PATCH v3 2/2] cpufreq: ti-cpufreq: Use devres managed API in probe()

The ti_cpufreq_probe() function uses regular kzalloc to allocate the ti_cpufreq_data structure and kfree for freeing this memory on failures. Simplify this code by using the devres managed API. Cc: Zumeng Chen Signed-off-by: Suman Anna Acked-by: Viresh Kumar --- drivers/cpufreq/ti-cpufreq.c

[PATCH v3 1/2] cpufreq: ti-cpufreq: Fix an incorrect error return value

829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when failure") Cc: Zumeng Chen Cc: # v4.14+ Signed-off-by: Suman Anna Acked-by: Viresh Kumar --- drivers/cpufreq/ti-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/

Re: [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups

Hi Rafael, On 05/18/2018 03:19 PM, Rafael J. Wysocki wrote: > On Friday, May 18, 2018 5:07:12 PM CEST Suman Anna wrote: >> On 04/02/2018 11:49 AM, Suman Anna wrote: >>> Hi Viresh, >>> >>> Please find the updated series replacing the previous patch [1] fixing &g

Re: New remoteproc driver for TI PRU

Hi David, On 06/29/2018 12:44 PM, David Lechner wrote: > On 06/29/2018 04:58 AM, Roger Quadros wrote: >> +Suman & Tero >> >> Hi David, >> >> On 24/06/18 00:08, David Lechner wrote: >>> >>> Date: Sat, 23 Jun 2018 15:43:59 -0500 >>> Subject: [PATCH 0/8] New remoteproc driver for TI PRU >>> >>> This

Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver

gt; Tony > > 8< --- > From tony Mon Sep 17 00:00:00 2001 > From: Tony Lindgren <t...@atomide.com> > Date: Mon, 15 Jan 2018 15:25:54 -0800 > Subject: [PATCHv2] reset: ti-rstctrl: use the reset-simple driver > > We can support the RSTCT

Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver

Hi Tony, On 01/16/2018 05:22 PM, Tony Lindgren wrote: > Hi, > > * Suman Anna <s-a...@ti.com> [180116 21:23]: >> While this adaptation is very simple for replacing the RSTCTRL registers >> from the hwmod data into an existing reset driver, I am afraid that it >&g

Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver

Hi Tony, On 01/19/2018 03:33 PM, Tony Lindgren wrote: > * Suman Anna <s-a...@ti.com> [180119 20:23]: >> On 01/16/2018 05:22 PM, Tony Lindgren wrote: >>> The RSTST registers mostly tell the device internal reset reason >>> like watchdog reset for an accelera

Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver

On 01/19/2018 05:49 PM, Tony Lindgren wrote: > * Suman Anna <s-a...@ti.com> [180119 23:30]: >> On 01/19/2018 03:33 PM, Tony Lindgren wrote: >>> OK let's do some tests on that, I'll take a look at doing a dts >>> file over next few weeks. >> >> You can

Re: [PATCH v7 3/9] arm: omap: Move dmtimer.h out of plat-omap

Hi Keerthy, On 01/09/2018 12:23 AM, J, KEERTHY wrote: > The header file is currently under plat-omap directory > under arch/omap. Move this out to an accessible place. > > No Code changes done to the header file. > > Signed-off-by: Keerthy > Reviewed-by: Sebastian Reichel

Re: [PATCH v7 4/9] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource

Hi Keerthy, On 01/09/2018 12:23 AM, J, KEERTHY wrote: > Move the dmtimer driver out of plat-omap to clocksource. > So that non-omap devices also could use this. What non-omap devices do you have in mind? I don't think this driver is ready for that yet. It still has a lot of OMAP dependencies. So

Re: [PATCH v7 5/9] dmtimer: Add timer ops to the platform data structure

On 01/09/2018 12:23 AM, J, KEERTHY wrote: > Add timer ops to the platform data structure > > Signed-off-by: Keerthy > Reviewed-by: Sebastian Reichel > Tested-by: Ladislav Michl > --- >

<    1   2   3   4   5   6   7   8   9   10   >