This patch is based on one that was submitted by Wolfgang Netbal back in Feb
2016 but a formal patch was never submitted.
I added a couple small changes (style errors and imx7 define) and tested on a
imx7d board. One quick note, the IMX7D define may not really be needed since
most imx7 uarts look
If the device name from the device tree starts with a forward slash (/) the
rtdm device stores it in the registry including the forward slash. When we
go to use that device and do the registry lookup we use a relative path from
/dev/rtdm which doesn't contain the forward slash and fails to find a
Some SOCs will have two GPIO chips that require two independent drivers. In my
case I was working with the Zynq SOC and needed a driver for the gpios on the
FPGA and a driver for the gpios available on the ARM core. This change allows
for two rt gpio drivers to be built and loaded at the same
---
kernel/drivers/gpio/Kconfig | 10 +-
kernel/drivers/gpio/Makefile | 3 ++-
kernel/drivers/gpio/gpio-xilinx.c | 40 +++
3 files changed, 51 insertions(+), 2 deletions(-)
create mode 100644 kernel/drivers/gpio/gpio-xilinx.c
diff --git
On 02/01/2018 05:43 PM, Jan Kiszka wrote:
> Hi,
>
> it seems those functions above force the caller always to secondary mode
> (ok, panic is not an issue). Intentionally? To avoid using the wrapped
> versions which may trigger one of the calls again? Or could we also call
> the RT versions, at
Hi,
it seems those functions above force the caller always to secondary mode
(ok, panic is not an issue). Intentionally? To avoid using the wrapped
versions which may trigger one of the calls again? Or could we also call
the RT versions, at least after init_done?
Jan
--
Siemens AG, Corporate
On 2018-01-30 10:58, Philippe Gerum wrote:
> On 01/30/2018 07:59 AM, Jan Kiszka wrote:
>> On 2018-01-30 01:26, Joonyoung Shim wrote:
>>> Sometimes the kernel lockup occurs with "rtifconfig rteth0 down" command
>>> execution on TDMA slave.
>>>
>>> [525182.648366] INFO: rcu_sched detected stalls on
Makes sense, after the fact I realized this would diverge from the
mainline structs. Will fix up and update.
On Thu, Feb 1, 2018 at 5:02 AM, Philippe Gerum wrote:
> On 01/31/2018 03:28 AM, Greg Gallagher wrote:
>> This patch is based on one that was submitted by Wolfgang
Yep, sorry I thought I removed that. Will update
On Thu, Feb 1, 2018 at 5:29 AM, Philippe Gerum wrote:
> On 01/31/2018 03:36 AM, Greg Gallagher wrote:
>> If the device name from the device tree starts with a forward slash (/) the
>> rtdm device stores it in the registry
Yes, will fix that
On Thu, Feb 1, 2018 at 5:30 AM, Philippe Gerum wrote:
> On 01/31/2018 03:36 AM, Greg Gallagher wrote:
>> Some SOCs will have two GPIO chips that require two independent drivers. In
>> my
>> case I was working with the Zynq SOC and needed a driver for the
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> Some SOCs will have two GPIO chips that require two independent drivers. In
> my
> case I was working with the Zynq SOC and needed a driver for the gpios on the
> FPGA and a driver for the gpios available on the ARM core. This change allows
> for
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> If the device name from the device tree starts with a forward slash (/) the
> rtdm device stores it in the registry including the forward slash. When we
> go to use that device and do the registry lookup we use a relative path from
> /dev/rtdm which
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> ---
> kernel/drivers/gpio/Kconfig | 10 +-
> kernel/drivers/gpio/Makefile | 3 ++-
> kernel/drivers/gpio/gpio-xilinx.c | 40
> +++
> 3 files changed, 51 insertions(+), 2 deletions(-)
[snip]
On 01/31/2018 03:28 AM, Greg Gallagher wrote:
> This patch is based on one that was submitted by Wolfgang Netbal back in Feb
> 2016 but a formal patch was never submitted.
> I added a couple small changes (style errors and imx7 define) and tested on a
> imx7d board. One quick note, the IMX7D
14 matches
Mail list logo