From: Sonic Zhang
The platform data definition of the rotary driver should be generic for all
architectures.
Signed-off-by: Sonic Zhang
---
arch/blackfin/mach-bf527/boards/ad7160eval.c |2 +-
arch/blackfin/mach-bf527/boards/ezkit.c|2 +-
arch/blackfin/mach-bf548/boar
From: Sonic Zhang
- use readw and writew to access rotary MMRs
- remap rotary register physical address into kernel space in probe
Signed-off-by: Sonic Zhang
---
arch/blackfin/mach-bf527/boards/ad7160eval.c |5 +++
arch/blackfin/mach-bf527/boards/ezkit.c |5 +++
arch/blackfin/mach
From: Sonic Zhang
Signed-off-by: Sonic Zhang
---
arch/blackfin/mach-bf527/boards/ad7160eval.c |8
arch/blackfin/mach-bf527/boards/ezkit.c |8
arch/blackfin/mach-bf548/boards/ezkit.c |8
arch/blackfin/mach-bf609/boards/ezkit.c |8
From: Sonic Zhang
Signed-off-by: Sonic Zhang
---
arch/blackfin/mach-bf527/boards/ad7160eval.c |8
arch/blackfin/mach-bf527/boards/ezkit.c |8
arch/blackfin/mach-bf548/boards/ezkit.c |8
arch/blackfin/mach-bf609/boards/ezkit.c |8
From: Sonic Zhang
- use readw and writew to access rotary MMRs
- remap rotary register physical address into kernel space in probe
v2-changes:
- replace kzalloc with devm_kzalloc
- replace request_irq with devm_request_irq
- remove memory free and irq free from the device remove function
Signed
From: Sonic Zhang
The platform data definition of the rotary driver should be generic for all
architectures.
Signed-off-by: Sonic Zhang
---
arch/blackfin/mach-bf527/boards/ad7160eval.c |2 +-
arch/blackfin/mach-bf527/boards/ezkit.c|2 +-
arch/blackfin/mach-bf548/boar
On Wed, Jan 7, 2015 at 10:08 AM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> Checkpatch complains, and probably with good reason that we should use
> const char const * for the static constant array that never gets
> changed.
>
> Signed-off-by: Olliver Schinagl
Patch applied.
Yours,
On Wed, Jan 7, 2015 at 10:08 AM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> The gpio binding document says that new code should always use named
> gpios. Patch 40b73183 added support to parse a list of gpios from child
> nodes, but does not make it possible to use named gpios. This pat
On Wed, Jan 7, 2015 at 10:08 AM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> In the gpio bindings documents it is requested to use the marco's in
> include/dt-bindings/gpio/gpio.h whenever possible. The gpios in the led
> drivers don't seem to form an exception, so update the example in
On Thu, Jan 8, 2015 at 11:12 PM, Dmitry Torokhov
wrote:
> On Thu, Jan 08, 2015 at 08:40:20AM -0600, Rob Herring wrote:
>> On Thu, Jan 8, 2015 at 2:45 AM, Olliver Schinagl wrote:
>> >>> --- a/drivers/leds/leds-gpio.c
>> >>> +++ b/drivers/leds/leds-gpio.c
>> >>> @@ -184,7 +184,7 @@ static struct g
On 14-01-15 13:45, Linus Walleij wrote:
On Thu, Jan 8, 2015 at 11:12 PM, Dmitry Torokhov
wrote:
On Thu, Jan 08, 2015 at 08:40:20AM -0600, Rob Herring wrote:
On Thu, Jan 8, 2015 at 2:45 AM, Olliver Schinagl wrote:
--- a/drivers/leds/leds-gpio.c
+++ b/drivers/leds/leds-gpio.c
@@ -184,7 +184,7
* Felipe Balbi [150112 08:50]:
> Hi,
>
> On Thu, Jan 08, 2015 at 10:25:12AM -0600, Felipe Balbi wrote:
> > On Tue, Jan 06, 2015 at 11:37:34AM -0600, Felipe Balbi wrote:
> > > On Fri, Dec 26, 2014 at 01:28:20PM -0600, Felipe Balbi wrote:
> > > > STATUS register can be modified by the HW, so we
> >
On Tue, Jan 13, 2015 at 06:30:51PM +0800, Chen-Yu Tsai wrote:
> >> You could probably chain the regulators in the DT via xxx-supply
> >> if it helps. But beyond that, it is hard to do anything meaningful
> >> at this point. Modeling them as fixed regulators beyond our control
> >> is simpler. We al
In order to accommodate new protocol number for Rushmore touchpads
let's shift protocol numbers by 8 bits (i.e. 1 -> 0x100) - this way
we keep protocol version reported in input device id the same as it
was, but add some holes in numbering.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/
In preparation of reworking the way we set protocol parameters let's
split certain protocol items from alps_model_info into a separate
structure.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/alps.c | 58 +++---
drivers/input/mouse/alps.h | 26 +++
Even though Rushmore is very close to V3 protocol it is sufficiently
different to warrant it's own protocol name.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/alps.c | 26 --
drivers/input/mouse/alps.h | 1 +
2 files changed, 17 insertions(+), 10 deletions(-)
Hi Pali,
This series try to address the issue you brought regarding trackstick
initialization on Dell Latitudes in a different way than the patches you
proposed. Basically in this series we move resetting and all detection in
alps_detect() and make sure we keep the state so alps_init() can reuse i
On some Dell Latitudes we fail to identify presence of trackstick unless we
reset the device. The issue is quite benign as we do perform reset in
alps_init(), so the trackstick ends up working, but mouse name reported to
userspace is not accurate.
In order to fix the issue while avoiding the addit
Move setting of all protocol properties into alps_set_protocol (former
alps_set_defaults) instead of having it split between several functions.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/alps.c | 131 +++--
1 file changed, 67 insertions(+), 64
From: Pali Rohár
Previously dev2 device was used for both external PS/2 mouse and internal
trackstick device (if available). This change introduces dev3 device which
is used for external PS/2 mouse data and dev2 is now used only for
trackstick.
In case that trackstick is not present dev2 is not
On Sat, Jan 10, 2015 at 03:15:39PM +0100, Belisko Marek wrote:
> Ping for input maintainer. DT changes was acked. Thanks.
>
> On Tue, Sep 30, 2014 at 10:17 PM, Marek Belisko wrote:
> > This patch adds new parameters that allow to address typical hardware
> > design differences: touch screens may
Hi Jonathan,
On Fri, Dec 19, 2014 at 02:17:49PM -0800, Jonathan Richardson wrote:
> + if (of_property_read_u32(np, "scanning_period", &val) >= 0) {
> + if (val < 1 || val > 256) {
> + dev_err(dev, "scanning_period must be [1-256]\n");
> + ret
On 19/12/14 15:03, Jonathan Richardson wrote:
> On 14-12-19 02:26 PM, Joe Perches wrote:
>> On Fri, 2014-12-19 at 14:17 -0800, Jonathan Richardson wrote:
>>> Add initial version of the Broadcom touchscreen driver.
>>
>> more trivia:
>>
>>> diff --git a/drivers/input/touchscreen/bcm_iproc_tsc.c
>>>
Hi Yoichi,
On Fri, Dec 05, 2014 at 06:17:39PM +0900, Yoichi Yuasa wrote:
> v4 Changes:
> - remove inline
> - master_xfer checks in probe()
> - rewrite rohm_i2c_burst_read()
> - rohm_i2c_burst_read() transfer error returns -EIO
> - remove unused module parameters
> - fix prev_touch_report update
>
On 15-01-14 05:02 PM, Dmitry Torokhov wrote:
Hi Jonathan,
On Fri, Dec 19, 2014 at 02:17:49PM -0800, Jonathan Richardson wrote:
+ if (of_property_read_u32(np, "scanning_period", &val) >= 0) {
+ if (val < 1 || val > 256) {
+ dev_err(dev, "scanning_period
On Wed, Jan 14, 2015 at 09:44:39PM -0800, Scott Branden wrote:
> On 15-01-14 05:02 PM, Dmitry Torokhov wrote:
> >Hi Jonathan,
> >
> >On Fri, Dec 19, 2014 at 02:17:49PM -0800, Jonathan Richardson wrote:
> >>+ if (of_property_read_u32(np, "scanning_period", &val) >= 0) {
> >>+ if (val < 1
Hi,
Am 15.01.2015 um 01:59 schrieb Dmitry Torokhov :
> On Sat, Jan 10, 2015 at 03:15:39PM +0100, Belisko Marek wrote:
>> Ping for input maintainer. DT changes was acked. Thanks.
>>
>> On Tue, Sep 30, 2014 at 10:17 PM, Marek Belisko wrote:
>>> This patch adds new parameters that allow to address
27 matches
Mail list logo
