This patch adds DTS definition of the imx278 based XEA board.
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- Fix 'memory' node and remove regulators subnode
- Rename 'flash0: s25fl256s0@0' to flash@0
- Add proper compatible for XEA board
---
arch/arm/boot/dts/
Hi Shawn,
> Dear Community,
>
> > This patch adds DTS definition of the imx278 based XEA board.
> >
> > Signed-off-by: Lukasz Majewski
> > ---
> > arch/arm/boot/dts/Makefile | 3 +-
> > arch/arm/boot/dts/imx28-lwe.dtsi | 185
> > +++
Hi Shawn,
> From: Mans Rullgard
>
> Add pinmux setting for USB1 overcurrent on pwm2 pad.
>
Gentle ping on this patch.
> Signed-off-by: Mans Rullgard
> Signed-off-by: Lukasz Majewski
> ---
> Changes for v2:
> - Add S-o-B
> ---
> arch/arm/boot/dts/imx
Dear Community,
> This patch adds DTS definition of the imx278 based XEA board.
>
> Signed-off-by: Lukasz Majewski
> ---
> arch/arm/boot/dts/Makefile | 3 +-
> arch/arm/boot/dts/imx28-lwe.dtsi | 185
> +++ arch/arm/boot/dts/
From: Mans Rullgard
Add pinmux setting for USB1 overcurrent on pwm2 pad.
Signed-off-by: Mans Rullgard
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- Add S-o-B
---
arch/arm/boot/dts/imx28.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx28.dtsi b
Hi Florian,
> On 11/27/2020 4:33 PM, Lukasz Majewski wrote:
> >> So why use DSA at all? What benefit does it bring you? Why not do
> >> the entire switch configuration from within FEC, or a separate
> >> driver very closely related to it?
> >
> > Min
Hi Vladimir,
> On Fri, Nov 27, 2020 at 12:35:49AM +0100, Lukasz Majewski wrote:
> > > > - The question regarding power management - at least for my use
> > > > case there is no need for runtime power management. The L2
> > > > switch shall w
I cannot find such chapter in the official documentation from NXP:
"VFxxx Controller Reference Manual, Rev. 0, 10/2016"
Maybe you have more verbose version? Could you share how the document
is named?
>
>Andrew
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH,
the degree of control you need over the DMA
> channel. If you can reuse the FEC driver, then a DSA driver might
> work. If the coupling it too loose, and you have to take control of
> the DMA, then a pure switchdev driver seems more appropriate.
>
> Andrew
>
Thanks for th
is and statically
> assign VLANs. Frames sent with VLAN 1 are forwarded out port 1. Frames
> sent with VLAN 2 are sent out port 2. You need the port to
> append/strip these VLAN tags for ingress/egress. tag_8021q.c gives you
> some code to help with this. But can you still use the hardware
Hi Vladimir,
> Hi Lukasz,
>
> On Thu, Nov 26, 2020 at 12:24:55AM +0100, Lukasz Majewski wrote:
> > This is the first attempt to add support for L2 switch available on
> > some NXP devices - i.e. iMX287 or VF610. This patch set uses common
> > FEC and DSA code.
> &
Hi Andrew, Florian,
> On Wed, Nov 25, 2020 at 05:30:04PM -0800, Florian Fainelli wrote:
> >
> >
> > On 11/25/2020 4:00 PM, Andrew Lunn wrote:
> > > On Thu, Nov 26, 2020 at 12:24:55AM +0100, Lukasz Majewski wrote:
> > >> This is the first atte
The 'eth_switch' node is now used to enable support for L2 switch.
Moreover, a separate 'switch' node was introduced to keep the code more
clean.
Signed-off-by: Lukasz Majewski
---
arch/arm/boot/dts/imx28-xea.dts | 55 +
1 file changed, 55
.freescale.com/imx/linux-2.6-imx.git
Branch: imx_2.6.35_maintain
SHA1: b3912bb8a4caf3ec50909135e88af959982c43ca
[2] - https://github.com/lmajewski/linux-imx28-l2switch/commits/master
Signed-off-by: Lukasz Majewski
---
drivers/net/ethernet/freescale/fec.h | 39 ++
drivers/net
After this change ECR (control register) defines are moved to fec.h, so
they can be reused by L2 switch code.
Signed-off-by: Lukasz Majewski
---
drivers/net/ethernet/freescale/fec.h | 3 +++
drivers/net/ethernet/freescale/fec_main.c | 3 ---
2 files changed, 3 insertions(+), 3 deletions
s FEC
(fec_main.c).
Signed-off-by: Lukasz Majewski
---
drivers/net/dsa/Kconfig | 11 +
drivers/net/dsa/Makefile| 1 +
drivers/net/dsa/mtip-l2switch.c | 399
drivers/net/dsa/mtip-l2switch.h | 239 +++
4 files changed, 650 inser
o/?l=devicetree&m=160632123203787&w=2
Those patches has been tested (applied) on 4.9.130-cip and v5.9 (vanila
mainline kernel)
Lukasz Majewski (4):
net: fec: Move some defines to ./drivers/net/ethernet/freescale/fec.h
header
net: dsa: Provide DSA driver for NXP's More Than IP L
This patch adds DTS definition of the imx278 based XEA board.
Signed-off-by: Lukasz Majewski
---
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/imx28-lwe.dtsi | 185 +++
arch/arm/boot/dts/imx28-xea.dts | 99 +
3 files changed, 286
The 'eth_switch' name has been misspelled in the imx28.dtsi file,
so this change fixes it.
Signed-off-by: Lukasz Majewski
---
arch/arm/boot/dts/imx28.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.
From: Mans Rullgard
Add pinmux setting for USB1 overcurrent on pwm2 pad.
Signed-off-by: Mans Rullgard
---
arch/arm/boot/dts/imx28.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index 6e7531b64bf7..6d24546f0abe 10
Hi Thomas,
> Lukasz,
>
> On Fri, Oct 30 2020 at 11:02, Lukasz Majewski wrote:
> > I do have a question regarding the Linux time namespaces in respect
> > of adding support for virtualizing the CLOCK_REALTIME.
> >
> > According to patch description [1] and tim
29
[2] - https://www.man7.org/linux/man-pages/man7/time_namespaces.7.html
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-669
on happens on UART lines.
Signed-off-by: Lukasz Majewski
Suggested-by: Robin Murphy
---
Changes for v2:
- Use /delete-property/dma-names; instead of dma-names = "","";
---
arch/arm/boot/dts/vf610-bk4.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts
Hi Robin,
> On 09/10/2019 15:30, Lukasz Majewski wrote:
> > This change disables the DMA support (RX/TX) on the NXP's fsl_lpuart
> > driver - the PIO mode is used instead. This change is necessary for
> > better robustness of BK4's device use cases with many po
on happens on UART lines.
Signed-off-by: Lukasz Majewski
---
arch/arm/boot/dts/vf610-bk4.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-bk4.dts b/arch/arm/boot/dts/vf610-bk4.dts
index 0f3870d3b099..ad20f3442d40 100644
--- a/arch/arm/boot/dts/vf610-bk4.dts
+++
Hi Alexandre,
> On 03/10/2019 16:10:53+0200, Lukasz Majewski wrote:
> > Sorry, but I do see some inconsistency here.
> >
> > The application note [1] says that the correction shall be done in
> > application SW.
> >
> > The rtc-range.c program [2]
Hi Alexandre,
> On 03/10/2019 15:14:34+0200, Lukasz Majewski wrote:
> > Hi Alexandre,
> >
> > > On 03/10/2019 14:21:50+0200, Lukasz Majewski wrote:
> > > > >
> > > > > See the datasheet:
> > > > >
> > >
Hi Alexandre,
> On 03/10/2019 14:21:50+0200, Lukasz Majewski wrote:
> > >
> > > See the datasheet:
> > >
> > > "During any year which is a multiple of 4, the RV-4162 RTC will
> > > automatically insert leap day, February 29. Therefore,
Hi Alexandre,
> Hello,
>
> On 11/09/2019 17:48:03+0200, Lukasz Majewski wrote:
> > This change adds support for 'century bits' on 4162 family of RTC
> > devices (from ST or microcrystal), which allow storing time beyond
> > year 2099.
> >
> > F
Hi Geert,
> Hi Lukasz,
>
> On Tue, Oct 1, 2019 at 11:34 AM Lukasz Majewski wrote:
> > > On Tue, Oct 1, 2019 at 11:07 AM Lukasz Majewski
> > > wrote:
> > > > Call spi_slave_abort() only when the spidev->spi is !NULL and
> &
Hi Geert,
Thank you for a very prompt response.
> Hi Lukasz,
>
> On Tue, Oct 1, 2019 at 11:07 AM Lukasz Majewski wrote:
> > Call spi_slave_abort() only when the spidev->spi is !NULL and the
> > structure hasn't already been kfreed.
> >
> > Reported-by:
Call spi_slave_abort() only when the spidev->spi is !NULL and the
structure hasn't already been kfreed.
Reported-by: kbuild test robot
Reported-by: Julia Lawall
Reported-by: Dan Carpenter
Signed-off-by: Lukasz Majewski
---
This fix applies on:
repo: https://kernel.googlesource.com
Hi Lee,
> On Mon, 30 Sep 2019, Lukasz Majewski wrote:
>
> > Dear Lee,
> >
> > > This patch set provides several enhancements to mc13xxx MFD family
> > > of devices by introducing mc34708 as a separate device.
> > >
> > > This IC ha
t; There shall be no functional changes for devices not supporting this
> feature. However, other devices - like m41t80 - have different
> approaches to handle century information.
Gentle ping on this patch - it has been almost 3 weeks without any
reply ...
Thanks in advance.
>
> Sig
t
>
> drivers/input/touchscreen/mc13783_ts.c | 63 ++---
> drivers/mfd/mc13xxx-core.c | 98
> +- include/linux/mfd/mc34708.h|
> 37 ++ 3 files changed, 185 insertions(+), 13 deletions(-)
> create mode 100644 include/linux/mfd/mc34708.h
Hi Mark, Geert,
> On Thu, Sep 26, 2019 at 04:06:45PM +0200, Lukasz Majewski wrote:
> > > On Thu, Sep 26, 2019 at 2:49 PM Lukasz Majewski
> > > wrote:
>
> > > > The question is if we shall call the spi_slave_abort() when
> > > > cleaning up
Hi Geert,
> Hi Lukasz,
>
> On Thu, Sep 26, 2019 at 2:49 PM Lukasz Majewski wrote:
> > > On Thu, Sep 26, 2019 at 12:14 PM Lukasz Majewski
> > > wrote:
> > > > > Static analysis with Coverity has detected an potential
> >
Hi Geert,
> Hi Lukasz,
>
> On Thu, Sep 26, 2019 at 12:14 PM Lukasz Majewski
> wrote:
> > > Static analysis with Coverity has detected an potential
> > > dereference of a free'd object with commit:
> > >
> > > commit 9f918a728cf86b275
Hi Colin,
> Hi,
>
> Static analysis with Coverity has detected an potential dereference
> of a free'd object with commit:
>
> commit 9f918a728cf86b2757b6a7025e1f46824bfe3155
> Author: Lukasz Majewski
> Date: Wed Sep 25 11:11:42 2019 +0200
>
> spi: Add
Hi Geert,
> Hi Lukasz,
>
> On Thu, Sep 26, 2019 at 3:33 AM Lukasz Majewski wrote:
> > This change is necessary for spidev devices (e.g. /dev/spidev3.0)
> > working in the slave mode (like NXP's dspi driver for Vybrid SoC).
> >
> > When SPI HW works in thi
Hi Mark,
> On Wed, Sep 25, 2019 at 11:11:42AM +0200, Lukasz Majewski wrote:
> > This change is necessary for spidev devices (e.g. /dev/spidev3.0)
> > working in the slave mode (like NXP's dspi driver for Vybrid SoC).
>
> Please do not submit new versions of alrea
dspi_slave_abort() terminates all pending and
ongoing DMA transactions (with sync) and clears internal FIFOs.
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- None
---
drivers/spi/spi-fsl-dspi.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/spi/spi-fsl-dspi.c b
d the system was assessed if it is
possible to continue correct SPI transmission.
This series applies clearly on v5.2 (tag) and current mainline:
SHA1: 351c8a09b00b5c51c8f58b016fffe51f87e2d820
Lukasz Majewski (2):
spi: Add call to spi_slave_abort() function when spidev driver is
released
n SPI lines - the SPI Linux driver needs a chance to recover
from this abnormal situation and prepare itself for next (correct)
transmission.
This change doesn't pose any threat on drivers working in master mode as
spi_slave_abort() function checks if SPI slave mode is supported.
Signed-off-
d the system was assessed if it is
possible to continue correct SPI transmission.
This series applies clearly on v5.2 (tag) and current mainline:
SHA1: 4c07e2ddab5b6b57dbcb09aedbda1f484d5940cc
Lukasz Majewski (2):
spi: Add call to spi_slave_abort() function when spidev driver is
released
n SPI lines - the SPI Linux driver needs a chance to recover
from this abnormal situation and prepare itself for next (correct)
transmission.
This change doesn't pose any threat on drivers working in master mode as
spi_slave_abort() function checks if SPI slave mode is supported.
Signed-off-
dspi_slave_abort() terminates all pending and
ongoing DMA transactions (with sync) and clears internal FIFOs.
Signed-off-by: Lukasz Majewski
---
drivers/spi/spi-fsl-dspi.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/spi/spi-fsl-dspi.c b/drivers/spi/spi-fsl-dspi.c
ike m41t80 - have different approaches
to handle century information.
Signed-off-by: Lukasz Majewski
---
drivers/rtc/rtc-m41t80.c | 56 +++-
1 file changed, 44 insertions(+), 12 deletions(-)
diff --git a/drivers/rtc/rtc-m41t80.c b/drivers/rtc/rtc-m41t
be sampled in a data format compatible to the older chips in order
to keep the API between the mfd and the touchscreen driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v5:
- Remove adc_do_conversion() callbacks from struct mc13xxx_variant
- Remove duplicated
From: Sascha Hauer
The platform data once was optional, make it optional again. This
is a first step towards device tree support for the mc13xxx touchscreen
driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
Acked-by: Dmitry Torokhov
---
Changes for v5:
- None
Changes for
This patch set provides several enhancements to mc13xxx MFD family
of devices by introducing mc34708 as a separate device.
This IC has dedicated pen detection feature, which allows better
touchscreen experience.
This is the fifth version of this code (v5).
Discussion regarding previous versions c
From: Sascha Hauer
The mc34708 has a different bit to enable pen detection. This
adds the driver data and devtype necessary to probe the device
and to distinguish between the mc13783 and the mc34708.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
Acked-by: Dmitry Torokhov
Hi Lee,
> Hi Lee,
>
> > On Thu, 18 Jul 2019, Lukasz Majewski wrote:
> >
> > > From: Sascha Hauer
> > >
> > > The mc34708 has an improved adc. The older variants will always
> > > convert a fixed order of channels. The mc34708 can do up
OR memory shall
have reg=<2> as it is connected to Bus B, CS 0.
Fixes: a67d2c52a82f ("ARM: dts: Add support for Liebherr's BK4 device (vf610
based)")
Suggested-by: Fabio Estevam
Signed-off-by: Lukasz Majewski
Reviewed-by: Fabio Estevam
---
Changes for v3:
- Reorder Signed
OR memory shall
have reg=<2> as it is connected to Bus B, CS 0.
Signed-off-by: Lukasz Majewski
Suggested-by: Fabio Estevam
Fixes: a67d2c52a82f ("ARM: dts: Add support for Liebherr's BK4 device
(vf610 based)")
---
Changes for v2:
- Add proper Suggested-by tag as Fabio was the
Hi Fabio,
> Hi Lukasz,
>
> On Tue, Jul 30, 2019 at 12:53 PM Lukasz Majewski
> wrote:
>
> > Shall I refer to the original commit (which added this DTS)? Or the
> > original issue posted to linux-mtd [1] ?
>
> You can add a Fixes tag like this:
>
> Fixe
Hi Fabio,
> Hi Lukasz,
>
> Subject line could be improved:
>
> ARM: dts: vf610-bk4: Fix qspi node description
>
> On Tue, Jul 30, 2019 at 12:06 PM Lukasz Majewski
> wrote:
> >
> > Before this change the device tree description of qspi node for
>
SPI-NOR memory shall
have reg=<2> as it is connected to Bus B, CS 0.
Signed-off-by: Lukasz Majewski
---
arch/arm/boot/dts/vf610-bk4.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/vf610-bk4.dts b/arch/arm/boot/dts/vf610-bk4.dts
index 3fa0cbe456
Hi Lee,
> On Thu, 18 Jul 2019, Lukasz Majewski wrote:
>
> > From: Sascha Hauer
> >
> > The mc34708 has an improved adc. The older variants will always
> > convert a fixed order of channels. The mc34708 can do up to eight
> > conversions in arbitrary ch
This patch set provides several enhancements to mc13xxx MFD family
of devices by introducing mc34708 as a separate device.
This IC has dedicated pen detection feature, which allows better
touchscreen experience.
This is the fourth version of this code (v4).
Discussion regarding v1 can be found he
be sampled in a data format compatible to the older chips in order
to keep the API between the mfd and the touchscreen driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v4:
- None
Changes for v3:
- None
Changes for v2:
- Change the return code patch when the
From: Sascha Hauer
The mc34708 has a different bit to enable pen detection. This
adds the driver data and devtype necessary to probe the device
and to distinguish between the mc13783 and the mc34708.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
Acked-by: Dmitry Torokhov
From: Sascha Hauer
The platform data once was optional, make it optional again. This
is a first step towards device tree support for the mc13xxx touchscreen
driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
Acked-by: Dmitry Torokhov
---
Changes for v4:
- Add Dmitry's
Hi Dmitry,
> Hi Lukasz,
>
> On Wed, Jul 17, 2019 at 10:17:04AM +0200, Lukasz Majewski wrote:
> > Hi Dmitry,
> >
> > > On Wed, Jul 17, 2019 at 12:19:29AM +0200, Lukasz Majewski wrote:
> > > > From: Sascha Hauer
> > > >
> > >
Hi Dmitry,
> On Wed, Jul 17, 2019 at 12:19:29AM +0200, Lukasz Majewski wrote:
> > From: Sascha Hauer
> >
> > The mc34708 has a different bit to enable pen detection. This
> > adds the driver data and devtype necessary to probe the device
> > and to distin
Hi Dmitry,
> On Wed, Jul 17, 2019 at 12:19:28AM +0200, Lukasz Majewski wrote:
> > From: Sascha Hauer
> >
> > The platform data once was optional, make it optional again. This
> > is a first step towards device tree support for the mc13xxx
> > touchscreen drive
From: Sascha Hauer
The mc34708 has a different bit to enable pen detection. This
adds the driver data and devtype necessary to probe the device
and to distinguish between the mc13783 and the mc34708.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v3:
- Replace
be sampled in a data format compatible to the older chips in order
to keep the API between the mfd and the touchscreen driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v3:
- None
Changes for v2:
- Change the return code patch when the mc13xxx ADC is performing
From: Sascha Hauer
The platform data once was optional, make it optional again. This
is a first step towards device tree support for the mc13xxx touchscreen
driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v3:
- None
Changes for v2:
- None
Changes from the
This patch set provides several enhancements to mc13xxx MFD family
of devices by introducing mc34708 as a separate device.
This IC has dedicated pen detection feature, which allows better
touchscreen experience.
This is the third version of this code (v3).
Discussion regarding v1 can be found her
Hi Dmitry,
> On Mon, Jul 15, 2019 at 10:43:44AM +0200, Lukasz Majewski wrote:
> > Hi Dmitry,
> >
> > Thank you for your reply.
> >
> > > On Fri, Jul 12, 2019 at 12:23:45AM +0200, Lukasz Majewski wrote:
> > > > From: Sascha Hauer
> > >
Hi Dmitry,
> Hi Lukasz,
>
> On Fri, Jul 12, 2019 at 12:23:46AM +0200, Lukasz Majewski wrote:
> > From: Sascha Hauer
> >
> > The mc34708 has a different bit to enable pen detection. This
> > adds the driver data and devtype necessary to probe the device
&
Hi Dmitry,
Thank you for your reply.
> On Fri, Jul 12, 2019 at 12:23:45AM +0200, Lukasz Majewski wrote:
> > From: Sascha Hauer
> >
> > The platform data once was optional, make it optional again. This
> > is a first step towards device tree support for the mc1
From: Sascha Hauer
The platform data once was optional, make it optional again. This
is a first step towards device tree support for the mc13xxx touchscreen
driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- None
Changes from the original patch:
- Commit
be sampled in a data format compatible to the older chips in order
to keep the API between the mfd and the touchscreen driver.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- Change the return code patch when the mc13xxx ADC is performing conversion
- Introduce
From: Sascha Hauer
The mc34708 has a different bit to enable pen detection. This
adds the driver data and devtype necessary to probe the device
and to distinguish between the mc13783 and the mc34708.
Signed-off-by: Sascha Hauer
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- Change
This patch set provides several enhancements to mc13xxx MFD family
of devices by introducing mc34708 as a separate device.
This IC has dedicated pen detection feature, which allows better
touchscreen experience.
This is the seconf version of this code (v2).
Discussion regarding v1 can be found he
On Sun, 5 May 2019 18:10:54 +0400
Stepan Golosunov wrote:
> 02.05.2019 в 15:04:18 + Joseph Myers написал:
> > On Tue, 30 Apr 2019, Lukasz Majewski wrote:
> >
> > > - The need for explicit clearing padding when calling syscalls
> > > (as to be better safe
Hi Stepan,
> 27.04.2019 в 00:46:53 +0200 Lukasz Majewski написал:
> > Hi Arnd,
> >
> > > As Stepan Golosunov points out, we made a small mistake in the
> > > get_timespec64() function in the kernel. It was originally added
> > > under the assumption t
ove any #ifdef CONFIG_64BIT_TIME completely.
>
> Link:
> https://lore.kernel.org/lkml/20190422090710.bmxdhhankurha...@sghpc.golosunov.pp.ru/
> Cc: Lukasz Majewski Cc: Stepan Golosunov
> Signed-off-by: Arnd Bergmann
> ---
> Please apply this one as a bugfix for 5.1
> ---
&g
Hi Arnd and Stepan,
> On Mon, Apr 22, 2019 at 11:07 AM Stepan Golosunov
> wrote:
> > 20.04.2019 в 13:21:12 +0200 Lukasz Majewski написал:
> > Is it? The kernel (5.1-rc6) code looks to me like
> >
> > /* Zero out the padding for 32 bit systems or in compat
Hi Stepan,
> 15.04.2019 в 00:08:38 +0200 Lukasz Majewski написал:
> > +# if defined __NR_clock_settime64
> > + /* Make sure that passed __timespec64 struct pad is 0. */
> > + struct __timespec64 ts = *tp;
> > + ts.tv_pad = 0;
> > + return INLINE_SYSCALL_CAL
3xx/vision_ep9307.c | 4 ++--
> 14 files changed, 19 insertions(+), 19 deletions(-)
> rename arch/arm/mach-ep93xx/{include/mach => }/gpio-ep93xx.h (100%)
> rename arch/arm/mach-ep93xx/{include/mach => }/hardware.h (96%)
> rename arch/arm/mach-ep93xx/{include/mach =>
This commit adds support for KOE's 5.7" display.
Signed-off-by: Lukasz Majewski
Reviewed-by: Rob Herring
---
Previous discussion (and Rob's Reviewed-by) about this patch
https://patchwork.kernel.org/patch/10339595/
It must have been lost during the development process, so
I d
Hi Arnd,
> On Thu, Mar 7, 2019 at 8:53 AM Lukasz Majewski wrote:
> >
> > Hi Zack,
> >
> > > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski
> > > wrote:
> > > > From other discussion [4] - regarding the following system
> > >
Hi Zack,
> On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote:
> > From other discussion [4] - regarding the following system calls:
> > time, stime, gettimeofday, settimeofday, adjtimex, nanosleep,
> > alarm, getitimer, setitimer, select, utime, utimes, futimesat, a
Hi Arnd,
> On Tue, Mar 5, 2019 at 4:24 PM Lukasz Majewski wrote:
> >
> > Dear Arnd,
> >
> > In your "playground" repository [1] (branch: y2038), the time
> > functions (stime, settimeofday, etc) are not converted in Linux to
> > be Y
rnel/git/arnd/playground.git/tree/kernel/time/time.c?h=y2038
[2] - git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
[3] -
https://elixir.bootlin.com/linux/v2.6.32/source/arch/arm/include/asm/unistd.h#L419
[4] - https://lists.linaro.org/pipermail/y2038/2017-November/002387.html
s, Inc.
> > --
> > 2.7.4
>
>
>
> Renesas Electronics Europe GmbH,Geschaeftsfuehrer/President : Michael
> Hannawald, Sitz der Gesellschaft/Registered office: Duesseldorf,
> Arcadiastrasse 10, 40472 Duesseldorf,
> Germany,Handelsregister/Commercial Register:
set a subset of control fields in
configuration registers (CTAR0, PUSHR).
For testing the spidev_test program has been used.
Test script for this patch can be found here:
https://github.com/lmajewski/tests-spi/blob/master/tests/spi/spi_tests.sh
Signed-off-by: Lukasz Majewski
---
Changes f
Hi Mark,
> On Mon, Feb 04, 2019 at 01:52:42PM +0100, Lukasz Majewski wrote:
> > > On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
>
> > > You've been sending ARM: patches to me (the SPI maintainer) and
> > > one of the DT maintainers.
Hi Mark,
> On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
>
> > Is there any interest in adding new code (or fixes) to VF610 ?
>
> You've been sending ARM: patches to me (the SPI maintainer) and one of
> the DT maintainers.
> You need to send
tests/spi/spi_tests.sh
>
> Signed-off-by: Lukasz Majewski
> ---
> Changes for v5:
>
> - Rebase to v5.0-rc1 (no code changes needed)
Is there any interest in adding new code (or fixes) to VF610 ?
The first version of this patch was posted more than 4 months ago with
no feedback on
30.8-142.3
> > arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> > prerequisite 'spi_bus_bridge'
> >
> >
> > Caused by commit
> >
> > cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading
> > ID code from MVB
Hi Frieder,
> Hi Lukasz,
>
> On 09.01.19 15:56, Lukasz Majewski wrote:
> > Hi Schrempf,
> >
> >> On 08.01.19 10:24, Yogesh Narayan Gaur wrote:
> >>> - Add driver for NXP FlexSPI host controller
> >>>
> >>>FlexSPI is a fl
t; > arch/arm64/configs/defconfig |1 +
> > drivers/spi/Kconfig | 10 +
> > drivers/spi/Makefile |1 +
> > drivers/spi/spi-nxp-fspi.c| 1095
> > + 8 files chan
set a subset of control fields in
configuration registers (CTAR0, PUSHR).
For testing the spidev_test program has been used.
Test script for this patch can be found here:
https://github.com/lmajewski/tests-spi/blob/master/tests/spi/spi_tests.sh
Signed-off-by: Lukasz Majewski
---
Changes f
Hi Fabio,
> Hi Fabio,
>
> > Hi Lukasz,
> >
> > On Thu, Dec 6, 2018 at 11:08 AM Lukasz Majewski
> > wrote:
> > > I will check this latter this week...
> >
> > Reading the spi dt-binding it states that the spi slave node is
> > opti
set a subset of control fields in
configuration registers (CTAR0, PUSHR).
For testing the spidev_test program has been used.
Test script for this patch can be found here:
https://github.com/lmajewski/tests-spi/blob/master/tests/spi/spi_tests.sh
Signed-off-by: Lukasz Majewski
---
Changes f
The procedure to read this ID value is as follows:
rmmod spi_fsl_dspi
insmod spi-gpio.ko
echo 504 > /sys/class/gpio/export
cat /sys/class/gpio/gpio504/value
...
echo 511 > /sys/class/gpio/export
cat /sys/class/gpio/gpio511/value
rmmod spi-gpio.ko
insmod spi_fsl_dspi
Signed-off-by:
1 - 100 of 882 matches
Mail list logo
