Hi Hn,
On Thu, May 21, 2015 at 03:43:08PM +0800, Hn Chen wrote:
> Hi, Dmitry,
>
> Thanks for your comments.
> Here are my replies for some comments.
>
> > + fw_id = ((fw_chunk_info.chunk_info.version_number >> 12) & 0xF);
> > + chip_id = (((dev_wdt87xx->sys_param.fw_id) >> 12) & 0xF);
> > +
On Thu, May 21, 2015 at 01:42:24PM +0200, Geert Uytterhoeven wrote:
> Hi Dmitry,
>
> This is a resent of a series by Laurent Pinchart to fix OF matching for
> the adxl34x driver.
>
> According to the discussion in response to that series, we were under
> the impression this was going in thr
On Fri, May 22, 2015 at 02:05:52AM +0200, Marek Vasut wrote:
> On Friday, May 22, 2015 at 02:01:21 AM, Dmitry Torokhov wrote:
> > On Fri, May 22, 2015 at 01:58:34AM +0200, Marek Vasut wrote:
> > > On Friday, May 08, 2015 at 07:22:28 PM, Dmitry Torokhov wrote:
> > > > On Fri, May 08, 2015 at 11:47:3
The STMPE MFD is only used with device tree configured systems (and STMPE
MFD core depends on OF), so force the configuration to come from device
tree only.
Signed-off-by: Dmitry Torokhov
---
Not tested as no device, please give it a spin.
drivers/input/touchscreen/Kconfig| 1 +
drivers/i
Am 22.05.2015 um 22:17 schrieb Dmitry Torokhov:
> On Fri, May 22, 2015 at 09:01:50PM +0200, Heiner Kallweit wrote:
>> Am 22.05.2015 um 20:29 schrieb Dmitry Torokhov:
>>> On Fri, May 22, 2015 at 07:34:43AM +0200, Heiner Kallweit wrote:
Am 22.05.2015 um 01:06 schrieb Dmitry Torokhov:
> Hi He
On Fri, May 22, 2015 at 09:01:50PM +0200, Heiner Kallweit wrote:
> Am 22.05.2015 um 20:29 schrieb Dmitry Torokhov:
> > On Fri, May 22, 2015 at 07:34:43AM +0200, Heiner Kallweit wrote:
> >> Am 22.05.2015 um 01:06 schrieb Dmitry Torokhov:
> >>> Hi Heiner,
> >>>
> >>> On Thu, May 21, 2015 at 11:19:52P
The platform_sysrq_reset_seq code was intended as a way for an embedded
platform to provide its own sysrq sequence at compile time. After over
two years, nobody has started using it in an upstream kernel, and
the platforms that were interested in it have moved on to devicetree,
which can be used to
On Thursday 21 May 2015 11:11:28 Arnd Bergmann wrote:
> diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c
> index 8ba52e56bb8b..9c5395db6a57 100644
> --- a/drivers/tty/sysrq.c
> +++ b/drivers/tty/sysrq.c
> @@ -55,8 +55,7 @@
> static int __read_mostly sysrq_enabled = CONFIG_MAGIC_SYSRQ_DEFAULT
Am 22.05.2015 um 20:29 schrieb Dmitry Torokhov:
> On Fri, May 22, 2015 at 07:34:43AM +0200, Heiner Kallweit wrote:
>> Am 22.05.2015 um 01:06 schrieb Dmitry Torokhov:
>>> Hi Heiner,
>>>
>>> On Thu, May 21, 2015 at 11:19:52PM +0200, Heiner Kallweit wrote:
Even with poper DT config the module did
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. The main change is that
we tell joydev not to touch "absolute mice", such as VMware virtual
mouse, as that produced bad result (cursor stuck in u
On Fri, May 22, 2015 at 07:34:43AM +0200, Heiner Kallweit wrote:
> Am 22.05.2015 um 01:06 schrieb Dmitry Torokhov:
> > Hi Heiner,
> >
> > On Thu, May 21, 2015 at 11:19:52PM +0200, Heiner Kallweit wrote:
> >> Even with poper DT config the module didn't autoload.
> >> That's fixed by this additional
On Thu, May 21, 2015 at 11:11:28AM +0200, Arnd Bergmann wrote:
> The platform_sysrq_reset_seq code was intended as a way for an embedded
> platform to provide its own sysrq sequence at compile time. After over
> two years, nobody has started using it in an upstream kernel, and
> the platforms that
On Tue, Apr 28, 2015 at 11:16:28AM +0530, Rajeev Kumar wrote:
> rajeev-dlh.ku...@st.com email-id doesn't exist anymore as I have left the
> company. Replace ST's id with Rajeev Kumar
>
> Signed-off-by: Rajeev Kumar
Applied, thank you.
> ---
> drivers/input/keyboard/spear-keyboard.c |
On Sun, Apr 26, 2015 at 06:15:22PM +, Khem Raj wrote:
> gcc-5 defaults to gnu11 which used c99 inline semantics
> in c99 'inline' is not externally visible unlike gnu89, therefore
> we use 'static inline' which has same semantics between gnu89 and c99
>
> Signed-off-by: Khem Raj
> CC: Dmitry
On Fri, May 22, 2015 at 04:37:12PM +0200, Ulf Hansson wrote:
> On 14 April 2015 at 12:41, Ulf Hansson wrote:
> > The legacy system PM support has long time ago been dropped from the
> > AMBA bus. Align to that by converting to the modern system PM
> > callbacks.
> >
> > Fixes: 26825cfd90f9 (ARM: 7
On Fri, May 22, 2015 at 04:37:12PM +0200, Ulf Hansson wrote:
> On 14 April 2015 at 12:41, Ulf Hansson wrote:
> > The legacy system PM support has long time ago been dropped from the
> > AMBA bus. Align to that by converting to the modern system PM
> > callbacks.
> >
> > Fixes: 26825cfd90f9 (ARM: 7
From: Frank Li
enable snvs ONOFF power key support
Signed-off-by: Frank Li
---
arch/arm/boot/dts/imx6sx.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dtsi
index 3cb3b5b..ad38aea 100644
--- a/arch/arm/boot/dts/imx6sx.dts
From: Frank Li
The snvs-pwrkey is designed to enable POWER key function which controlled
by SNVS ONOFF. the driver can report the status of POWER key and wakeup
system if pressed after system suspend.
Signed-off-by: Frank Li
Signed-off-by: Robin Gong
---
.../devicetree/bindings/crypto/fsl-sec
From: Robin Gong
add snvs power key driver.
It work in imx chips after i.mx6sx
ON/OFF key used power on/off whole system.
This driver make it wakeup from suspend state when short press
ON/OFF key.
Long time press will trig SNVS power off chip without software
intervention.
Signed-off-by: Robin
From: Frank Li
snvs is MFP device. Change dts to use syscon to allocate register resource.
snvs power off also switch to common syscon-poweroff
Signed-off-by: Frank Li
---
arch/arm/boot/dts/imx6qdl.dtsi | 19 +--
arch/arm/boot/dts/imx6sl.dtsi | 19 +--
arch/arm
On 14 April 2015 at 12:41, Ulf Hansson wrote:
> The legacy system PM support has long time ago been dropped from the
> AMBA bus. Align to that by converting to the modern system PM
> callbacks.
>
> Fixes: 26825cfd90f9 (ARM: 7914/1: amba: Drop legacy PM support ...)
> Signed-off-by: Ulf Hansson
W
From: Frank Li
snvs included rtc, on/off key, power-off module
change to syscon to access register
Signed-off-by: Frank Li
---
drivers/rtc/rtc-snvs.c | 136 +
1 file changed, 70 insertions(+), 66 deletions(-)
diff --git a/drivers/rtc/rtc-snvs.c
From: Frank Li
snvs actually is multi fucntion driver.
Change to use syscon to access register.
Signed-off-by: Frank Li
---
.../devicetree/bindings/crypto/fsl-sec4.txt| 28 --
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git a/Documentation/devicetree/b
From: Frank Li
Change from v3 to v4
- fix align
- change to pr_warn
Change from v2 to v3
- Keep snvs rtc compatiblity with old dts file
- use general syscon-poweroff instead of modifying snvs-poweroff.c
Change from v1 to v2
- Change simple-bus to simple-mfd
- RTC remove lock.
- RTC remov
Hi,
This looks good to me, a few nits below
On 22/05/2015 at 00:16:47 +0800, frank...@freescale.com wrote :
> - spin_unlock_irqrestore(&data->lock, flags);
> + regmap_update_bits(data->regmap, data->offset + SNVS_LPCR,
> + (SNVS_LPCR_LPTA_EN | SNVS_LPCR_LPWUI_EN),
Th
According to the touch controller SPEC, SPI return a 16 bit value,
only 12 bits are valid, they are bit[14-3].
The value of MISO and MOSI can be configed when SPI in idle mode.
Currently this touch driver consider the SPI bus set the MOSI and
MISO in low level when SPI bus in idle mode. So the bit
26 matches
Mail list logo