[PATCH 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC

Kristina [1] i.MX23: http://cache.freescale.com/files/dsp/doc/ref_manual/IMX23RM.pdf i.MX28: http://cache.freescale.com/files/dsp/doc/ref_manual/MCIMX28RM.pdf Kristina Martšenko (4): iio: mxs-lradc: separate touchscreen and buffer virtual channels iio: mxs-lradc: make ADC reads not disable to

[PATCH 3/4] iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions

been tested on i.MX23. Signed-off-by: Kristina Martšenko --- drivers/staging/iio/adc/mxs-lradc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c index 0cf276ff0dc5..5b5cb205b9ed 100644 --- a/drivers/

[PATCH 2/4] iio: mxs-lradc: make ADC reads not disable touchscreen interrupts

. Signed-off-by: Kristina Martšenko --- drivers/staging/iio/adc/mxs-lradc.c | 24 +--- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c index fc65cd311be9..0cf276ff0dc5 100644 --- a

[PATCH 4/4] iio: mxs-lradc: only update the buffer when its conversions have finished

x27;s only push to the buffer when its conversions are ready. Signed-off-by: Kristina Martšenko --- drivers/staging/iio/adc/mxs-lradc.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c index 5b

[PATCH 1/4] iio: mxs-lradc: separate touchscreen and buffer virtual channels

g buffered capture. It has been tested on i.MX28, but not on i.MX23. [1] 06ddd353f5c8 ("iio: mxs: Implement support for touchscreen") [2] dee05308f602 ("Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection") Signed-off-by: Kristina Martšenko --- Note that this

[PATCH] staging: goldfish: switch from spinlock to mutex

Use a mutex instead of a spinlock in goldfish_nand.c, as suggested by the TODO list. Signed-off-by: Kristina Martšenko --- drivers/staging/goldfish/README | 1 - drivers/staging/goldfish/goldfish_nand.c | 15 +++ 2 files changed, 7 insertions(+), 9 deletions(-) diff --git

Re: [PATCH] staging: goldfish: switch from spinlock to mutex

On 03/04/14 11:32, Dan Carpenter wrote: > Sorry for the delay, I'm just catching up with some old emails. No problem. > On Tue, Mar 25, 2014 at 01:45:09AM +0200, Kristina Martšenko wrote: >> Use a mutex instead of a spinlock in goldfish_nand.c, as suggested by >> the TODO

Re: [PATCH] staging: goldfish: switch from spinlock to mutex

On 03/04/14 13:13, Dan Carpenter wrote: > On Thu, Apr 03, 2014 at 01:00:53PM +0300, Kristina Martšenko wrote: >> On 03/04/14 11:32, Dan Carpenter wrote: >>> On Tue, Mar 25, 2014 at 01:45:09AM +0200, Kristina Martšenko wrote: >>>> Use a mutex instead of a spinlock in

Re: [PATCH] staging: goldfish: switch from spinlock to mutex

On 04/04/14 14:04, Dan Carpenter wrote: > On Fri, Apr 04, 2014 at 12:26:27PM +0300, Kristina Martšenko wrote: >> On 03/04/14 13:13, Dan Carpenter wrote: >>> On Thu, Apr 03, 2014 at 01:00:53PM +0300, Kristina Martšenko wrote: >>>> On 03/04/14 11:32, Dan Carpenter wro

Re: [PATCH] staging: goldfish: switch from spinlock to mutex

On 04/04/14 16:30, Dan Carpenter wrote: > On Fri, Apr 04, 2014 at 02:46:14PM +0300, Kristina Martšenko wrote: > >> Yes, I didn't find any interrupt handlers either, which is partially why >> I thought it was (probably) safe. > > What's the other part of why i

Re: [PATCH 1/4] iio: mxs-lradc: separate touchscreen and buffer virtual channels

On 18/01/15 02:19, Marek Vasut wrote: > On Saturday, January 17, 2015 at 01:22:08 AM, Kristina Martšenko wrote: > > Hi! Hi! > Good stuff, thank you! Just minor nitpicks below. > > [...] > >> diff --git a/drivers/staging/iio/adc/mxs-lradc.c >> b/drivers/

Re: [PATCH 2/4] iio: mxs-lradc: make ADC reads not disable touchscreen interrupts

On 18/01/15 02:21, Marek Vasut wrote: > On Saturday, January 17, 2015 at 01:22:09 AM, Kristina Martšenko wrote: >> Reading a channel through sysfs, or starting a buffered capture, will >> currently turn off the touchscreen. This is because the read_raw() and >> buffer pr

Re: [PATCH 3/4] iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions

On 19/01/15 09:57, Marek Vasut wrote: > On Monday, January 19, 2015 at 08:20:31 AM, Juergen Borleis wrote: >> On Saturday 17 January 2015 01:22:10 Kristina Martšenko wrote: >>> Reading a channel through sysfs, or starting a buffered capture, can >>> occasional

Re: [PATCH 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC

On 18/01/15 13:21, Stefan Wahren wrote: > Hi Kristina, Hi Stefan! >> Kristina Martšenko hat am 17. Januar 2015 um >> 01:22 geschrieben: >> These patches fix some issues with using the touchscreen and reading >> other ADC channels at the same time. >> >&

[PATCH v2 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC

hanges from patch #2 Kristina Martšenko (4): iio: mxs-lradc: separate touchscreen and buffer virtual channels iio: mxs-lradc: make ADC reads not disable touchscreen interrupts iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions iio: mxs-lradc: only update the buffer when

[PATCH v2 1/4] iio: mxs-lradc: separate touchscreen and buffer virtual channels

g buffered capture. It has been tested on i.MX28, but not on i.MX23. [1] 06ddd353f5c8 ("iio: mxs: Implement support for touchscreen") [2] dee05308f602 ("Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection") Signed-off-by: Kristina Martšenko --- Note that this

[PATCH v2 2/4] iio: mxs-lradc: make ADC reads not disable touchscreen interrupts

. Signed-off-by: Kristina Martšenko Reviewed-by: Marek Vasut --- drivers/staging/iio/adc/mxs-lradc.c | 20 +++- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c index 4e574b76ead0

[PATCH v2 3/4] iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions

been tested on i.MX23. Signed-off-by: Kristina Martšenko Reviewed-by: Marek Vasut --- drivers/staging/iio/adc/mxs-lradc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c index 653af03bc69d..d2e0

[PATCH v2 4/4] iio: mxs-lradc: only update the buffer when its conversions have finished

x27;s only push to the buffer when its conversions are ready. Signed-off-by: Kristina Martšenko Reviewed-by: Marek Vasut --- drivers/staging/iio/adc/mxs-lradc.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/i

Re: [PATCH v2 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC

On 26/01/15 23:01, Jonathan Cameron wrote: > On 25/01/15 18:47, Marek Vasut wrote: >> On Sunday, January 25, 2015 at 05:28:18 PM, Kristina Martšenko wrote: >>> These patches fix some issues with using the touchscreen and reading >>> other ADC channels at the sam

Anybody working on ced1401?

Hi Alois, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving ced1401 out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want

Anybody working on crystalhd?

Hi Naren, Jarod, Scott, Manu, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving crystalhd out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the dr

Anybody working on frontier?

Hi David, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving frontier out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't wan

Anybody working on keucr?

Hi Al, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving keucr out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want stag

Anybody working on netlogic?

Hi Ganesan and Jayachandran, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving netlogic out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driv

Re: Anybody working on netlogic?

Thanks, > Ganesan > > -Original Message- > From: Kristina Martšenko [mailto:kristina.martse...@gmail.com] > Sent: Wednesday, June 18, 2014 5:17 PM > To: Ganesan Ramalingam; Jayachandran Chandrashekaran Nair > Cc: Greg KH; de...@driverdev.osuosl.org > Subject: Anybody working on

Re: Anybody working on crystalhd?

On 19/06/14 04:03, Greg KH wrote: > On Thu, Jun 19, 2014 at 12:07:38AM +, Naren (Narendra) Sankar wrote: >> We have EOL this part and have not been selling it for a while and there has >> been no new customer interest in a long time. >> >> So I am also ok with this moving off the kernel and be

Anybody working on panel?

Hi Willy, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving panel out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want s

Anybody working on rtl8712?

Hi Larry and Florian, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving rtl8712 out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as w

Anybody working on tidspbridge?

Hi Omar, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving tidspbridge out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't w

Anybody working on winbond?

Hi Pavel, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving winbond out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want

Re: Anybody working on tidspbridge?

On 20/06/14 18:43, Kristina Martšenko wrote: > Hi Omar, > > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that > nobody seems to have worked towards moving tidspbridge out of staging in > over a year. Are there any plans to clean it up and move it

Anybody working on wlags49_h2?

Hi Henk, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving wlags49_h2(5) out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't

Anybody working on bcm?

Hi Stephen, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving bcm out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want s

Re: Anybody working on panel?

On 20/06/14 19:52, Willy Tarreau wrote: > Hi Kristina, > > On Fri, Jun 20, 2014 at 06:35:03PM +0300, Kristina Mart?enko wrote: >> Hi Willy, >> >> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >> nobody seems to have worked towards moving panel out of staging in over >> a

Re: Fwd: Re: Anybody working on rtl8712?

On 20/06/14 23:52, Christian Lamparter wrote: > On Friday, June 20, 2014 09:19:07 PM Xose Vazquez Perez wrote: >> Kristina wrote: >> >>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >>> nobody seems to have worked towards moving rtl8712 out of staging in >>> over a year.

Re: Anybody working on rtl8712?

On 20/06/14 20:15, Larry Finger wrote: > On 06/20/2014 10:40 AM, Kristina Martšenko wrote: >> Hi Larry and Florian, >> >> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >> nobody seems to have worked towards moving rtl8712 out of staging

Re: Anybody working on wlags49_h2?

On 21/06/14 22:46, Greg KH wrote: > On Sat, Jun 21, 2014 at 06:35:41PM +0100, Dave Kilroy wrote: >> On 20/06/2014 17:18, Kristina Martšenko wrote: >>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >>> nobody seems to have worked tow

Anybody working on cxt1e1?

Hi Bob, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving cxt1e1 out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want st

Anybody working on gdm72xx?

Hi Sage, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving gdm72xx out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want

Anybody working on quickstart?

Hi Angelo, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving quickstart out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't

Anybody working on silicom?

Hi Daniel, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving silicom out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't wan

Anybody working on line6?

Hi Markus, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving line6 out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want

Anybody working on phison?

Hi Evan, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving phison out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want s

Anybody working on dgrp or serqt_usb2?

Hi Bill, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving dgrp or serqt_usb2 out of staging in over a year. Are there any plans to clean these drivers up and move them out soon? Because otherwise we're going to have to delete them,

Anybody working on sep?

Hi Mark, I'm helping Greg do a bit of cleanup in the staging tree. I noticed that nobody seems to have worked towards moving sep out of staging in over a year. Are there any plans to clean it up and move it out soon? Because otherwise we're going to have to delete the driver, as we don't want stag

Re: Anybody working on gdm72xx?

On 23/06/14 23:41, Ben Chan wrote: > Hi Kristina and Greg, > > I can help migrate the gdm72xx driver from staging to mainline. I > believe the issues in TODO have been addressed. That's great, thanks! > Is there a migration process that I should follow? I don't think there's anything special yo

Re: Fwd: Re: Anybody working on rtl8712?

On 21/06/14 20:52, Christian Lamparter wrote: > On Saturday, June 21, 2014 06:45:07 PM Kristina Martšenko wrote: >> On 20/06/14 23:52, Christian Lamparter wrote: >>> rtl8192su development is chugging along. It just doesn't take place on >>> driverdev list. The driv

Re: Fwd: Re: Anybody working on rtl8712?

On 21/06/14 21:24, Larry Finger wrote: > On 06/21/2014 12:52 PM, Christian Lamparter wrote: >> I think there's a reason why the development takes so long >> (The RTL8192S* chips have been around since 2008, 2009) >> and why we all have better things to do and write harsh >> responses. As far as I c

Re: Anybody working on dgrp or serqt_usb2?

On 24/06/14 01:08, Bill Pemberton wrote: > On 06/23/2014 04:26 PM, Kristina Martšenko wrote: >> Hi Bill, >> >> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >> nobody seems to have worked towards moving dgrp or serqt_usb2 out of >>

Re: [PATCH] staging: winbond: remove driver

On 27/06/14 04:11, Greg KH wrote: > On Mon, Jun 23, 2014 at 06:41:29PM +0300, Kristina Martšenko wrote: >> The driver hasn't been cleaned up and nobody is working to do so, so >> remove it. >> >> Signed-off-by: Kristina Martšenko >> Cc: Pavel Machek >

Re: Anybody working on cxt1e1?

On 24/06/14 15:44, Bob Beers wrote: > No,I am not able to work on that. It probably should be removed. > Bob Okay then. No one else has shown interest in it either in the past week, so I'll go ahead and remove it. Thanks, Kristina ___ devel mailing list

Re: [Q] Removed cxt1e1 module in staging branch

On 02/07/14 12:41, DaeSeok Youn wrote: > Hi, all. > > I saw your change which removes cxt1e1 in staging tree. > Actually, I have been cleaning up coding style and fixing minor issues > without real cxt1e1 hardware. > > And I am not cleaning up all of files in cxt1e1 but some files already > done

Status of RMI4 drivers?

Hi, I'm going over some "older" drivers in the staging tree and wanted to ask about cptm1217 and ste_rmi4. They've been in staging for three and a half years now, waiting for the upstream Synaptics RMI4 drivers. From what I understand, the RMI4 development is happening in the synaptics-rmi4 branch

Re: Status of RMI4 drivers?

On 06/07/14 21:12, Dmitry Torokhov wrote: > On Sat, Jul 5, 2014 at 8:39 PM, Greg KH wrote: >> On Sat, Jul 05, 2014 at 04:37:37PM +0100, Alan Cox wrote: >>> On Fri, 2014-07-04 at 21:48 +0300, Kristina Martšenko wrote: >>>> Hi, >>>> >>>> I

Re: Anybody working on tidspbridge?

On 29/06/14 19:42, Greg KH wrote: > On Fri, Jun 20, 2014 at 07:05:17PM +0300, Kristina Martšenko wrote: >> On 20/06/14 18:43, Kristina Martšenko wrote: >>> Hi Omar, >>> >>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that >&

Re: Anybody working on ced1401?

Ellero wrote: >>>>> Il 26/06/2014 21:23, Greg KH ha scritto: >>>>>> On Thu, Jun 26, 2014 at 09:36:17AM +0200, Alois Schloegl >>>>>> wrote: >>>>>>> On 2014-06-18 13:33, Kristina Martšenko wrote: >>>>>>>

[PATCH 2/2] ARM: OMAP2+: remove DSP platform device

It was added to support DSP Bridge. Since DSP Bridge was removed, and nothing else is using the platform device, remove it too. Signed-off-by: Kristina Martšenko Cc: Omar Ramirez Luna Cc: Suman Anna Cc: Felipe Contreras --- arch/arm/mach-omap2/Makefile | 4 - arch/arm/mach-omap2

[PATCH] staging: phison: remove driver

The driver hasn't been cleaned up and it doesn't look like anyone is working on it anymore (including the original author). So remove the driver from the kernel. If someone wants to work on cleaning it up and moving it out of staging, this commit can be reverted. Signed-off-by: Kristina

[PATCH] staging: quickstart: remove driver

The driver hasn't been cleaned up and it doesn't look like anyone is working on it anymore (including the original author). So remove the driver from the kernel. If someone wants to work on cleaning it up and moving it out of staging, this commit can be reverted. Signed-off-by: Kristina

Re: Anybody working on sep?

On 23/06/14 23:32, Kristina Martšenko wrote: > Hi Mark, > > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that > nobody seems to have worked towards moving sep out of staging in over a > year. Are there any plans to clean it up and move it out soon? N