On Fri, Feb 6, 2015 at 5:34 PM, Michal Malý
madcatxs...@devoid-pointer.net wrote:
This patch series improves handling of various Logitech gaming wheels and
allows switching between various compatibility modes which might be useful
to improve compatibility with very old games and testing
Hi Dmitry,
Since the line I mentioned was removed in v3.19-rc1, I am fine with this patch.
Acked-by: Sonic Zhang sonic.zh...@analog.com
On Fri, Feb 6, 2015 at 2:09 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Instead of using #ifdef to guard potentially unused suspend and resume code
Hi Krzysztof,
Krzysztof Kozlowski k.kozlow...@samsung.com hat am 30. Januar 2015 um 15:47
geschrieben:
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
-
Although the protocol guide says the CRC is calculated from T7 onwards on
the 224s it appears necessary to calculate from T71 (the previous object).
The mismatch is not critical from a functional perspective but causes an
incorrect warning Config CRC error, calculated=... file=...
to be emitted
mxt_update_cfg() first checks the info block CRC (data-info_crc) and
always does an upload irrespective of configuration CRC if it does not match.
However the info_crc is never initialised from the information provided
by the firmware which causes an upload to be done at each probe if
Sometimes configuration fails to load with:
Bad format: failed to parse object
This can occur because the firmware loader does not ensure that
the configuration data is null terminated.
The scanf() therefore reads arbitrary garbage at the end of file.
If one item of garbage happens to
On pon, 2015-02-09 at 20:02 +0100, Stefan Wahren wrote:
Hi Krzysztof,
Krzysztof Kozlowski k.kozlow...@samsung.com hat am 30. Januar 2015 um
15:47
geschrieben:
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of
On Mon, 09 Feb 2015 11:08:01 +0100
Oliver Neukum oneu...@suse.de wrote:
+ ret = usb_interrupt_msg(dev, usb_sndintpipe(dev, 0x02),
+ buf2, sizeof(buf2),
+ transfered, USB_CTRL_SET_TIMEOUT);
You cannot do this. Even for a single byte
On Sun, Feb 08, 2015 at 01:26:32PM +0100, Pali Rohár wrote:
On Monday 02 February 2015 15:27:55 Pali Rohár wrote:
On Monday 02 February 2015 11:49:58 Pali Rohár wrote:
On Monday 02 February 2015 06:49:31 Dmitry Torokhov wrote:
On Sun, Jan 18, 2015 at 10:47:06AM +0100, Pali Rohár wrote:
On pią, 2015-02-06 at 15:59 +0100, Pavel Machek wrote:
On Fri 2015-02-06 15:43:08, Krzysztof Kozlowski wrote:
On pią, 2015-02-06 at 14:49 +0100, Pavel Machek wrote:
On Fri 2015-01-30 15:47:58, Krzysztof Kozlowski wrote:
Use power_supply_put() to decrement the power supply's device
On Sat, 2015-02-07 at 15:48 +0200, Lauri Kasanen wrote:
Without this, my Gasia Co.,Ltd PS(R) Gamepad would not send
any events. Now everything works including the leds.
Based on work by Andrew Haines and Antonio Ospite.
cc: Antonio Ospite a...@ao2.it
cc: Andrew Haines andrewd...@aol.com
As far as I can tell, there is no way to specify values for ABS-keys
in the device tree binding.
It may not be present in device tree binding, but the driver does support it,
so I would rather extend the binding than have a brand new driver.
All right, I find it a bit like whacking a
On Fri, Feb 06, 2015 at 05:00:13PM +0100, Antonio Ospite wrote:
Last doubt, now that I am fixing the DSDT I am going to add an
Interrupt resource, but what is the correct way to specify its value?
Pin 3 of GPO2 is mapped to IRQ 220 by the mainline kernel, so I added
this:
Interrupt
13 matches
Mail list logo
