* Peter Hurley | 2014-09-23 13:03:51 [-0400]:
readline() does this; it 'saves' the caller's termios, sets termios
for non-canonical reads, reads one char, and 'restores' the caller's
termios.
interresting, thanks. I guess I would need to opimize this a little so
the baudrate isn't going to 0 and
* Frans Klaver | 2014-09-22 11:28:54 [+0200]:
Wow, thanks for your work here. This does indeed sound hard to trap.
I guess then we'd still have to answer the question why the yocto build
calls set_termios() so often, but that's not on you then. Did you notice
it even changing settings? We might
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.
While at it, remove the
On Tue, Sep 23, 2014 at 11:58 PM, Greg Kroah-Hartman wrote:
So both would be needed to be backported to stable kernels? Why not
just do the fix first, then the cleanup afterward, to make backporting
easier?
Sure thing. I read something about cleaning up first, then actually changing
stuff,
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero when calculating the difference between
calculated and desired baud rates. To prevent this, cap the n13 and n16
values on 1.
Division
On Fri, Sep 05, 2014 at 01:42:09AM +0400, Sergei Shtylyov wrote:
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY
On 17 September 2014 19:20, Balaji T K balaji...@gmail.com wrote:
As I won't be able to maintain omap_hsmmc driver
Signed-off-by: Balaji T K balaji...@gmail.com
Sorry to see you go Balaji. Thanks for all your support!
Patch applied for next.
Kind regards
Uffe
---
MAINTAINERS | 3 +--
1
On Wed, Sep 24, 2014 at 09:55:21AM +0200, Frans Klaver wrote:
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero when calculating the difference between
calculated and desired baud
On Wed, Sep 24, 2014 at 01:08:52AM -0700, Greg Kroah-Hartman wrote:
On Wed, Sep 24, 2014 at 09:55:21AM +0200, Frans Klaver wrote:
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero
On 22 September 2014 13:55, Andreas Fenkart afenk...@gmail.com wrote:
mmci and omap_hsmmc share very little fields in the platform
mmci? Should be omap right?
I noticed the similar typo for one of the patches as well.
Kind regards
Uffe
struct. unsharing significantly simplifies the
On 09/19/2014 08:27 PM, Paul Walmsley wrote:
On Fri, 19 Sep 2014, Paul Walmsley wrote:
However, I saw the following crash at boot on 37xxevm during one of
the boot test. Ran thirty more boot tests afterwards on that board
and it did not recur. It seems unlikely that the problem is related
to
On Wed, Sep 24, 2014 at 10:41:11AM +0200, Frans Klaver wrote:
On Wed, Sep 24, 2014 at 01:08:52AM -0700, Greg Kroah-Hartman wrote:
On Wed, Sep 24, 2014 at 09:55:21AM +0200, Frans Klaver wrote:
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in
There is no need to init .owner field.
Based on the patch from Peter Griffin peter.grif...@linaro.org
mmc: remove .owner field for drivers using module_platform_driver
This patch removes the superflous .owner field for drivers which
use the module_platform_driver API, as this is overriden in
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable only from secure mode.
First four patches extend
From: Tomasz Figa t.f...@samsung.com
Exynos4 SoCs equipped with an L2C-310 cache controller and running under
secure firmware require certain registers of aforementioned IP to be
accessed only from secure mode. This means that SMC calls are required
for certain register writes. To handle this, an
From: Tomasz Figa t.f...@samsung.com
This patch adds device tree nodes for L2 cache controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/boot/dts/exynos4210.dtsi | 9 +
From: Tomasz Figa t.f...@samsung.com
On Exynos SoCs it is necessary to resume operation of L2C early in
assembly code, because otherwise certain systems will crash. This patch
adds necessary code to non-secure resume handler.
Signed-off-by: Tomasz Figa t.f...@samsung.com
[rewrote the code
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch introduces bindings to enable
prefetch settings to be specified from DT and
From: Tomasz Figa t.f...@samsung.com
Certain implementations of secure hypervisors (namely the one found on
Samsung Exynos-based boards) do not provide access to individual L2C
registers. This makes the .write_sec()-based interface insufficient and
provoking ugly hacks.
This patch is first step
From: Tomasz Figa t.f...@samsung.com
Certain platforms (i.e. Exynos) might need to set .write_sec callback
from firmware initialization which is happenning in .init_early callback
of machine descriptor. However current code will overwrite the pointer
with whatever is present in machine
From: Tomasz Figa t.f...@samsung.com
Because certain secure hypervisor do not allow writes to individual L2C
registers, but rather expect set of parameters to be passed as argument
to secure monitor calls, there is a need to provide an interface for the
L2C driver to ask the firmware to configure
On Wed, Sep 24, 2014 at 12:05:38PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch
On 24.09.2014 13:14, Mark Rutland wrote:
On Wed, Sep 24, 2014 at 12:05:38PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
There is no need to init .owner field.
Based on the patch from Peter Griffin peter.grif...@linaro.org
mmc: remove .owner field for drivers using module_platform_driver
This patch removes the superflous .owner field for drivers which
use the module_platform_driver API, as this is overriden in
On Thu, 04 Sep 2014, Sebastian Andrzej Siewior wrote:
From: Jeff Lance j-lan...@ti.com
The logic in AFE_Pen_Ctrl bitmask in the CTRL register is different for five
wire versus four or eight wire touschscreens. This patch should fix this for
five-wire touch screens. There should be no change
On Wed, Sep 24, 2014 at 12:19:45PM +0100, Tomasz Figa wrote:
On 24.09.2014 13:14, Mark Rutland wrote:
On Wed, Sep 24, 2014 at 12:05:38PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C
prefetch
On 22:07-20140923, Olof Johansson wrote:
On Thu, Sep 11, 2014 at 04:28:55PM -0700, Tony Lindgren wrote:
The following changes since commit d7eb67f7fef9c046f27a975118da2324de65a90c:
Merge branch 'pull/v3.18/powerdomain-fixes' of
https://github.com/nmenon/linux-2.6-playground into
* Nishanth Menon n...@ti.com [140924 08:24]:
On 22:07-20140923, Olof Johansson wrote:
On Thu, Sep 11, 2014 at 04:28:55PM -0700, Tony Lindgren wrote:
The following changes since commit
d7eb67f7fef9c046f27a975118da2324de65a90c:
Merge branch 'pull/v3.18/powerdomain-fixes' of
This patch series adds a simple macro pm_runtime_last_busy_and_autosuspend()
which invokes pm_runtime_mark_last_busy() and pm_runtime_put_autosuspend()
sequentially. Then we do a tree wide update of current patterns which are
present. As evident from log below this pattern is frequent in the
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul vinod.k...@intel.com
---
drivers/i2c/busses/i2c-omap.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul vinod.k...@intel.com
---
drivers/usb/musb/omap2430.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/musb/omap2430.c
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
This patch also changes return value from macro rather than 0 always!
Signed-off-by: Vinod Koul vinod.k...@intel.com
---
drivers/mmc/host/omap_hsmmc.c | 19 ---
1 files changed, 4
hello.
On 09/24/2014 09:11 AM, Greg KH wrote:
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY support.
Hello.
This patchset is against the usb-next' branch of Greg KH's 'usb.git' repo.
Here I add support for the generic PHY to the 'struct usb_hcd' (having to
rename the existing 'phy' field to 'usb_phy' beforehand). This was mainly
intended to be used with the PCI OHCI/EHCI drivers and also xHCI
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY support.
Signed-off-by: Antoine Tenart antoine.ten...@free-electrons.com
On Wed, Sep 24, 2014 at 11:05:50PM +0400, Sergei Shtylyov wrote:
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY
Hello.
On 09/24/2014 11:28 PM, Felipe Balbi wrote:
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY support.
On Wed, Sep 24, 2014 at 11:31:11PM +0400, Sergei Shtylyov wrote:
Hello.
On 09/24/2014 11:28 PM, Felipe Balbi wrote:
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing
On Wednesday, September 24, 2014 09:44:50 PM Vinod Koul wrote:
This patch series adds a simple macro pm_runtime_last_busy_and_autosuspend()
which invokes pm_runtime_mark_last_busy() and pm_runtime_put_autosuspend()
sequentially. Then we do a tree wide update of current patterns which are
On Wed, Sep 24, 2014 at 01:10:51PM +0100, Mark Rutland wrote:
On Wed, Sep 24, 2014 at 12:19:45PM +0100, Tomasz Figa wrote:
On 24.09.2014 13:14, Mark Rutland wrote:
I'm not too keen on tristate properties. Is this level of flexibility
really required?
I would say that we need a way to
40 matches
Mail list logo
