n panel type for Ivy Bridge + Mobile chips.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/gpu/drm/i915/intel_opregion.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_opregion.c
b/drivers/gpu/drm/i915/intel_opregion.c
index adca262..
Thank you all for your help on this.
Adrien
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
All ELAN hid devices seem to require the ALWAYS_POLL quirk. Let's use
this quirk for all devices from this vendor, rather than maintaining a
list of all its known product IDs.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/hid/hid-ids.h | 5 -
drivers/hid/u
iptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71
[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/driver
Benjamin Tissoires.
Changes since v2:
- Apply ALWAYS_POLL quirk to all ELAN devices by default, as suggested by
Jiri Kosina and Oliver Neukum.
Adrien Vergé (2):
USB: quirks: Fix another ELAN touchscreen
USB: quirks: Apply ALWAYS_POLL to all ELAN devices
drivers/hid/hid-ids.h | 5
All ELAN hid devices seem to require the ALWAYS_POLL quirk. Let's use
this quirk for all devices from this vendor, rather than maintaining a
list of all its known product IDs.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/hid/hid-ids.h | 5 -
drivers/hid/u
default, as suggested by
Jiri Kosina and Oliver Neukum.
Adrien Vergé (2):
USB: quirks: Fix another ELAN touchscreen
USB: quirks: Apply ALWAYS_POLL to all ELAN devices
drivers/hid/hid-ids.h | 5 -
drivers/hid/usbhid/hid-quirks.c | 9 +++--
drivers/usb/core/quirks.c | 3
iptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71
[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/driver
2015-11-24 15:11 GMT+01:00 Benjamin Tissoires :
> Instead of adding a second table, I'd rather have a match on
> HID_ANY_ID for the product ID.
Thanks Benjamin, the way you propose is much cleaner. (I actually
looked for such a *wildcard* product id, but apparently didn't looked
deep enough!)
--
nd in hid_product_blacklist[].
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/hid/hid-ids.h | 5 -
drivers/hid/usbhid/hid-quirks.c | 43 +++--
2 files changed, 29 insertions(+), 19 deletions(-)
diff --git a/drivers/hid/hid-id
iptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71
[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/driver
This is the third version of a patchset which originally aimed to fix a buggy
touchscreen from ELAN Microelectronics.
Thanks to feedback from Jiri Kosina and Oliver Neukum, the ALWAYS_POLL quirk is
now applied to all ELAN devices by default.
Adrien Vergé (2):
USB: quirks: Fix another ELAN
iptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71
[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.
Tested-by: Adrien Vergé
Signed-off-by: Adrien Vergé
Acked-by: Jiri Kosina
---
drivers/hid/hid-ids.h | 1 +
drivers/hid/usbhid/hid-qu
2015-11-23 15:52 GMT+01:00 Jiri Kosina :
> The drivers/hid part is
>
> Acked-by: Jiri Kosina
Thanks.
> Makes one wonder however whether we shouldn't be applying ALWAYS_POLL to
> all ELAN devices by default anyway.
True! But I don't want to risk breaking anything on other models in this
iptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71
[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.
Tested-by: Adrien Vergé
---
drivers/hid/hid-ids.h | 1 +
drivers/hid/usbhid/hid-quirks.c | 1 +
drivers/usb/core/quirks.c | 3 ++
ONTEXTIDR and PID_NS independent
This series of patches applies to v3.13.
Adrien Vergé (5):
ARM CoreSight: ETM: Fix a memory allocation failure
ARM CoreSight: ETM: Use device attributes
ARM CoreSight: ETM: Rename 'comparator' to 'address comparator'
ARM CoreSight: ETM: Add
is present
in the Context ID register.
Signed-off-by: Adrien Vergé
---
arch/arm/include/asm/hardware/coresight.h | 5 ++
arch/arm/kernel/etm.c | 131 --
2 files changed, 129 insertions(+), 7 deletions(-)
diff --git a/arch/arm/include/asm/hardware
In the same manner as for enabling tracing, an entry is created
in sysfs to set the address range that triggers tracing.
Signed-off-by: Adrien Vergé
---
arch/arm/kernel/etm.c | 52 ---
1 file changed, 49 insertions(+), 3 deletions(-)
diff --git a
When an application reads the ETB buffer too often, it can be empty.
In this case, it results in a "vmalloc: allocation failure: 0 bytes",
a backtrace in dmesg and a vfree on an incorrect address.
This patch allocates and frees the trace buffer only when necessary.
Signed-off-by: Ad
Replace all kobjects attributes with device attributes.
User experience isn't changed since the same files are created in sysfs.
Signed-off-by: Adrien Vergé
---
arch/arm/kernel/etm.c | 48 +---
1 file changed, 21 insertions(+), 27 deletions(-)
Since there are different types of comparators, and other kinds will
be used (such as Context ID comparators), rename them properly.
Signed-off-by: Adrien Vergé
---
arch/arm/include/asm/hardware/coresight.h | 4 ++--
arch/arm/kernel/etm.c | 19 ++-
2 files
2014-01-24 Paul Bolle :
> I see. Well, if your analysis is correct I think you're supposed to add
> Fixes: 1a97b7f22774 ("ALSA: hda/realtek - Remove the last static quirks
> for ALC882")
Sorry for that. Thank you for correcting.
2014-01-25 Nicolo' :
> I can confirm this happens on my machin
I think very few people use Linux on their MBA 1,1. Moreover, part of
them remained on v2.6.
2014/1/24 Paul Bolle :
> On Fri, 2014-01-24 at 14:56 -0500, Adrien Vergé wrote:
>> Similarly to other Apple products, MBA 1,1 needs a specific quirk.
>> Pin 0x18 must be set to VREF_5
Vergé
Signed-off-by: Adrien Vergé
---
sound/pci/hda/patch_realtek.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index c564694..723de28 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound
2014/1/24 Will Deacon :
> I think I'd rather have the global ID than disable a potentially useful
> feature, especially since this is likely to be consumed by external trace
> tools as opposed to user-space tasks.
I understand.
2014/1/24 Christopher Covington :
> Would it be reasonable to make wh
2014/1/24 Will Deacon :
> Are you sure about this? The value we write is actually task_pid_nr, which I
> believe to be globally unique.
You are right: the task_pid_nr is unique in the system. However when
using namespaces, the so called "PID" is the virtual number that
processes in different names
compatible with PID_NS.
Signed-off-by: Adrien Vergé
---
arch/arm/Kconfig.debug | 2 +-
arch/arm64/Kconfig.debug | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 5765abf..ed46748 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch
In the same manner as for enabling tracing, an entry is created
in sysfs to set the address range that triggers tracing.
Signed-off-by: Adrien Vergé
---
arch/arm/kernel/etm.c | 52 ---
1 file changed, 49 insertions(+), 3 deletions(-)
diff --git a
Since there are different types of comparators, and other kinds will
be used (such as Context ID comparators), rename them properly.
Signed-off-by: Adrien Vergé
---
arch/arm/include/asm/hardware/coresight.h | 4 ++--
arch/arm/kernel/etm.c | 19 ++-
2 files
In the same manner as for enabling tracing, an entry is created in
sysfs to set the PID that triggers tracing. This change is effective
only if CONFIG_PID_IN_CONTEXTIDR is set, and thus is not compatible
with PID namespaces.
Signed-off-by: Adrien Vergé
---
arch/arm/include/asm/hardware
Replace all kobjects attributes with device attributes.
User experience isn't changed since the same files are created in sysfs.
Signed-off-by: Adrien Vergé
---
arch/arm/kernel/etm.c | 48 +---
1 file changed, 21 insertions(+), 27 deletions(-)
Some user applications try to retrieve trace data often, there
is no need to call vmalloc() when there is 0 byte to fetch.
Signed-off-by: Adrien Vergé
---
arch/arm/kernel/etm.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch/arm/kernel/etm.c b/arch/arm
nt for pid type (not long)
- During trace fetching, call vmalloc() only if really needed
This series of patches applies to v3.13.
Adrien Vergé (6):
ARM CoreSight: ETM: Use device attributes
ARM CoreSight: ETM: Rename 'comparator' to 'address comparator'
ARM CoreSight: ET
Hi Greg and Christopher,
Thank you for your feedback.
2013/12/4 Greg Kroah-Hartman
> What is it's purpose then? At first glance, this seems to be exactly
> what 'perf' provides already. Doesn't perf work on ARM today?
On ARM, perf is unable to trace every instruction, and certainly not
record
2013/12/4 Greg Kroah-Hartman :
> How much overhead does the existing tracing code have on ARM? Is ETM
> still even needed? Why not just use ETM for the core tracing code
> instead?
Coresight ETM is not just faster than /sys/kernel/debug/tracing, it
provides more detailed and customisable info. F
2013/12/4 Greg Kroah-Hartman :
> Your pid implementation is broken, see my other email about that :(
Thank you for your remarks on pid. I'll try to correct that.
> And again, what's wrong with the existing tracing functionalty that is
> processor agnostic? Why can't we just delete this driver to
time (and more experience than me ;)) moves it out from sysfs.
Thanks,
Adrien
2013/12/4 Greg Kroah-Hartman :
> On Tue, Dec 03, 2013 at 11:39:21PM -0500, Adrien Vergé wrote:
>> Usage of ETM tracing facility is currently very limited: user can
>> only start/stop tracing. This se
In the same manner as for enabling tracing, an entry is created in
sysfs to set the PID that triggers tracing. This change requires
CONFIG_PID_IN_CONTEXTIDR to be set when using on-chip ETM.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc
In the same manner as for enabling tracing, an entry is created
in sysfs to set the address range that triggers tracing.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kroah-Hartman
Since there are different types of comparators, and other kinds will
be used (such as Context ID comparators), rename them properly.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kro
trace_pid to
let the user read/write custom values.
This series of patches apply to v3.13-rc2.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kroah-Hartman
Cc: Randy Dunlap
---
Adrie
trace_pid to
let the user read/write custom values.
This series of patches apply to v3.13-rc2.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kroah-Hartman
Cc: Randy Dunlap
---
Adrie
Hi,
I am modifying the perf internals to avoid the overhead due to a
second copy, when using Intel's BTS (execution tracing). Mainly, I
have a buffer that fills during the execution of the traced process,
and I sometimes need to save its contents.
When my buffer should be emptied, I schedule a ta
2013/5/29 Roger Quadros :
> ehci-omap needs NOP_USB_XCEIV PHY driver to function
> properly, so select it. As the USB PHY drivers no longer
> depend on USB_PHY, it is safe to select the PHY drivers.
>
> Signed-off-by: Roger Quadros
Acked-by: Adrien Vergé
Tested-by: Adrien Vergé
) support.
We do not enable USB_EHCI_HCD here because all features aren't fully
supported yet.
This patch applies to Linux 3.10-rc3.
Cc: Roger Quadros
Cc: Arnd Bergmann
Cc: Felipe Balbi
Signed-off-by: Adrien Vergé
---
arch/arm/configs/omap2plus_defconfig |2 ++
1 file changed, 2 inser
Dear Arnd and Roger, thank you for your answers.
2013/5/28 Roger Quadros
> Selecting NOP_USB_XCEIV is wrong as it in turn depends on USB_PHY.
>
> I'm not for depends as it would hide USB_EHCI_HCD_OMAP in menuconfig.
> I'm for explicitly selecting both, as it makes the user's life much
> easier.
>
On OMAP4 platforms, EHCI HCD needs the physical layer signalling
activated, along with the NOP USB Transceiver driver. Otherwise, the
kernel boots without registering any USB device.
This patch applies to Linux 3.10-rc2.
Signed-off-by: Adrien Vergé
---
diff --git a/drivers/usb/host/Kconfig b
47 matches
Mail list logo
