Re: [PATCH] net: rfkill-regulator: Add devicetree support.

Am 10.02.2014 um 09:27 schrieb Johannes Berg: > On Fri, 2014-02-07 at 20:48 +0100, Marek Belisko wrote: > >> +#define RFKILL_TYPE_ALL (0) >> +#define RFKILL_TYPE_WLAN(1) >> +#define RFKILL_TYPE_BLUETOOTH (2) >> +#define RFKILL_TYPE_UWB (3) >> +#define

Re: [PATCH] net: rfkill-regulator: Add devicetree support.

Am 10.02.2014 um 09:27 schrieb Johannes Berg: On Fri, 2014-02-07 at 20:48 +0100, Marek Belisko wrote: +#define RFKILL_TYPE_ALL (0) +#define RFKILL_TYPE_WLAN(1) +#define RFKILL_TYPE_BLUETOOTH (2) +#define RFKILL_TYPE_UWB (3) +#define RFKILL_TYPE_WIMAX

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 18.12.2013 um 18:49 schrieb Dan Williams: > On Wed, 2013-12-18 at 14:16 +0100, Dr. H. Nikolaus Schaller wrote: >> Hi Dan, >> >> Am 17.12.2013 um 23:27 schrieb Dan Williams: >> >>> On Tue, 2013-12-17 at 20:56 +0100, Dr. H. Nikolaus Schall

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 17.12.2013 um 23:27 schrieb Dan Williams: > On Tue, 2013-12-17 at 20:56 +0100, Dr. H. Nikolaus Schaller wrote: >> Hi Dan, >> >> Am 16.12.2013 um 20:40 schrieb Dan Williams: >> >>> On Fri, 2013-12-13 at 15:43 +0100, Dr. H. Nikolaus Schaller wrote:

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 17.12.2013 um 23:27 schrieb Dan Williams: On Tue, 2013-12-17 at 20:56 +0100, Dr. H. Nikolaus Schaller wrote: Hi Dan, Am 16.12.2013 um 20:40 schrieb Dan Williams: On Fri, 2013-12-13 at 15:43 +0100, Dr. H. Nikolaus Schaller wrote: Hi, Am 02.10.2013 um 09:00 schrieb Dr. H

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 18.12.2013 um 18:49 schrieb Dan Williams: On Wed, 2013-12-18 at 14:16 +0100, Dr. H. Nikolaus Schaller wrote: Hi Dan, Am 17.12.2013 um 23:27 schrieb Dan Williams: On Tue, 2013-12-17 at 20:56 +0100, Dr. H. Nikolaus Schaller wrote: Hi Dan, Am 16.12.2013 um 20:40 schrieb Dan

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 16.12.2013 um 20:40 schrieb Dan Williams: > On Fri, 2013-12-13 at 15:43 +0100, Dr. H. Nikolaus Schaller wrote: >> Hi, >> >> Am 02.10.2013 um 09:00 schrieb Dr. H. Nikolaus Schaller: >> >>> Hi Jan, >>> >>> we are using a GT

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Dan, Am 16.12.2013 um 20:40 schrieb Dan Williams: On Fri, 2013-12-13 at 15:43 +0100, Dr. H. Nikolaus Schaller wrote: Hi, Am 02.10.2013 um 09:00 schrieb Dr. H. Nikolaus Schaller: Hi Jan, we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an issue that under

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi, Am 02.10.2013 um 09:00 schrieb Dr. H. Nikolaus Schaller: > Hi Jan, > > we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an > issue that under some conditions the modem sends a packed wIndex over USB > that is rejected by the hso driver making trou

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi, Am 02.10.2013 um 09:00 schrieb Dr. H. Nikolaus Schaller: Hi Jan, we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an issue that under some conditions the modem sends a packed wIndex over USB that is rejected by the hso driver making troubles afterwards

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Hi Tomi, Am 18.11.2013 um 14:29 schrieb Tomi Valkeinen: > On 2013-11-11 16:30, Dr. H. Nikolaus Schaller wrote: > >> Maybe it looks as if it is an unsolvable problem. The OPA works only if >> acbias >> and bypass are enabled, but is not allowed to tell that it i

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Hi Tomi, Am 18.11.2013 um 14:29 schrieb Tomi Valkeinen: On 2013-11-11 16:30, Dr. H. Nikolaus Schaller wrote: Maybe it looks as if it is an unsolvable problem. The OPA works only if acbias and bypass are enabled, but is not allowed to tell that it is there. That's why the board file

Re: [PATCH 3/3] misc: bmp085: Add missing platform data.

Am 15.11.2013 um 14:58 schrieb Arnd Bergmann: > On Thursday 14 November 2013, Marek Belisko wrote: >> DT bindings contains more parameters to set so add them to platform data also >> to have possibility to use on arch where DT isn't available yet. >> >> Signed-off-by: Marek Belisko > > Can

Re: [PATCH 3/3] misc: bmp085: Add missing platform data.

Am 15.11.2013 um 14:58 schrieb Arnd Bergmann: On Thursday 14 November 2013, Marek Belisko wrote: DT bindings contains more parameters to set so add them to platform data also to have possibility to use on arch where DT isn't available yet. Signed-off-by: Marek Belisko ma...@goldelico.com

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Am 11.11.2013 um 15:13 schrieb Tomi Valkeinen: > On 2013-11-11 15:57, Dr. H. Nikolaus Schaller wrote: >> Hi Tomi, >> >> Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: >> >>> Hi, >>> >>> On 2013-11-05 09:24, Belisko Marek wrote: >>&

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Am 11.11.2013 um 15:13 schrieb Tomi Valkeinen: > On 2013-11-11 15:57, Dr. H. Nikolaus Schaller wrote: >> Hi Tomi, >> >> Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: >> >>> Hi, >>> >>> On 2013-11-05 09:24, Belisko Marek wrote: >>&

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Hi Tomi, Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: > Hi, > > On 2013-11-05 09:24, Belisko Marek wrote: >> Hi, >> >> ping. >> >> On Mon, Oct 14, 2013 at 11:02 PM, Marek Belisko wrote: >>> This patches is adding bypass and acbias functionality to omapdss venc >>> driver. >>> In first

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Hi Tomi, Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: Hi, On 2013-11-05 09:24, Belisko Marek wrote: Hi, ping. On Mon, Oct 14, 2013 at 11:02 PM, Marek Belisko ma...@goldelico.com wrote: This patches is adding bypass and acbias functionality to omapdss venc driver. In first patch

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Am 11.11.2013 um 15:13 schrieb Tomi Valkeinen: On 2013-11-11 15:57, Dr. H. Nikolaus Schaller wrote: Hi Tomi, Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: Hi, On 2013-11-05 09:24, Belisko Marek wrote: Hi, ping. On Mon, Oct 14, 2013 at 11:02 PM, Marek Belisko ma

Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias.

Am 11.11.2013 um 15:13 schrieb Tomi Valkeinen: On 2013-11-11 15:57, Dr. H. Nikolaus Schaller wrote: Hi Tomi, Am 11.11.2013 um 14:29 schrieb Tomi Valkeinen: Hi, On 2013-11-05 09:24, Belisko Marek wrote: Hi, ping. On Mon, Oct 14, 2013 at 11:02 PM, Marek Belisko ma

Re: [Patch 1/1]: libertas/sdio: fix releasing memory twice.

Hi Dan, Am 12.10.2013 um 21:58 schrieb Dan Williams: > On Sat, 2013-10-12 at 18:02 +0200, Dr. H. Nikolaus Schaller wrote: >> While upgrading the GTA04 kernel to 3.12-rc4 we came across >> an issue with libertas/sdio referencing stale memory on ifconfig up >> when trying

Re: [Patch 1/1]: libertas/sdio: fix releasing memory twice.

Hi Dan, Am 12.10.2013 um 21:58 schrieb Dan Williams: On Sat, 2013-10-12 at 18:02 +0200, Dr. H. Nikolaus Schaller wrote: While upgrading the GTA04 kernel to 3.12-rc4 we came across an issue with libertas/sdio referencing stale memory on ifconfig up when trying to load the firmware

[Patch 1/1]: libertas/sdio: fix releasing memory twice.

While upgrading the GTA04 kernel to 3.12-rc4 we came across an issue with libertas/sdio referencing stale memory on ifconfig up when trying to load the firmware (for a second time). I am not at all sure if the patch is how it should be done and the right location, but it appears to work for us

[Patch 1/1]: libertas/sdio: fix releasing memory twice.

While upgrading the GTA04 kernel to 3.12-rc4 we came across an issue with libertas/sdio referencing stale memory on ifconfig up when trying to load the firmware (for a second time). I am not at all sure if the patch is how it should be done and the right location, but it appears to work for us

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 11.10.2013 um 12:09 schrieb Tomi Valkeinen: > On 11/10/13 12:50, Dr. H. Nikolaus Schaller wrote: > >> Hm. Is this a SPI or does it just look like one? Or is it some - otherwise >> unknown - "3 wire serial interface". Or is it a "3(+1) GPIO slave devi

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi all, Am 11.10.2013 um 11:06 schrieb Lars-Peter Clausen: > On 10/11/2013 10:59 AM, Belisko Marek wrote: >> Hi Tomi, >> >> On Fri, Oct 11, 2013 at 10:17 AM, Tomi Valkeinen >> wrote: >>> On 11/10/13 10:42, Dr. H. Nikolaus Schaller wrote: >>>

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Lars-Peter, ah, I didn't see your mail while writing mine - so some overlap. Am 11.10.2013 um 09:08 schrieb Lars-Peter Clausen: > On 10/11/2013 06:41 AM, Tomi Valkeinen wrote: >> On 10/10/13 21:58, Lars-Peter Clausen wrote: >> >>> According to the datasheet the the panel as a dedicated dout

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi all, Am 11.10.2013 um 06:41 schrieb Tomi Valkeinen: > On 10/10/13 21:58, Lars-Peter Clausen wrote: > >> According to the datasheet the the panel as a dedicated dout pin. Maybe >> you did not connect it in your design, which means you won't be able to >> read any data from the panel at all. >

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 11.10.2013 um 12:09 schrieb Tomi Valkeinen: On 11/10/13 12:50, Dr. H. Nikolaus Schaller wrote: Hm. Is this a SPI or does it just look like one? Or is it some - otherwise unknown - 3 wire serial interface. Or is it a 3(+1) GPIO slave device? I am still not sure about

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi all, Am 11.10.2013 um 06:41 schrieb Tomi Valkeinen: On 10/10/13 21:58, Lars-Peter Clausen wrote: According to the datasheet the the panel as a dedicated dout pin. Maybe you did not connect it in your design, which means you won't be able to read any data from the panel at all. I

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Lars-Peter, ah, I didn't see your mail while writing mine - so some overlap. Am 11.10.2013 um 09:08 schrieb Lars-Peter Clausen: On 10/11/2013 06:41 AM, Tomi Valkeinen wrote: On 10/10/13 21:58, Lars-Peter Clausen wrote: According to the datasheet the the panel as a dedicated dout pin.

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi all, Am 11.10.2013 um 11:06 schrieb Lars-Peter Clausen: On 10/11/2013 10:59 AM, Belisko Marek wrote: Hi Tomi, On Fri, Oct 11, 2013 at 10:17 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote: On 11/10/13 10:42, Dr. H. Nikolaus Schaller wrote: I am not sure if there is a SPI driver

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Am 10.10.2013 um 14:26 schrieb Lars-Peter Clausen: > On 10/10/2013 02:13 PM, Tomi Valkeinen wrote: >> On 10/10/13 14:52, Dr. H. Nikolaus Schaller wrote: >> >>> Yes, I agree and I am willing to help if someone comes up with such a SoC. >>> At the moment we ha

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 10.10.2013 um 13:10 schrieb Tomi Valkeinen: > On 10/10/13 12:34, Dr. H. Nikolaus Schaller wrote: >> Hi Tomi, >> >> Am 10.10.2013 um 10:19 schrieb Tomi Valkeinen: >> >>> Hi, >>> >>> On 10/10/13 00:08, Marek Belisko wrote: >

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 10.10.2013 um 10:19 schrieb Tomi Valkeinen: > Hi, > > On 10/10/13 00:08, Marek Belisko wrote: >> For communicating with driver is used gpio bitbanging because TD028 does >> not have a standard compliant SPI interface. It is a 3-wire thing with >> direction reversal. > > Isn't that

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 10.10.2013 um 10:19 schrieb Tomi Valkeinen: Hi, On 10/10/13 00:08, Marek Belisko wrote: For communicating with driver is used gpio bitbanging because TD028 does not have a standard compliant SPI interface. It is a 3-wire thing with direction reversal. Isn't that SPI_3WIRE?

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Hi Tomi, Am 10.10.2013 um 13:10 schrieb Tomi Valkeinen: On 10/10/13 12:34, Dr. H. Nikolaus Schaller wrote: Hi Tomi, Am 10.10.2013 um 10:19 schrieb Tomi Valkeinen: Hi, On 10/10/13 00:08, Marek Belisko wrote: For communicating with driver is used gpio bitbanging because TD028 does

Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.

Am 10.10.2013 um 14:26 schrieb Lars-Peter Clausen: On 10/10/2013 02:13 PM, Tomi Valkeinen wrote: On 10/10/13 14:52, Dr. H. Nikolaus Schaller wrote: Yes, I agree and I am willing to help if someone comes up with such a SoC. At the moment we have connected it to the OMAP3 only. True

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Am 03.10.2013 um 22:00 schrieb David Miller: > From: "Dr. H. Nikolaus Schaller" > Date: Thu, 3 Oct 2013 21:40:34 +0200 > >> I have made the bug observation from debug log that this bit is set in a >> response >> each time the modem has a RING messag

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Am 03.10.2013 um 22:00 schrieb David Miller: From: Dr. H. Nikolaus Schaller h...@goldelico.com Date: Thu, 3 Oct 2013 21:40:34 +0200 I have made the bug observation from debug log that this bit is set in a response each time the modem has a RING message. It might be specific to this modem

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi, Am 03.10.2013 um 21:29 schrieb David Miller: > From: "Dr. H. Nikolaus Schaller" > Date: Wed, 2 Oct 2013 09:00:18 +0200 > >> From f5c7e15b61f2ce4fe3105ff914f6bfaf5d74af0d Mon Sep 17 00:00:00 2001 >> From: "H. Nikolaus Schaller" >> Date: Thu,

Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi, Am 03.10.2013 um 21:29 schrieb David Miller: From: Dr. H. Nikolaus Schaller h...@goldelico.com Date: Wed, 2 Oct 2013 09:00:18 +0200 From f5c7e15b61f2ce4fe3105ff914f6bfaf5d74af0d Mon Sep 17 00:00:00 2001 From: H. Nikolaus Schaller h...@goldelico.com Date: Thu, 15 Nov 2012 14:40:57

[PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Jan, we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an issue that under some conditions the modem sends a packed wIndex over USB that is rejected by the hso driver making troubles afterwards. Not rejecting makes it work fine. BR, Nikolaus Schaller --- >From

[PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication

Hi Jan, we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an issue that under some conditions the modem sends a packed wIndex over USB that is rejected by the hso driver making troubles afterwards. Not rejecting makes it work fine. BR, Nikolaus Schaller --- From

<    1   2   3