There is no need to implement subroutine for suspend since there is no
data to store before suspending.
Signed-off-by: Grzegorz Jaszczyk
---
drivers/i2c/busses/i2c-mv64xxx.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/i2c/busses/i2c-mv64xxx.c b/drivers/i2c/busses
There is no need to implement subroutine for suspend since there is no
data to store before suspending.
Signed-off-by: Grzegorz Jaszczyk
---
drivers/thermal/armada_thermal.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/thermal/armada_thermal.c b/drivers/thermal
Both SATA and second USB3.0 interface are supported in Armada-39x SoC
family. Add necessary clk description, so both xhci and sata drivers
can be correctly initialized.
The binding documentation has also been updated accordingly.
Signed-off-by: Grzegorz Jaszczyk
---
Documentation/devicetree
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-385-db-ap.dts | 26 +++---
1 file changed, 23 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/armada-385-db-ap.dts
b/arch/arm/boot/dts/armada-385-db-ap.dts
index a18f516..6648a3f 100644
--- a/arch
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-385-db-ap.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/armada-385-db-ap.dts
b/arch/arm/boot/dts/armada-385-db-ap.dts
index 2d3fd6e..a18f516 100644
--- a/arch/arm/boot/dts/armada-385-db-ap.dts
+++ b
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lior Amsalem
---
arch/arm/boot/dts/armada-39x.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/armada-39x.dtsi
b/arch/arm/boot/dts/armada-39x.dtsi
index 03dc0ec..5e01438 100644
--- a/arch/arm/boot/dts
14 introduces armada-395.dtsi which describes Armada 395 SoC family and
patch 15 updates armada-398.dtsi. Next patch updates Armada 398 DB dts about
supported usb interfaces and finally last 2 patches introduces description for 2
board: Armada 390 DB and Armada 395 GP.
Grzegorz Jaszczyk (18
The whole Armada 39x SoC family of processors has GPIO's which all can be
supported with existing driver.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-39x.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/armada-39x
The whole Armada 39x SoC family of processors has one USB2.0 and one
USB3.0 which all can be supported with existing drivers.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-39x.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/armada
Beside interfaces described in the armada-39x.dtsi, the Armada 395 SoC
family supports: 2 x SATA3 (2 ports in one unit) and the USB3.0
Signed-off-by: Grzegorz Jaszczyk
---
.../devicetree/bindings/arm/marvell/armada-39x.txt | 2 +-
arch/arm/boot/dts/armada-395.dtsi | 76
Despite that FS states that rtc is present only in A395 and A398 and not in
A390, the rtc is working with A390.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-39x.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/armada-39x.dtsi
b/arch/arm/boot
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-398-db.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/armada-398-db.dts
b/arch/arm/boot/dts/armada-398-db.dts
index 788c3ba..969b49f 100644
--- a/arch/arm/boot/dts/armada-398-db.dts
+++ b/arch/arm
This commit adds description for following features for this board:
- Serial port
- I2C buses
- 16MB SPI-NOR
- USB2.0
- USB3.0
- PCIe interfaces
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-390-db.dts | 164
1 file changed, 164 insertions
This commit adds description for the following features for this board:
- Serial port
- PCIe interfaces
- USB2.0
- USB3.0
- SDIO
- 1024 MiB NAND-FLASH
- SATA
- I2C buses
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-395-gp.dts | 147
1 file
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-39x.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/armada-39x.dtsi
b/arch/arm/boot/dts/armada-39x.dtsi
index 8a22c02..03dc0ec 100644
--- a/arch/arm/boot/dts/armada-39x.dtsi
+++ b/arch/arm/boot/dts
Beside interfaces described in the armada-39x.dtsi and armada-395.dtsi, the
Armada 398 SoC family supports 2 additional SATA port (2 ports in one unit)
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-398.dtsi | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff
39x SDHCI controller in other to take advantage of this
functionality.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/boot/dts/armada-39x.dtsi | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/armada-39x.dtsi
b/arch/arm/boot/dts/armada-39x.dtsi
ind
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/mvebu_v7_defconfig
b/arch/arm/configs/mvebu_v7_defconfig
index f1a0e25..000a866 100644
--- a/arch/arm/configs/mvebu_v7_defconfig
+++ b/arch/arm/configs
This commit enables:
- CA9's Performance Monitor Unit
- CA9 MPcore SoC Controller
- Coherency fabric
on Armada 39x, basing on the Armada 38x (which has the same CA9 CPU).
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lior Amsalem
---
arch/arm/boot/dts/armada-39x.dtsi | 15 +
This commit enables:
- CA9's Performance Monitor Unit
- CA9 MPcore SoC Controller
- Coherency fabric
on Armada 39x, basing on the Armada 38x (which has the same CA9 CPU).
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lior Amsalem
---
arch/arm/boot/dts/armada-39x.dtsi | 15 +
The armada-390.dtsi was broken since the first patch which adds Device Tree
files for Armada 39x SoC was introduced.
Signed-off-by: Grzegorz Jaszczyk
Cc: # 4.0+
Fixes 538da83 ("ARM: mvebu: add Device Tree files for Armada 39x SoC and board")
---
arch/arm/boot/dts/armada-390.dtsi
UBIFS is commonly used on Marvell EBU v7 platforms to store the root
file-system, so it makes sense to have those options enabled by default
in mvebu_v7_defconfig.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/mvebu_v7_defconfig
b/arch/arm/configs/mvebu_v7_defconfig
index 486a4ca..f43a7aa 100644
--- a/arch/arm/configs/mvebu_v7_defconfig
+++ b/arch/arm/configs
Hi Russel, Thmoas
2016-07-21 14:46 GMT+02:00 Thomas Petazzoni
:
> Hello,
>
> On Thu, 21 Jul 2016 13:44:09 +0100, Russell King - ARM Linux wrote:
>> On Thu, Jul 21, 2016 at 02:43:59PM +0200, Grzegorz Jaszczyk wrote:
>> > Signed-off-by: Grzegorz Jaszczyk
>>
>> W
Hi Andrew,
2016-07-21 15:43 GMT+02:00 Andrew Lunn :
> On Thu, Jul 21, 2016 at 02:43:56PM +0200, Grzegorz Jaszczyk wrote:
>
> Hi Grzegorz
>
> Some of these patches are missing a commit log entry. Please add at
> least one line.
>
Ok, I will add it in next version of this
Hi Rob,
2016-07-22 0:16 GMT+02:00 Rob Herring :
> On Thu, Jul 21, 2016 at 02:44:11PM +0200, Grzegorz Jaszczyk wrote:
>> -compatible = "marvell,a398-db", "marvell,armada398", "marvell,armada390";
>> +compatible = "marvell,a398-db", "mar
2018-03-02 17:57 GMT+01:00 Mark Rutland :
>> > > Do you see this for a panic() in *any* interrupt handler?
>> >
>> > I only test with this two interrupt handlers: watchdog and i2c but I
>> > think it will behave the same with others - I can try with other if
>> > you want, any suggestion which? May
> Not using EOImode==1 is definitely an oddity (at least on the host), but
> that doesn't mean it shouldn't work.
>
> The reason the thing is hanging is that although we correctly deactivate
> the interrupt, nothing performs the priority drop. Your write to EOI
> helps in the sense that it guarante
ration.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm64/kernel/machine_kexec.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/arm64/kernel/machine_kexec.c
b/arch/arm64/kernel/machine_kexec.c
index f76ea92..30ad183 100644
--- a/arch/arm64/kernel/machine_kexec.c
+
AM437x SoCs.
Signed-off-by: Suman Anna
Signed-off-by: Roger Quadros
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lee Jones
---
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 383 +
1 file changed, 383 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc
tance specific
data using a device-name based lookup logic. The reset and the L3 external
access are managed by the parent interconnect ti-sysc bus driver so that
PRUSS1 and PRUSS0 can be independently supported.
Signed-off-by: Suman Anna
Signed-off-by: Andrew F. Davis
Signed-off-by: Grzegorz Jas
child
devices (like Interrupt Controller, MDIO node and some syscon nodes) so that
they can be managed by specific platform drivers.
Grzegorz Jaszczyk (1):
dt-bindings: soc: ti: Add TI PRUSS bindings
Suman Anna (5):
soc: ti: pruss: Add a platform driver for PRUSS in TI SoCs
soc: ti: pruss: Add
ation.
Signed-off-by: Andrew F. Davis
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/Kconfig | 2 +-
drivers/soc/ti/pruss.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index 99dbc14..c290343 1
ned-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/Kconfig | 2 +-
drivers/soc/ti/pruss.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index 40d6a22..99dbc14 100644
--- a/drivers/soc/ti/Kconfig
+++ b/d
sting pruss platform driver has been updated to support these new
ICSSG instances through new AM65x specific compatibles. A build dependency
with ARCH_K3 is added to enable building all the existing PRUSS platform
drivers for this ARMv8 platform.
Signed-off-by: Suman Anna
Signed-off-by: Grz
AM335x SoC, and support for
other TI SoCs will be added in subsequent patches.
Signed-off-by: Suman Anna
Signed-off-by: Andrew F. Davis
Signed-off-by: Tero Kristo
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/Kconfig | 11
drivers/soc/ti/Makefile | 1 +
drivers/soc/ti
On Wed, 29 Jul 2020 at 19:34, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The Programmable Real-Time Unit and Industrial Communication Subsystem
> > (PRU-ICSS or simply PRUSS) contains an interrupt control
On Wed, 29 Jul 2020 at 20:43, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > The Programmable Real-Time Unit Subsystem (PRUSS) contains a local
> > interrupt controller (INTC) that can handle various system input events
> > and post interrupts
On Wed, 29 Jul 2020 at 21:23, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > From: David Lechner
> >
> > This implements the irq_get_irqchip_state and irq_set_irqchip_state
> > callbacks for the TI PRUSS INTC driver. The set callback can b
On Wed, 29 Jul 2020 at 21:28, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The K3 AM65x and J721E SoCs have the next generation of the PRU-ICSS IP,
> > commonly called ICSSG. The PRUSS INTC present within the
On Wed, 29 Jul 2020 at 20:48, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The PRUSS INTC has a fixed number of output interrupt lines that are
> > connected to a number of processors or other PRUSS instances
On Fri, 31 Jul 2020 at 16:09, David Lechner wrote:
>
> On 7/31/20 6:48 AM, Grzegorz Jaszczyk wrote:
> > On Wed, 29 Jul 2020 at 19:34, David Lechner wrote:
> >> It is not clear what the meaning of each cell is. Looking at later
> >> patches, it
> >> look
Hi
On Sun, 2 Aug 2020 at 13:57, Pavel Machek wrote:
>
> On Sun 2020-08-02 13:53:30, Pavel Machek wrote:
> > Hi!
> >
> > > A typical usage scenario would be to load the application firmware into
> > > one or
> > > more of the PRU cores, initialize one or more of the peripherals and
> > > perform
On Fri, 31 Jul 2020 at 23:09, Rob Herring wrote:
>
> On Fri, Jul 31, 2020 at 01:48:57PM +0200, Grzegorz Jaszczyk wrote:
> > On Wed, 29 Jul 2020 at 19:34, David Lechner wrote:
> > >
> > > On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > > > From: Suman A
Hi Rob,
On Mon, 17 Aug 2020 at 23:14, Rob Herring wrote:
>
> On Wed, Jul 29, 2020 at 01:02:03PM +0200, Grzegorz Jaszczyk wrote:
> > This patch adds the bindings for the Programmable Real-Time Unit
> > and Industrial Communication Subsystem (PRU-ICSS) present on various
>
Hi All,
The Programmable Real-Time Unit and Industrial Communication Subsystem
(PRU-ICSS or simply PRUSS) on various TI SoCs consists of dual 32-bit
RISC cores (Programmable Real-Time Units, or PRUs) for program execution.
There are 3 foundation component for PRUSS subsystem: the PRUSS platform d
veloped-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 125 -
include/linux/pruss.h | 56 +++
2 files changed, 178 insertions(+), 3 deletions(-)
create mode 100644 include/linux/pruss.h
diff --git
different addresses needs to be published at run-time reusing
the same CTABLE entry.
Co-developed-by: Andrew F. Davis
Signed-off-by: Andrew F. Davis
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Roger Quadros
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz
.
The application nodes themselves should define their own bindings.
Co-developed-by: Tero Kristo
Signed-off-by: Tero Kristo
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
.../bindings/remoteproc/ti,pru-consumer.yaml | 64
: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 35 ++
1 file changed, 35 insertions(+)
diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
index ac13e4452a57..fed7a2051ebf 100644
--- a/drivers/remoteproc
veloped-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
index cc2e585778b1..bfb53967edda 100644
--- a/drivers/remoteproc/pru_rproc.c
+++
tly manipulate the respective memories,
as per their design contract with the associated firmware.
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Andrew F. Davis
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/prus
Hi All,
The Programmable Real-Time Unit and Industrial Communication Subsystem (PRU-ICSS
or simply PRUSS) on various TI SoCs consists of dual 32-bit RISC cores
(Programmable Real-Time Units, or PRUs) for program execution.
There are 3 foundation components for TI PRUSS subsystem: the PRUSS platfo
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
include/linux/pruss_driver.h | 44
1 file changed, 44 insertions(+)
diff --git a/include/linux/pruss_driver.h b/include/linux/pruss_driver.h
index e2d5477225c6..3312281ef4c1 100644
-
le or disable the firmware
running on PRU cores access to any peripherals or memory to achieve
desired functionality. The access is disabled by default on power-up
and on any suspend (context is not maintained).
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grz
upon any failures.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/pruss.c | 41 +
include/linux/pruss.h | 102 +
2 files changed, 143 insertions(+)
diff --git a/drivers
generic
pruss_cfg_update() API function.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
include/linux/pruss.h | 55 +++
1 file changed, 55 insertions(+)
diff --git a/include/linux/pruss.h b/include/linux
: Tero Kristo
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/soc/ti/pruss.c | 58
include/linux/pruss.h| 19
include/linux/pruss_driver.h | 1 +
3 files changed, 78 insertions(+)
diff --git a/drivers
Hi Rob,
On Fri, 18 Dec 2020 at 23:51, Rob Herring wrote:
>
> On Wed, Dec 16, 2020 at 9:55 AM Grzegorz Jaszczyk
> wrote:
> >
> > Hi Rob,
> >
> > On Mon, 14 Dec 2020 at 23:58, Rob Herring wrote:
> > >
> > > On Fri, Dec 11, 2020 at 03:29:29PM
Hi Mathieu
On Mon, 7 Dec 2020 at 18:37, Mathieu Poirier wrote:
[...]
> > +static int pru_handle_intrmap(struct rproc *rproc)
> > +{
> > + struct device *dev = rproc->dev.parent;
> > + struct pru_rproc *pru = rproc->priv;
> > + struct pru_irq_rsc *rsc = pru->pru_interrupt_map;
> > +
://patchwork.kernel.org/project/linux-arm-kernel/cover/20201204201807.14716-1-grzegorz.jaszc...@linaro.org/
Best regards,
Grzegorz
Grzegorz Jaszczyk (1):
remoteproc: pru: Add support for PRU specific interrupt configuration
Suman Anna (5):
dt-bindings: remoteproc: Add binding doc for PRU cores in the PRU
-developed-by: Roger Quadros
Signed-off-by: Roger Quadros
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v3->v4:
- no changes
v2->v3:
- no changes
v1->v2:
- fix below yamllint warnings:
./Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml:37:6:
[warning] wrong in
mware images for each PRU core are retrieved from
DT nodes, and can be adjusted through sysfs if required.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v3->v4:
- No changes.
v2->v3:
- Add Reviewed-by: tag
-
that is set only on K3 SoCs.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v3->v4:
- No changes.
v2->v3:
Address Mathieu comments:
- Change type of some local variable in pru_rproc_memcpy from 'int *&#
Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v3->v4:
- No changes.
v2->v3:
Address Mathieu comments:
- pru_rproc_load_elf_segments(): use filesz instead of (phdr->p_filesz)
and move the check for the !filesz around PT_L
rough .pru_irq_map ELF section is
optional. It varies on specific firmware functionality and therefore
have to be unwinded during PRU stop and performed again during
PRU start.
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v3->v4:
- Use sizeof(unsi
lted
because of a halt instruction, then no change occurs).
Logic for setting the PC and jumping over a halt instruction shall
be added in the future.
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v3->v4:
- No changes.
v2->v3:
Addres
Hi Rob
On Mon, 16 Nov 2020 at 16:28, Rob Herring wrote:
>
> On Sat, 14 Nov 2020 09:46:08 +0100, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The Programmable Real-Time Unit and Industrial Communication Subsystem
> > (PRU-ICSS or simply PRUSS) on various T
Hi Suman,
On Tue, 17 Nov 2020 at 20:41, Suman Anna wrote:
>
> Hi Greg,
>
> I have a few minor comments below..
>
> On 11/14/20 2:46 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The Programmable Real-Time Unit Subsystem (PRUSS) consists of
>
Hi Suman,
On Tue, 17 Nov 2020 at 21:09, Suman Anna wrote:
>
> Hi Greg,
>
> On 11/14/20 2:46 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The K3 AM65x family of SoCs have the next generation of the PRU-ICSS
> > processor subsystem, commonly referr
Hi Suman,
On Tue, 17 Nov 2020 at 21:40, Suman Anna wrote:
>
> Hi Greg,
>
> On 11/14/20 2:46 AM, Grzegorz Jaszczyk wrote:
> > The firmware blob can contain optional ELF sections: .resource_table
> > section and .pru_irq_map one. The second one contains the PRUSS
> >
Hi Suman,
On Thu, 19 Nov 2020 at 00:04, Suman Anna wrote:
>
> Hi Greg,
>
> On 11/18/20 9:27 AM, Grzegorz Jaszczyk wrote:
> > Hi Suman,
> >
> > On Tue, 17 Nov 2020 at 21:40, Suman Anna wrote:
> >>
> >> Hi Greg,
> >>
> >> On 11/1
that is set only on K3 SoCs.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
- Update documentation of pru_rproc_memcpy() according to Suman
comments.
- Update documentation of is_k3 flag.
---
drivers/remoteproc/pru_rproc
rough .pru_irq_map ELF section is
optional. It varies on specific firmware functionality and therefore
have to be unwinded during PRU stop and performed again during
PRU start.
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
Address Suman
mware images for each PRU core are retrieved from
DT nodes, and can be adjusted through sysfs if required.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dr
-developed-by: Roger Quadros
Signed-off-by: Roger Quadros
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
- fix below yamllint warnings:
./Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml:37:6:
[warning] wrong indentation: expected 6 but found 5 (indentat
of pru_rproc_memcpy() function and is_k3 flag.
- Patch #6: No changes.
Best regards,
Grzegorz
Grzegorz Jaszczyk (1):
remoteproc/pru: Add support for PRU specific interrupt configuration
Suman Anna (5):
dt-bindings: remoteproc: Add binding doc for PRU cores in the PRU-ICSS
remoteproc/pru: Add
Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
- Use PRU_IRAM_ADDR_MASK definition instead of raw 0x3.
- Convert 'len' argument from int to size_t type in all *da_to_va.
- Return 0 in case of missing .resource_table for pru_rproc_parse_fw(
lted
because of a halt instruction, then no change occurs).
Logic for setting the PC and jumping over a halt instruction shall
be added in the future.
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 137 +
1 file
t; >>> Hi Grzeg,
> >>>
> >>> I have started to review this set - comments will come over the next few
> >>> days.
> >>>
> >>> See below for a start.
> >>>
> >>> On Thu, Nov 19, 2020 at 03:08:46PM +0100, Gr
Hi Mathieu,
On Thu, 3 Dec 2020 at 19:21, Mathieu Poirier wrote:
>
> On Thu, Nov 19, 2020 at 03:08:48PM +0100, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The remoteproc core creates certain standard debugfs entries,
> > that does not give a whole lot
Hi Mathieu,
On Wed, 2 Dec 2020 at 23:57, Mathieu Poirier wrote:
>
> On Thu, Nov 19, 2020 at 03:08:47PM +0100, Grzegorz Jaszczyk wrote:
> > The firmware blob can contain optional ELF sections: .resource_table
> > section and .pru_irq_map one. The second one contains the P
Hi Mathieu,
On Thu, 3 Dec 2020 at 19:51, Mathieu Poirier wrote:
>
> On Thu, Nov 19, 2020 at 03:08:49PM +0100, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The K3 AM65x family of SoCs have the next generation of the PRU-ICSS
> > processor subsystem, commo
Hi Mathieu,
On Thu, 3 Dec 2020 at 19:53, Mathieu Poirier wrote:
>
> On Thu, Nov 19, 2020 at 03:08:50PM +0100, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The K3 J721E family of SoCs have a revised version of the AM65x ICSSG IP
> > and contains two in
Hi Suman,
On Fri, 4 Dec 2020 at 16:05, Suman Anna wrote:
>
> Hi Greg,
>
> On 11/19/20 8:08 AM, Grzegorz Jaszczyk wrote:
> > Hi All,
> >
> > The Programmable Real-Time Unit and Industrial Communication Subsystem
> > (PRU-ICSS or simply PRUSS) on various TI S
regards,
Grzegorz
Grzegorz Jaszczyk (1):
remoteproc: pru: Add support for PRU specific interrupt configuration
Suman Anna (5):
dt-bindings: remoteproc: Add binding doc for PRU cores in the PRU-ICSS
remoteproc: pru: Add a PRU remoteproc driver
remoteproc: pru: Add pru-specific debugfs support
rough .pru_irq_map ELF section is
optional. It varies on specific firmware functionality and therefore
have to be unwinded during PRU stop and performed again during
PRU start.
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v2-v3:
Address Mathieu com
Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v2-v3:
Address Mathieu comments:
- pru_rproc_load_elf_segments(): use filesz instead of (phdr->p_filesz)
and move the check for the !filesz around PT_LOAD ch
lted
because of a halt instruction, then no change occurs).
Logic for setting the PC and jumping over a halt instruction shall
be added in the future.
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v2->v3:
Address Mathieu comments:
- Remove extra
mware images for each PRU core are retrieved from
DT nodes, and can be adjusted through sysfs if required.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v2->v3:
- Add Reviewed-by: tag
---
drivers/remoteproc/pru_rpr
that is set only on K3 SoCs.
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Mathieu Poirier
---
v2->v3:
Address Mathieu comments:
- Change type of some local variable in pru_rproc_memcpy from 'int *' to
'u32
-developed-by: Roger Quadros
Signed-off-by: Roger Quadros
Signed-off-by: Suman Anna
Signed-off-by: Grzegorz Jaszczyk
---
v2->v3:
- no changes
v1->v2:
- fix below yamllint warnings:
./Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml:37:6:
[warning] wrong indentation: expected 6 but
Hi Rob,
On Mon, 14 Dec 2020 at 23:58, Rob Herring wrote:
>
> On Fri, Dec 11, 2020 at 03:29:29PM +0100, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > Add a YAML binding document for PRU consumers. The binding includes
> > all the common properties tha
Hi All,
The Programmable Real-Time Unit and Industrial Communication Subsystem
(PRU-ICSS or simply PRUSS) on various TI SoCs consists of dual 32-bit
RISC cores (Programmable Real-Time Units, or PRUs) for program execution.
There are 3 foundation components for PRUSS subsystem: the PRUSS platform
veloped-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
- Introduce relevant updates after changing the 'prus' property name to
'ti,prus' in patch #1 as suggested by Rob Herring.
---
drivers/remoteproc/pru_rproc.c | 125 +++
veloped-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
index 568286040bc4..3ffd49f77cfc 100644
--- a/drivers/remoteproc/pru_rproc.c
+++
: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
drivers/remoteproc/pru_rproc.c | 35 ++
1 file changed, 35 insertions(+)
diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
index a37c3f5838ea..4a9c7973bf3a 100644
--- a/drivers/remoteproc
different addresses needs to be published at run-time reusing
the same CTABLE entry.
Co-developed-by: Andrew F. Davis
Signed-off-by: Andrew F. Davis
Co-developed-by: Suman Anna
Signed-off-by: Suman Anna
Signed-off-by: Roger Quadros
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz
.
The application nodes themselves should define their own bindings.
Co-developed-by: Tero Kristo
Signed-off-by: Tero Kristo
Signed-off-by: Suman Anna
Co-developed-by: Grzegorz Jaszczyk
Signed-off-by: Grzegorz Jaszczyk
---
v1->v2:
- Change the 'prus' property name to 'ti,pru
Now after ti,pruss-intc.yaml and ti,pru-rproc.yaml are merged, include
them in proper property and extend the examples section.
At the occasion extend the allowed property list about dma-ranges.
Signed-off-by: Grzegorz Jaszczyk
---
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 76
1 - 100 of 204 matches
Mail list logo
