On Sat, 20 Jun 2015, Antonio Borneo wrote:
Signed-off-by: Ellen Wang el...@cumulusnetworks.com
---
drivers/hid/hid-cp2112.c | 74
++
1 file changed, 55 insertions(+), 19 deletions(-)
diff --git a/drivers/hid/hid-cp2112.c
Clean up the max77693 private header file by removing:
1. Left-overs from previous way of interrupt handling (driver uses
regmap_irq_chip).
2. Unused members of struct 'max77693_dev' related to interrupts in
extcon driver.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by:
This prepares for merging some of the drivers between max77693 and
max77843 so the child MFD driver can be attached to any parent MFD main
driver.
Move the state container to common header file. Additionally add
consistent 'i2c' prefixes to its members (of 'struct i2c_client' type).
Add support for different configurations of charger's registers so the
same driver could be used on other devices (e.g. MAX77843).
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by: Mark Brown broo...@kernel.org
---
drivers/regulator/max77693.c | 39
Dear Mark,
The patchset merges max77843 regulator driver into max77693.
It touches multiple subsystems so I think the best way would be to
merge it through one tree. I already got acks from extcon, input
mfd and power maintainers.
If there are no objections then everything could go through
Add MAX77843_MUIC prefix to some of the defines used in max77843 extcon
driver so the max77693-private.h can be included simultaneously with
max77843-private.h.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by: Lee Jones lee.jo...@linaro.org
Acked-by: Chanwoo Choi
The max77693 regulator driver supports Maxim 77843 device so remove the
max77843 driver.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
---
drivers/regulator/Kconfig| 8 --
drivers/regulator/Makefile | 1 -
drivers/regulator/max77843.c | 203
Switch to the same definition of state container as in MAX77693 drivers.
This will allow usage of one regulator driver in both devices: MAX77693
and MAX77843.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by: Dmitry Torokhov dmitry.torok...@gmail.com
Acked-by: Lee Jones
The charger and safeout part of MAX77843 is almost the same as MAX77693.
From regulator point of view the only differences are the constraints
and register values related to these constraints. Now the max77693
regulator driver can be used for MAX77843.
Signed-off-by: Krzysztof Kozlowski
Add MAX77693 prefix to some of the defines used in max77693 extcon
driver so the max77693-private.h can be included simultaneously with
max77843-private.h.
Additionally use BIT() macro in header.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by: Lee Jones lee.jo...@linaro.org
Store the device type (obtained from i2c_device_id) as an enum and add a
default type of unknown to distinguish from case when this is not set
at all.
Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
Acked-by: Lee Jones lee.jo...@linaro.org
---
include/linux/mfd/max77693-private.h | 11
On Wednesday 08 July 2015 03:55 PM, Ellen Wang wrote:
cp2112_i2c_xfer() only reads up to 61 bytes, returning EIO
on longers reads. The fix is to wrap a loop around
cp2112_read() to pick up all the returned data.
Signed-off-by: Ellen Wang el...@cumulusnetworks.com
---
This is the updated
On 07/08/2015 02:34 AM, Jiri Kosina wrote:
On Sat, 20 Jun 2015, Antonio Borneo wrote:
Signed-off-by: Ellen Wang el...@cumulusnetworks.com
---
drivers/hid/hid-cp2112.c | 74 ++
1 file changed, 55 insertions(+), 19 deletions(-)
diff --git
On Wed, 1 Jul 2015, Jason Gerecke wrote:
Commit 862cf55 neglected to set the WACOM_DEVICETYPE_PAD flag for older
two-finger Bamboo Touch tablets. Not only does this result in the pad
device not appearing when such a tablet is plugged in, but also causes a
segfault when 'wacom_bpt_touch' tries
On Wed, 8 Jul 2015, Ellen Wang wrote:
Works as described. Thank you!
By the way, I tested the code with and without your fix on my rev 2 chip,
and
it behaved the same way as you describe on your rev 1 chip.
Ellen, are you okay with me applying the patch with
On Wed, 8 Jul 2015, Gabriele Mazzotta wrote:
i2c-hid takes care of requesting and handling IRQs for HID devices
which in turns might expect them to be always active when working
in normal conditions. Hence, disabling IRQs before calling the suspend
callbacks can potentially cause problems
Dmitry,
On 07/07/15 19:25, Dmitry Torokhov wrote:
Hi Roger,
On Tue, Jul 07, 2015 at 12:37:31PM +0300, Roger Quadros wrote:
Hi Dmitry,
On 07/07/15 03:27, Dmitry Torokhov wrote:
The binding specification says that touchscreen-size-x and -y specify
horizontal and vertical resolution of the
On Wed, 1 Jul 2015, Ellen Wang wrote:
Works as described. Thank you!
By the way, I tested the code with and without your fix on my rev 2 chip, and
it behaved the same way as you describe on your rev 1 chip.
Ellen, are you okay with me applying the patch with
Tested-by: Ellen Wang
On Tuesday 07 July 2015 22:49:30 Jiri Kosina wrote:
On Tue, 7 Jul 2015, Gabriele Mazzotta wrote:
The irq is most likely required by the suspend callback, so disable it
only after the callback had been executed.
It would be nice to have a more verbose changelog here -- i.e. why we want
On 07/08/2015 02:15 AM, Jiri Kosina wrote:
On Wed, 1 Jul 2015, Ellen Wang wrote:
Works as described. Thank you!
By the way, I tested the code with and without your fix on my rev 2 chip, and
it behaved the same way as you describe on your rev 1 chip.
Ellen, are you okay with me applying the
cp2112_i2c_xfer() only reads up to 61 bytes, returning EIO
on longers reads. The fix is to wrap a loop around
cp2112_read() to pick up all the returned data.
Signed-off-by: Ellen Wang el...@cumulusnetworks.com
---
This is the updated patch with a check for 0 return from
cp2112_read(). I tested
On Tue, Jul 07, 2015 at 09:01:39AM +0800, Axel Lin wrote:
These reg_default tables are not modified after initialized, so make them
const.
Signed-off-by: Axel Lin axel@ingics.com
Applied, thank you.
---
drivers/input/misc/drv260x.c | 2 +-
drivers/input/misc/drv2665.c | 2 +-
On Wed, Jul 08, 2015 at 10:59:04AM +0300, Roger Quadros wrote:
Dmitry,
On 07/07/15 19:25, Dmitry Torokhov wrote:
Hi Roger,
On Tue, Jul 07, 2015 at 12:37:31PM +0300, Roger Quadros wrote:
Hi Dmitry,
On 07/07/15 03:27, Dmitry Torokhov wrote:
The binding specification says that
On 07/08/2015 05:07 AM, Vaibhav Hiremath wrote:
On Wednesday 08 July 2015 03:55 PM, Ellen Wang wrote:
cp2112_i2c_xfer() only reads up to 61 bytes, returning EIO
on longers reads. The fix is to wrap a loop around
cp2112_read() to pick up all the returned data.
Signed-off-by: Ellen Wang
Use for_each_set_bit to check for set bits in bitmap
as it is more efficient than checking individual bits.
Signed-off-by: Anshul Garg aksgarg1...@gmail.com
---
drivers/input/ff-core.c |5 ++---
drivers/input/joydev.c | 11 +--
2 files changed, 7 insertions(+), 9 deletions(-)
cp2112_i2c_xfer() only reads up to 61 bytes, returning EIO
on longers reads. The fix is to wrap a loop around
cp2112_read() to pick up all the returned data.
Signed-off-by: Ellen Wang el...@cumulusnetworks.com
---
This is the updated patch with a check for 0 return from
cp2112_read(). I tested
From: Markus Elfring elfr...@users.sourceforge.net
Date: Wed, 8 Jul 2015 22:12:25 +0200
The gpiod_put() function performs also input parameter validation
by forwarding its single input pointer to the gpiod_free() function.
Thus the test around the calls is not needed.
This issue was detected by
On Wed, Jul 8, 2015 at 7:11 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 06:58:36PM -0400, Benjamin Tissoires wrote:
On Tue, Jul 7, 2015 at 2:06 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jul 07, 2015 at 01:37:14PM +0800, duson wrote:
We
On Wed, Jul 08, 2015 at 06:58:36PM -0400, Benjamin Tissoires wrote:
On Tue, Jul 7, 2015 at 2:06 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jul 07, 2015 at 01:37:14PM +0800, duson wrote:
We want the hover event like BTN_LEFT, even no contract object,
it still can be
29 matches
Mail list logo
