On Tue, Aug 19, 2014 at 01:57:02PM -0500, Felipe Balbi wrote:
> On Tue, Aug 19, 2014 at 02:14:47PM +0200, Frans Klaver wrote:
> > At 3.6Mbaud, with slightly over 2Mbit/s data coming in, we see 1600 uart
> > rx buffer overflows within 30 seconds. Threading the interrupt handling
> > reduces
> > thi
Hi,
On Tue, Aug 19, 2014 at 08:24:05AM -0700, Tony Lindgren wrote:
> Commit 43fef47f94a1 (mfd: twl4030-power: Add a configuration to turn
> off oscillator during off-idle) added support for configuring the PMIC
> to cut off resources during deeper idle states to save power.
[...]
> Fixes: 43fef4
On 08/19/2014 04:16 PM, Mark Rutland wrote:
On Mon, Aug 18, 2014 at 10:46:41PM +0100, Jyri Sarha wrote:
Add machine driver support for BeagleBone-Black HDMI audio. BBB has
NXP TDA998X HDMI transmitter connected to McASP port in I2S mode. The
44100 Hz sample-rate and it's multiples can not be acc
On Tue, Aug 19, 2014 at 02:14:47PM +0200, Frans Klaver wrote:
> At 3.6Mbaud, with slightly over 2Mbit/s data coming in, we see 1600 uart
> rx buffer overflows within 30 seconds. Threading the interrupt handling
> reduces
> this to about 170 overflows in 10 minutes.
Can you try Sebastian Siewior's
On Wed, 20 Aug 2014, Stephen Rothwell wrote:
> On Mon, 18 Aug 2014 13:58:26 -0700 (PDT) Hugh Dickins
> wrote:
> >
> > [PATCH next] vfs: initialize m_list to fix crash in mnt_set_mountpoint
> >
> > Fix mnt_set_mountpoint() crash: new_mountpoint() must initialize m_list.
> >
> > Reported-by: Feli
On Tuesday 19 August 2014 02:20 PM, Markus Pargmann wrote:
> Hi,
>
> On Tue, Aug 19, 2014 at 12:50:59AM +0200, Javier Martinez Canillas wrote:
>> Hello Mugunthan,
>>
>> On Mon, Aug 18, 2014 at 9:58 PM, Mugunthan V N wrote:
Thus, for this patchset, as is:
Tested-by: Steven Rostedt
>
On Fri, Aug 08, 2014 at 06:29:50PM +0200, Sebastian Andrzej Siewior wrote:
> * Vinod Koul | 2014-07-31 17:47:02 [+0530]:
>
> >On Tue, Jul 29, 2014 at 08:58:58PM +0200, Sebastian Andrzej Siewior wrote:
> >> The rx path of the 8250_dma user in the RX-timeout case:
> >> - it starts the RX transfer
>
Commit 43fef47f94a1 (mfd: twl4030-power: Add a configuration to turn
off oscillator during off-idle) added support for configuring the PMIC
to cut off resources during deeper idle states to save power.
This however caused regression for n900 display power that needed the
PMIC configuration to be d
Hi Hugh,
On Mon, 18 Aug 2014 13:58:26 -0700 (PDT) Hugh Dickins wrote:
>
> [PATCH next] vfs: initialize m_list to fix crash in mnt_set_mountpoint
>
> Fix mnt_set_mountpoint() crash: new_mountpoint() must initialize m_list.
>
> Reported-by: Felipe Balbi
> Signed-off-by: Hugh Dickins
I assume t
The omap1's debug-macro.S is similar to the generic 8250 code. Compared to
the 8520 code the omap1 macro automatically determines what UART to use
based on breadcrumbs left by the bootloader and automatically copes with
the eccentric register layout on OMAP7XX.
This patch drops both these features
Hi,
* Deepa Raj [140818 10:32]:
> Hi Tony,
>
> I have few more questions on OMAP3:
>
> 1) As you know there are power scripts in drivers/mfd folder for PMIC chip
> (Triton2). Is this mandatory to use these scripts like there are P1,P2,P3
> areas are there in PMIC.
Not mandatory, but you need
The omap1's debug-macro.S is similar to the generic 8250 code. Compared to
the 8520 code the omap1 macro automatically determines what UART to use
based on breadcrumbs left by the bootloader and automatically copes with
the eccentric register layout on OMAP7XX.
This patch drops both these features
Моето Скъпи Едно,
Приятно ми е да се запознаем аз видях в пощата си днес, когато аз бях търсят и
се интересуват от знаейки, че повече аз наистина биха искали да имат добри
отношения с вас, и аз имам специални причини, поради които реших да се свържем
с вас
Реших да ви пиша, поради неотложността
With the recent pinctrl-single changes, omaps can treat wake-up events
from deeper idle states as interrupts.
Let's add support for the optional second interrupt for wake-up
events. And then SoC can wakeup and handle the event using it's
regular handler.
Finally, to pass the wake-up interrupt in
From: Lucas Weaver
DRA74x and DRA72x family of processors vary slightly in the number
of CPUs. So, add different instances of PMU for each of these processor
groups. Further, since the interrupts bypass crossbar and are directly
connected to GIC, mark the dts nodes with relevant information.
Tes
Hi Tero,
On Fri, Aug 01, 2014 at 02:15:48PM +0100, Tero Kristo wrote:
> External clock provider can now be used to register external clocks under
> it. This is needed as the TI clock driver only registers clocks
> hierarchically under clock providers, and external clocks do not belong
> under any
On Mon, Aug 18, 2014 at 10:46:41PM +0100, Jyri Sarha wrote:
> Add machine driver support for BeagleBone-Black HDMI audio. BBB has
> NXP TDA998X HDMI transmitter connected to McASP port in I2S mode. The
> 44100 Hz sample-rate and it's multiples can not be accurately produced
> on BBB. The only suppo
On Tue, Aug 19, 2014 at 01:23:12PM +0100, Jyri Sarha wrote:
> On 08/19/2014 02:32 PM, Mark Rutland wrote:
> > On Mon, Aug 18, 2014 at 10:46:39PM +0100, Jyri Sarha wrote:
> >> The added ti,gpio-clock is a basic clock that can be enabled and
> >> disabled trough a gpio output. The DT binding document
On 08/19/2014 02:32 PM, Mark Rutland wrote:
On Mon, Aug 18, 2014 at 10:46:39PM +0100, Jyri Sarha wrote:
The added ti,gpio-clock is a basic clock that can be enabled and
disabled trough a gpio output. The DT binding document for the clock
is also added. For EPROBE_DEFER handling the registering o
To determine the correct divisor, we need to know the difference between
the desired baud rate and the actual baud rate. The calculation for this
difference is implemented twice within omap_serial_baud_is_mode16().
Pull out the calculation for easier maintenance.
Signed-off-by: Frans Klaver
---
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in calculate_baud_abs_diff may become 0. This causes
a division by zero when calculating the difference between calculated
and desired baud rates. To prevent this, cap n on 1.
Signed-off-by: Frans Klaver
---
dri
Here's version 2 of the patches that should improve the behavior of the omap
serial port at high baud and data rates.
Differences with regard to v1 are:
- centralize baud_is_mode16's calculation
- fix/unbreak an uninitialized variable in "use threaded interrupt handler"
- read has-hw-flow-co
This makes hardware flow control availability configurable from the
device tree.
Signed-off-by: Frans Klaver
---
Documentation/devicetree/bindings/serial/omap_serial.txt | 1 +
drivers/tty/serial/omap-serial.c | 4
2 files changed, 5 insertions(+)
diff --git a/Docum
At 3.6Mbaud, with slightly over 2Mbit/s data coming in, we see 1600 uart
rx buffer overflows within 30 seconds. Threading the interrupt handling reduces
this to about 170 overflows in 10 minutes.
In practice this therefore reduces the need for hardware flow control,
meaning the sending side doesn'
On Mon, Aug 18, 2014 at 10:46:39PM +0100, Jyri Sarha wrote:
> The added ti,gpio-clock is a basic clock that can be enabled and
> disabled trough a gpio output. The DT binding document for the clock
> is also added. For EPROBE_DEFER handling the registering of the clock
> has to be delayed until of_
On 08/19/2014 12:28 AM, Dmitry Torokhov wrote:
On Mon, Aug 18, 2014 at 03:13:29PM -0500, Nishanth Menon wrote:
Many palmas family of PMICs have support for interrupt based power
button. This allows the device to notify the processor of external
push button events over the shared palmas interrupt
Hi Dmitry
On 08/19/2014 12:23 AM, Dmitry Torokhov wrote:
Thanks for the review.
[...]
+
+/**
+ * pwron_irq() - button press isr
+ * @irq: irq
+ * @palmas_pwron: pwron struct
+ */
+static irqreturn_t pwron_irq(int irq, void *palmas_pwron)
+{
+ struct palmas_pwron *pwron =
Hi Suman,
On Tue, Jul 29, 2014 at 10:33 PM, Suman Anna wrote:
> We currently have two usecases. The primary usecase is the WkupM3
> processor on TI Sitara AM335x/AM437x SoCs used for suspend/resume
> management. This series is a dependency for the WkupM3 remoteproc driver
> that Dave posted [1].
Hi,
On Tue, Aug 19, 2014 at 12:50:59AM +0200, Javier Martinez Canillas wrote:
> Hello Mugunthan,
>
> On Mon, Aug 18, 2014 at 9:58 PM, Mugunthan V N wrote:
> >>
> >> Thus, for this patchset, as is:
> >>
> >> Tested-by: Steven Rostedt
> >
> > This will fail for DRA7xx not in AM33xx
> >
>
> cpsw_
29 matches
Mail list logo
