On 27/05/20 8:45 pm, Jan Kiszka wrote:
On 27.05.20 16:55, Nikhil Devshatwar wrote:
On 27/05/20 8:18 pm, Jan Kiszka wrote:
On 27.05.20 16:16, Nikhil Devshatwar wrote:
On 27/05/20 7:38 pm, Jan Kiszka wrote:
On 27.05.20 15:53, Nikhil Devshatwar wrote:
On 27/05/20 7:18 pm, Jan Kiszka
On 26.05.20 15:24, Marco Solieri wrote:
> On Mon, May 04, 2020 at 08:54:32PM +0200, Jan Kiszka wrote:
>> On 22.04.20 10:51, Jan Kiszka wrote:
>>> On 22.04.20 09:22, Marco Solieri wrote:
On Wed, Apr 22, 2020 at 08:42:32AM +0200, Jan Kiszka wrote:
> On 27.03.19 13:18, Marco Solieri wrote:
On 27.05.20 16:55, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 8:18 pm, Jan Kiszka wrote:
>> On 27.05.20 16:16, Nikhil Devshatwar wrote:
>>>
>>>
>>> On 27/05/20 7:38 pm, Jan Kiszka wrote:
On 27.05.20 15:53, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 16:32, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 7:52 pm, Jan Kiszka wrote:
>> On 27.05.20 16:09, Nikhil Devshatwar wrote:
>>>
>>>
>>> On 27/05/20 6:55 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> Add a virtual PCI
On 27/05/20 8:18 pm, Jan Kiszka wrote:
On 27.05.20 16:16, Nikhil Devshatwar wrote:
On 27/05/20 7:38 pm, Jan Kiszka wrote:
On 27.05.20 15:53, Nikhil Devshatwar wrote:
On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 15:28, Nikhil Devshatwar wrote:
On 27/05/20 6:41 pm, Jan Kiszka
On 27.05.20 16:16, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 7:38 pm, Jan Kiszka wrote:
>> On 27.05.20 15:53, Nikhil Devshatwar wrote:
>>>
>>>
>>> On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 15:28, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 16:09, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 6:55 pm, Jan Kiszka wrote:
>> On 27.05.20 14:32, nikhil...@ti.com wrote:
>>> From: Nikhil Devshatwar
>>>
>>> Add a virtual PCI device with IVSHMEM type (id = 1)
>>> Create IVSHMEM regions for 2 peer communication
>>> Enable the
On 27/05/20 7:38 pm, Jan Kiszka wrote:
On 27.05.20 15:53, Nikhil Devshatwar wrote:
On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 15:28, Nikhil Devshatwar wrote:
On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
Number of
On 27/05/20 6:55 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
Add a virtual PCI device with IVSHMEM type (id = 1)
Create IVSHMEM regions for 2 peer communication
Enable the vpci_irq for doorbell interrupt
This allows to run the ivshmem-demo
On 27.05.20 15:53, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 7:18 pm, Jan Kiszka wrote:
>> On 27.05.20 15:28, Nikhil Devshatwar wrote:
>>>
>>>
>>> On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> Number of peers
On 27.05.20 15:46, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 7:01 pm, Jan Kiszka wrote:
>> On 27.05.20 14:23, nikhil...@ti.com wrote:
>>> From: Nikhil Devshatwar
>>>
>>> PCI kernel framework requires that all the instances in the
>>> device tree either specify the PCIe domain or none does.
>>>
On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 15:28, Nikhil Devshatwar wrote:
On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
Number of peers available on a platform is different.
Do not hard code the target peer_id used
On 27.05.20 15:28, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 6:41 pm, Jan Kiszka wrote:
>> On 27.05.20 14:32, nikhil...@ti.com wrote:
>>> From: Nikhil Devshatwar
>>>
>>> Number of peers available on a platform is different.
>>> Do not hard code the target peer_id used for interrupt.
>>> Parse
On 27/05/20 7:01 pm, Jan Kiszka wrote:
On 27.05.20 14:23, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
PCI kernel framework requires that all the instances in the
device tree either specify the PCIe domain or none does.
Currently, Jailhouse dynamic overlay describes the PCI domain
On 27.05.20 15:31, Nikhil Devshatwar wrote:
>
>
> On 27/05/20 6:58 pm, Jan Kiszka wrote:
>> On 27.05.20 14:32, nikhil...@ti.com wrote:
>>> From: Nikhil Devshatwar
>>>
>>> Current IVSHMEM regions are described to be used for ivshmem-net
>>> driver. For standalone ivshmem communication, these
On 27.05.20 14:23, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> PCI kernel framework requires that all the instances in the
> device tree either specify the PCIe domain or none does.
>
> Currently, Jailhouse dynamic overlay describes the PCI domain
> which causes problems because root
On 27/05/20 6:58 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
Current IVSHMEM regions are described to be used for ivshmem-net
driver. For standalone ivshmem communication, these regions need to
be added explicitly instead of using the macro.
On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar
Number of peers available on a platform is different.
Do not hard code the target peer_id used for interrupt.
Parse this from the command line argument.
This de-couples the dependency
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> Current IVSHMEM regions are described to be used for ivshmem-net
> driver. For standalone ivshmem communication, these regions need to
> be added explicitly instead of using the macro.
>
> Add regions for a 2 peer IVSHMEM
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> ivshmem protocol does not describe a fixed size for the
> rw, input and output regions. For each platform, the uio
> driver will populate this information in the sysfw.
>
> Extract the size from sysfs maps entries and use
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> Add a virtual PCI device with IVSHMEM type (id = 1)
> Create IVSHMEM regions for 2 peer communication
> Enable the vpci_irq for doorbell interrupt
>
> This allows to run the ivshmem-demo baremetal inmate
> inside this
On 27.05.20 14:32, nikhil...@ti.com wrote:
> From: Nikhil Devshatwar
>
> Number of peers available on a platform is different.
> Do not hard code the target peer_id used for interrupt.
> Parse this from the command line argument.
>
> This de-couples the dependency between number of peers.
>
From: Nikhil Devshatwar
ivshmem protocol does not describe a fixed size for the
rw, input and output regions. For each platform, the uio
driver will populate this information in the sysfw.
Extract the size from sysfs maps entries and use it for
mapping different regions.
This will make the demo
From: Nikhil Devshatwar
Number of peers available on a platform is different.
Do not hard code the target peer_id used for interrupt.
Parse this from the command line argument.
This de-couples the dependency between number of peers.
ivshmem-demo can be run to communicate with desired target
From: Nikhil Devshatwar
This series adds ivshmem support for the k3-j721e-evm platform.
Modify the inmate-demo cell such that baremetal ivshmem demo
can be run on it
Also, generalize the current linux application to be usable
on other platforms with different configuration for ivshmem.
Nikhil
From: Nikhil Devshatwar
Current IVSHMEM regions are described to be used for ivshmem-net
driver. For standalone ivshmem communication, these regions need to
be added explicitly instead of using the macro.
Add regions for a 2 peer IVSHMEM communication
(0 = root cell, 1 = baremetal /
From: Nikhil Devshatwar
Add a virtual PCI device with IVSHMEM type (id = 1)
Create IVSHMEM regions for 2 peer communication
Enable the vpci_irq for doorbell interrupt
This allows to run the ivshmem-demo baremetal inmate
inside this cell.
Signed-off-by: Nikhil Devshatwar
---
From: Kishon Vijay Abraham I
Define the jailhouse_memory region for GIC ITS so that PCIe master
(RC mode) can write to GIC ITS for raising MSI/MSI-X interrupt.
This fixes the crash when GIC ITS is being used by root cell.
Signed-off-by: Kishon Vijay Abraham I
Signed-off-by: Nikhil Devshatwar
From: Nikhil Devshatwar
In kernel 5.4, support for following is not available:
* D5520 decoder
* GPU virtualization
* DSS display virtualization
Remove these from cell config.
Without these, when root cell tries to access these regions,
it causes failures due to mismatch in memory mapping.
e.g.
From: Nikhil Devshatwar
PCI kernel framework requires that all the instances in the
device tree either specify the PCIe domain or none does.
Currently, Jailhouse dynamic overlay describes the PCI domain
which causes problems because root cell DTS does not describe
this.
Fix this by not
From: Nikhil Devshatwar
This series fixes few issues with the jailhouse cell
config files. It adds required memory regions for
fixing crashes due to accessing few devices.
Also, remove some obsolete device partitioning
which is no longer supported in the 5.4 kernel.
We will add only when the
From: Nikhil Devshatwar
Define the jailhouse_memory regions for the USB toplevel MMRs
This fixes the crash when root cell or inmate cell tries to
access the USB devices.
Signed-off-by: Nikhil Devshatwar
---
configs/arm64/k3-j721e-evm-linux-demo.c | 16 +++-
From: Nikhil Devshatwar
Add a pinmux DT node for main_uart1.
Describe the pinctrl default state for main_uart1 node.
Signed-off-by: Nikhil Devshatwar
---
configs/arm64/dts/inmate-k3-j721e-evm.dts | 12
1 file changed, 12 insertions(+)
diff --git
33 matches
Mail list logo
