Re: n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Pali Rohár
On Sunday 15 February 2015 11:21:52 Pavel Machek wrote: Hi! By default, output goes to loudspeaker (top right relative to keyboard). Any ideas how to switch it to the speaker on the left or wired headset? Because I suspect that echo cancelation is not going to be simple...

Re: [PATCH v3 1/5] xhci: add a quirk for device disconnection errata for Synopsis Designware USB3 core

2015-02-15 Thread Sneeker Yeh
Hi Alan: thanks for comment it, and sorry that a little bit late for replying, 2015-02-12 23:18 GMT+08:00 Alan Stern st...@rowland.harvard.edu: On Thu, 12 Feb 2015, Mathias Nyman wrote: On 25.01.2015 10:13, Sneeker Yeh wrote: This issue is defined by a three-way race at disconnect, between

Re: n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Patrik Bachan aka DiGGiT
2015-02-15 11:21 GMT+01:00 Pavel Machek pa...@ucw.cz: Hi! By default, output goes to loudspeaker (top right relative to keyboard). Any ideas how to switch it to the speaker on the left or wired headset? Because I suspect that echo cancelation is not going to be simple...

Re: [PATCH v3 1/5] xhci: add a quirk for device disconnection errata for Synopsis Designware USB3 core

2015-02-15 Thread Sneeker Yeh
hi Mathias: thanks for reviewing these patch, and sorry for replying lately~ 2015-02-12 21:50 GMT+08:00 Mathias Nyman mathias.ny...@intel.com: On 25.01.2015 10:13, Sneeker Yeh wrote: This issue is defined by a three-way race at disconnect, between 1) Class driver interrupt endpoint

Re: n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Pavel Machek
On Sun 2015-02-15 12:08:02, Pali Rohár wrote: On Sunday 15 February 2015 11:21:52 Pavel Machek wrote: Hi! By default, output goes to loudspeaker (top right relative to keyboard). Any ideas how to switch it to the speaker on the left or wired headset? Because I suspect that echo

Re: n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Pali Rohár
On Sunday 15 February 2015 17:20:29 Pavel Machek wrote: On Sun 2015-02-15 12:08:02, Pali Rohár wrote: On Sunday 15 February 2015 11:21:52 Pavel Machek wrote: Hi! By default, output goes to loudspeaker (top right relative to keyboard). Any ideas how to switch it to the speaker on

[PATCH] serial: 8250: Revert tty: serial: 8250_core: read only RX if there is something in the FIFO

2015-02-15 Thread Sebastian Andrzej Siewior
This reverts commit 0aa525d11859c1a4d5b78fdc704148e2ae03ae13. The conditional RX-FIFO read seems to cause spurious interrupts and we see just: |serial8250: too much work for irq29 The previous behaviour was default for decades and Marvell's 88f6282 SoC might not be the only that relies on it.

n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Pavel Machek
Hi! By default, output goes to loudspeaker (top right relative to keyboard). Any ideas how to switch it to the speaker on the left or wired headset? Because I suspect that echo cancelation is not going to be simple... Pavel

Re: n900 audio: any ideas how to get headset speaker to work?

2015-02-15 Thread Pavel Machek
On Sun 2015-02-15 17:27:03, Pali Rohár wrote: On Sunday 15 February 2015 17:20:29 Pavel Machek wrote: On Sun 2015-02-15 12:08:02, Pali Rohár wrote: On Sunday 15 February 2015 11:21:52 Pavel Machek wrote: Hi! By default, output goes to loudspeaker (top right relative to

Enabling DBGEN signal in GP OMAP3

2015-02-15 Thread Grazvydas Ignotas
Hi, Does anyone know if there is a way to make DBGEN signal high on OMAP3530 and/or DM3730 without using a hardware debugger? My goal is to make use of hardware watchpoints in Cortex-A8, but that requires DBGEN to be high. The TRM states: The DBGEM signal on the Cortex-A8 is driven by setting