[PATCH v4 02/12] clk: mux: Split out register accessors for reuse

From: Stephen Boyd We want to reuse the logic in clk-mux.c for other clock drivers that don't use readl as register accessors. Fortunately, there really isn't much to the mux code besides the table indirection and quirk flags if you assume any bit shifting and masking has been done already. Pull

[PATCH v4 05/12] clk: qcom: Add MSM8960/APQ8064's HFPLLs

From: Stephen Boyd Describe the HFPLLs present on MSM8960 and APQ8064 devices. Signed-off-by: Stephen Boyd --- drivers/clk/qcom/gcc-msm8960.c | 172 +++ include/dt-bindings/clock/qcom,gcc-msm8960.h | 2 + 2

[PATCH v4 05/12] clk: qcom: Add MSM8960/APQ8064's HFPLLs

From: Stephen Boyd Describe the HFPLLs present on MSM8960 and APQ8064 devices. Signed-off-by: Stephen Boyd --- drivers/clk/qcom/gcc-msm8960.c | 172 +++ include/dt-bindings/clock/qcom,gcc-msm8960.h | 2 + 2 files changed, 174 insertions(+) diff --git

[PATCH v4 01/12] ARM: Add Krait L2 register accessor functions

From: Stephen Boyd Krait CPUs have a handful of L2 cache controller registers that live behind a cp15 based indirection register. First you program the indirection register (l2cpselr) to point the L2 'window' register (l2cpdr) at what you want to read/write. Then you

[PATCH v4 01/12] ARM: Add Krait L2 register accessor functions

From: Stephen Boyd Krait CPUs have a handful of L2 cache controller registers that live behind a cp15 based indirection register. First you program the indirection register (l2cpselr) to point the L2 'window' register (l2cpdr) at what you want to read/write. Then you read/write the 'window'

[PATCH v4 00/12] Krait clocks + Krait CPUfreq

fe parent patch. [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332607.html [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332615.html [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332608.html Sricharan R (2): clk: qcom:

[PATCH v4 00/12] Krait clocks + Krait CPUfreq

fe parent patch. [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332607.html [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332615.html [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332608.html Sricharan R (2): clk: qcom:

Re: [PATCH v5 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

On 11/14/2017 4:23 PM, Sricharan R wrote: > IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan > (Lithium) IP. An mdt type single image format is used for the > firmware. So the mdt_load function can be directly used to load > the firmware. Also add the relevant res

Re: [PATCH v5 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

On 11/14/2017 4:23 PM, Sricharan R wrote: > IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan > (Lithium) IP. An mdt type single image format is used for the > firmware. So the mdt_load function can be directly used to load > the firmware. Also add the relevant res

[PATCH v5 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5

[PATCH v5 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 38

[PATCH v5 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

t;r...@kernel.org> Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 7 ++- drivers/remoteproc/Kconfig | 1 + drivers/remoteproc/qcom_q6v5_pil.c | 53 +- 3 files changed, 59 inse

[PATCH v5 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

-by: Sricharan R --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 7 ++- drivers/remoteproc/Kconfig | 1 + drivers/remoteproc/qcom_q6v5_pil.c | 53 +- 3 files changed, 59 insertions(+), 2 deletions(-) diff --git a/Documentation

[PATCH v5 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c

[PATCH v5 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 166 - 1 file

[PATCH v5 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+)

[PATCH v5 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff --git a/drivers/remoteproc

[PATCH v5 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R <sricha...@codeaurora.

[PATCH v5 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R --- drivers/remoteproc

[PATCH v5 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

ed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/soc/qcom/mdt_loader.c | 82 ++--- include/linux/soc/qcom/mdt_loader.h | 3 ++ 2 files changed, 62 insertions(+), 23 deletions(-) diff --git a/drivers/soc/qcom/mdt_loader.c b/drivers/soc/qcom/

[PATCH v5 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Acked-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers

[PATCH v5 0/6] Add support for Hexagon q6v5-wcss integrated core

on top of latest remoteproc next V2: Last time introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export

[PATCH v5 0/6] Add support for Hexagon q6v5-wcss integrated core

on top of latest remoteproc next V2: Last time introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export

Re: [PATCH v4 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

Hi Rob, On 11/11/2017 2:38 AM, Rob Herring wrote: > On Thu, Nov 09, 2017 at 08:16:14PM +0530, Sricharan R wrote: >> IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan >> (Lithium) IP. An mdt type single image format is used for the >> firmware. So the

Re: [PATCH v4 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

Hi Rob, On 11/11/2017 2:38 AM, Rob Herring wrote: > On Thu, Nov 09, 2017 at 08:16:14PM +0530, Sricharan R wrote: >> IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan >> (Lithium) IP. An mdt type single image format is used for the >> firmware. So the

[PATCH v4 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R <sricha...@codeaurora.

[PATCH v4 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R --- drivers/remoteproc

[PATCH v4 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5

[PATCH v4 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R <sri

[PATCH v4 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 38

[PATCH v4 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R

[PATCH v4 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c

[PATCH v4 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 166 - 1 file

[PATCH v4 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

ed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/soc/qcom/mdt_loader.c | 82 ++--- include/linux/soc/qcom/mdt_loader.h | 3 ++ 2 files changed, 62 insertions(+), 23 deletions(-) diff --git a/drivers/soc/qcom/mdt_loader.c b/drivers/soc/qcom/

[PATCH v4 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+)

[PATCH v4 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Acked-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers

[PATCH v4 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff --git a/drivers/remoteproc

[PATCH v4 0/6] Add support for Hexagon q6v5-wcss integrated core

introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export rproc_elf_get_boot_addr remoteproc: qcom: Push reset

[PATCH v4 0/6] Add support for Hexagon q6v5-wcss integrated core

introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export rproc_elf_get_boot_addr remoteproc: qcom: Push reset

Re: [PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

ches and repost. Otherwise, just hope that you were ok with the approach [1]. [1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1481961.html Regards, Sricharan -- "QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Re: [PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

ches and repost. Otherwise, just hope that you were ok with the approach [1]. [1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1481961.html Regards, Sricharan -- "QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Re: [PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

Hi Bjorn, On 10/12/2017 11:56 PM, Bjorn Andersson wrote: > On Wed 30 Aug 21:45 PDT 2017, Sricharan R wrote: > >> qcom_mdt_load function loads the mdt type firmware and >> initialises the secure memory as well. Make the initialisation only >> when requested by the caller,

Re: [PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

Hi Bjorn, On 10/12/2017 11:56 PM, Bjorn Andersson wrote: > On Wed 30 Aug 21:45 PDT 2017, Sricharan R wrote: > >> qcom_mdt_load function loads the mdt type firmware and >> initialises the secure memory as well. Make the initialisation only >> when requested by the caller,

Re: [PATCH v4] dmaengine: qcom-bam: Process multiple pending descriptors

On 9/25/2017 11:50 AM, Vinod Koul wrote: > On Mon, Aug 28, 2017 at 08:30:24PM +0530, Sricharan R wrote: >> The bam dmaengine has a circular FIFO to which we >> add hw descriptors that describes the transaction. >> The FIFO has space for about 4096 hw descriptors. >&

Re: [PATCH v4] dmaengine: qcom-bam: Process multiple pending descriptors

On 9/25/2017 11:50 AM, Vinod Koul wrote: > On Mon, Aug 28, 2017 at 08:30:24PM +0530, Sricharan R wrote: >> The bam dmaengine has a circular FIFO to which we >> add hw descriptors that describes the transaction. >> The FIFO has space for about 4096 hw descriptors. >&

Re: [PATCH v3 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

Hi Rob, On 9/12/2017 7:51 PM, Rob Herring wrote: > On Thu, Aug 31, 2017 at 10:15:33AM +0530, Sricharan R wrote: >> IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan >> (Lithium) IP. An mdt type single image format is used for the >> firmware. So the

Re: [PATCH v3 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

Hi Rob, On 9/12/2017 7:51 PM, Rob Herring wrote: > On Thu, Aug 31, 2017 at 10:15:33AM +0530, Sricharan R wrote: >> IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan >> (Lithium) IP. An mdt type single image format is used for the >> firmware. So the

[PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- d

[PATCH v3 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R <sri

[PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R --- drivers/soc/qcom/mdt_loader.c

[PATCH v3 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R

[PATCH v3 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+)

[PATCH v3 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff --git a/drivers/remoteproc

[PATCH v3 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c

[PATCH v3 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 166 - 1 file

[PATCH v3 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5

[PATCH v3 0/6] Add support for Hexagon q6v5-wcss integrated core

. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export rproc_elf_get_boot_addr remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start

[PATCH v3 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R <sricha...@codeaurora.

[PATCH v3 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R --- drivers/remoteproc

[PATCH v3 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 38

[PATCH v3 0/6] Add support for Hexagon q6v5-wcss integrated core

. Sricharan R (6): remoteproc: qcom: mdt_loader: Make the firmware authentication optional remoteproc: Export rproc_elf_get_boot_addr remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start

[PATCH v2 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R <sricha...@codeaurora.

[PATCH v2 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R --- drivers/remoteproc

[PATCH v2 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c

[PATCH v2 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 165 + 1 file

[PATCH v2 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R <sri

[PATCH v2 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R

[PATCH v2 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+)

[PATCH v2 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff --git a/drivers/remoteproc

[PATCH v2 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/remoteproc/qcom_q6v5

[PATCH v2 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 38

[PATCH v2 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- d

[PATCH v2 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R --- drivers/soc/qcom/mdt_loader.c

[PATCH v2 0/6] Add support for Hexagon q6v5-wcss integrated core

. This is done on top of Avaneesh's msm8996 rproc support [1] [1] https://lkml.org/lkml/2017/7/21/217 V2: Last time introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make

[PATCH v2 0/6] Add support for Hexagon q6v5-wcss integrated core

. This is done on top of Avaneesh's msm8996 rproc support [1] [1] https://lkml.org/lkml/2017/7/21/217 V2: Last time introduced this a new rproc driver, but there is lot of code that can be shared if it is added to the q6v5-mpss pil driver. Sricharan R (6): remoteproc: qcom: mdt_loader: Make

Re: [PATCH v2 11/20] rpmsg: glink: Fix idr_lock from mutex to spinlock

Hi Chris, On 8/29/2017 3:21 AM, Chris Lew wrote: > Hi Sricharan, > > Minor bug in this patch. > > On 8/24/2017 12:21 AM, Sricharan R wrote: > [..] >> @@ -829,11 +839,14 @@ static int qcom_glink_rx_open(struct qcom_glink >> *glink, unsigned int rcid, >

Re: [PATCH v2 11/20] rpmsg: glink: Fix idr_lock from mutex to spinlock

Hi Chris, On 8/29/2017 3:21 AM, Chris Lew wrote: > Hi Sricharan, > > Minor bug in this patch. > > On 8/24/2017 12:21 AM, Sricharan R wrote: > [..] >> @@ -829,11 +839,14 @@ static int qcom_glink_rx_open(struct qcom_glink >> *glink, unsigned int rcid, >

[PATCH v4] dmaengine: qcom-bam: Process multiple pending descriptors

dma interrupts (after tests): 58806 Signed-off-by: Sricharan R <sricha...@codeaurora.org> Reviewed-by: Andy Gross <andy.gr...@linaro.org> Tested-by: Abhishek Sahu <abs...@codeaurora.org> --- [v4] Rebased against https://patchwork.kernel.org/patch/9874691/ and updated tags.

[PATCH v4] dmaengine: qcom-bam: Process multiple pending descriptors

dma interrupts (after tests): 58806 Signed-off-by: Sricharan R Reviewed-by: Andy Gross Tested-by: Abhishek Sahu --- [v4] Rebased against https://patchwork.kernel.org/patch/9874691/ and updated tags. drivers/dma/qcom/bam_dma.c | 169 + 1 file

[PATCH v2 02/20] rpmsg: glink: Associate indirections for pipe fifo accessor's

ersson <bjorn.anders...@linaro.org> Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/qcom_glink_rpm.c | 144 ++--- 1 file changed, 106 insertions(+), 38 deletions(-) diff --git a/drivers/rpmsg/qcom_glink_rpm.c b/drivers/rpmsg/qcom_glink_r

[PATCH v2 02/20] rpmsg: glink: Associate indirections for pipe fifo accessor's

indirections, so that the rest of the code can be shared. For this, have a qcom_glink_pipe that can be used in the common code containing the indirections and wrap it with glink_rpm_pipe that contains the transport specific members. Signed-off-by: Bjorn Andersson Signed-off-by: Sricharan R

[PATCH v2 03/20] rpmsg: glink: Split rpm_probe to reuse the common code

nsport. Also reuse driver's remove as well. Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/qcom_glink_rpm.c | 85 -- 1 file changed, 49 insertions(+), 36 deleti

[PATCH v2 04/20] rpmsg: glink: Move the common glink protocol implementation to glink_native.c

From: Bjorn Andersson <bjorn.anders...@linaro.org> Move the common part of glink core protocol implementation to glink_native.c that can be shared with the smem based glink transport in the later patches. Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> Signed-off-by:

[PATCH v2 03/20] rpmsg: glink: Split rpm_probe to reuse the common code

as well. Signed-off-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers/rpmsg/qcom_glink_rpm.c | 85 -- 1 file changed, 49 insertions(+), 36 deletions(-) diff --git a/drivers/rpmsg/qcom_glink_rpm.c b/drivers/rpmsg/qcom_glink_rpm.c index 870ce32

[PATCH v2 04/20] rpmsg: glink: Move the common glink protocol implementation to glink_native.c

From: Bjorn Andersson Move the common part of glink core protocol implementation to glink_native.c that can be shared with the smem based glink transport in the later patches. Signed-off-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers/rpmsg/Kconfig |6 +- drivers

[PATCH v2 07/20] rpmsg: glink: Do a mbox_free_channel in remove

mbox_request_channel is done in probe, so free the channel in remove. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/qcom_glink_native.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rpmsg/qcom_glink_native.c b/drivers/rpmsg/qcom_glink_native.c

[PATCH v2 08/20] rpmsg: glink: Introduce glink smem based transport

Adding a new smem transport register function and the fifo accessors for the same. Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/Kconfig | 10 ++ drivers/rpmsg/Makefile|

[PATCH v2 06/20] rpmsg: glink: Return -EAGAIN when there is no FIFO space

The TX FIFO can be full, if the remote client has not read enough data (or) reading it slowly. So its nessecary to return -EAGAIN to the local client to enable retry. Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/qcom_glink_native.c | 2 +- 1 file changed, 1 ins

[PATCH v2 07/20] rpmsg: glink: Do a mbox_free_channel in remove

mbox_request_channel is done in probe, so free the channel in remove. Signed-off-by: Sricharan R --- drivers/rpmsg/qcom_glink_native.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rpmsg/qcom_glink_native.c b/drivers/rpmsg/qcom_glink_native.c index 94b79e8..21adde3 100644

[PATCH v2 08/20] rpmsg: glink: Introduce glink smem based transport

function and the fifo accessors for the same. Signed-off-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers/rpmsg/Kconfig | 10 ++ drivers/rpmsg/Makefile| 1 + drivers/rpmsg/qcom_glink_native.c | 5 + drivers/rpmsg/qcom_glink_native.h | 1 + drivers/rpmsg

[PATCH v2 06/20] rpmsg: glink: Return -EAGAIN when there is no FIFO space

The TX FIFO can be full, if the remote client has not read enough data (or) reading it slowly. So its nessecary to return -EAGAIN to the local client to enable retry. Signed-off-by: Sricharan R --- drivers/rpmsg/qcom_glink_native.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH v2 10/20] rpmsg: glink: Add support for transport version negotiation

the transport is opened and they cannot be changed after negotiation has been completed. Each full implementation of G-Link must support a minimum of the current version, the previous version, and the base negotiation version called v0. Signed-off-by: Sricharan R <sricha...@codeaurora.org> Sign

[PATCH v2 10/20] rpmsg: glink: Add support for transport version negotiation

the transport is opened and they cannot be changed after negotiation has been completed. Each full implementation of G-Link must support a minimum of the current version, the previous version, and the base negotiation version called v0. Signed-off-by: Sricharan R Signed-off-by: Bjorn Andersson

[PATCH v2 13/20] rpmsg: glink: Use the local intents when receiving data

So previously on request from remote side, we allocated local intent buffers and passed the ids to the remote. Now when we receive data buffers from remote directed to that intent id, copy the data to the corresponding preallocated intent buffer. Signed-off-by: Sricharan R <sri

[PATCH v2 13/20] rpmsg: glink: Use the local intents when receiving data

So previously on request from remote side, we allocated local intent buffers and passed the ids to the remote. Now when we receive data buffers from remote directed to that intent id, copy the data to the corresponding preallocated intent buffer. Signed-off-by: Sricharan R Signed-off-by: Bjorn

[PATCH v2 12/20] rpmsg: glink: Add support for TX intents

allocate buffers of requested size, store the buffer id locally and also communicate the intent id to the remote. Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> Signed-off-by: Sricharan R <sricha...@codeaurora.org> --- drivers/rpmsg/qcom_glink_na

[PATCH v2 12/20] rpmsg: glink: Add support for TX intents

allocate buffers of requested size, store the buffer id locally and also communicate the intent id to the remote. Signed-off-by: Bjorn Andersson Signed-off-by: Sricharan R --- drivers/rpmsg/qcom_glink_native.c | 167 +- drivers/rpmsg/qcom_glink_native.h | 3

[PATCH v2 18/20] rpmsg: glink: Use the intents passed by remote

While sending data, use the remote intent id buffer of suitable size that was passed by remote previously. Signed-off-by: Sricharan R <sricha...@codeaurora.org> Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> --- drivers/rpmsg/qcom_glink_n

[PATCH v2 18/20] rpmsg: glink: Use the intents passed by remote

While sending data, use the remote intent id buffer of suitable size that was passed by remote previously. Signed-off-by: Sricharan R Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_glink_native.c | 35 +-- 1 file changed, 33 insertions(+), 2 deletions

[PATCH v2 16/20] rpmsg: glink: Add announce_create ops and preallocate intents

the rpmsg device gets probed. Signed-off-by: Sricharan R <sricha...@codeaurora.org> Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org> --- drivers/rpmsg/qcom_glink_native.c | 20 1 file changed, 20 insertions(+) diff --git a/drivers/rpmsg/qcom_glink_native.c b/d

<    4   5   6   7   8   9   10   11   12   13   >