Hi Mark Brown wrote:
For example, SSI device have many ports (0-8),
but ADG is only 1 device.
On this driver, all devices are using rsnd_write/read() to
access register.
OK, this sounds like the module should have this information - ie check
something in the module structure rather
Current Linux kernel is supporting regmap/regmap_field,
and, it is good match for Renesas Sound Gen1/Gen2 register mapping.
This patch uses regmap instead of original method for register access
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
sound/soc/sh/rcar/core.c | 45
adg.c only used rsnd_priv_read/write/bset()
which is the only user of NULL mod.
but, it can be removed.
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
sound/soc/sh/rcar/adg.c | 10 +++---
sound/soc/sh/rcar/rsnd.h |4
2 files changed, 7 insertions(+), 7
Linus, please apply the following patch series. There's fixes for
_three_ different data corruption bugs, all of which were found by users
hitting them in the wild.
The first one isn't bcache specific - in 3.11 bcache was switched to the
bio_copy_data in fs/bio.c, and that's when the bug in that
From: Gabriel de Perthuis g2p.c...@gmail.com
sysfs attributes with unusual characters have crappy failure modes
in Squeeze (udev 164); later versions of udev are unaffected.
This should make these characters more unusual.
Signed-off-by: Gabriel de Perthuis g2p.c...@gmail.com
Signed-off-by: Kent
That switch statement was obviously wrong, leading to some sort of weird
spinning on rare occasion with discards enabled...
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: linux-stable sta...@vger.kernel.org # = v3.10
---
drivers/md/bcache/journal.c | 2 +-
1 file changed, 1 insertion(+),
The memcpy() in bio_copy_data() was using the wrong offset vars, leading
to data corruption in weird unusual setups.
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: Jens Axboe ax...@kernel.dk
Cc: linux-stable sta...@vger.kernel.org # = v3.9
---
fs/bio.c | 4 ++--
1 file changed, 2
Background writeback works by scanning the btree for dirty data and
adding those keys into a fixed size buffer, then for each dirty key in
the keybuf writing it to the backing device.
When read_dirty() finishes and it's time to scan for more dirty data, we
need to wait for the outstanding
In writeback mode, when we get a cache flush we need to make sure we
issue a flush to the backing device.
The code for sending down an extra flush was wrong - by cloning the bio
we were probably getting flags that didn't make sense for a bare flush,
and also the old code was firing for FUA bios,
The journal replay code didn't handle this case, causing it to go into
an infinite loop...
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: linux-stable sta...@vger.kernel.org # = v3.10
---
drivers/md/bcache/journal.c | 30 ++
1 file changed, 18 insertions(+), 12
bch_journal_meta() was missing the flush to make the journal write
actually go down (instead of waiting up to journal_delay_ms)...
Whoops
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: linux-stable sta...@vger.kernel.org # = v3.10
---
drivers/md/bcache/journal.c | 1 +
1 file changed, 1
btree_sort_fixup() was overly clever, because it was trying to avoid
pulling a key off the btree iterator in more than one place.
This led to a really obscure bug where we'd break early from the loop in
btree_sort_fixup() if the current key overlapped with keys in more than
one older set, and the
schedule_timeout() != schedule_timeout_uninterruptible()
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: linux-stable sta...@vger.kernel.org # = v3.10
---
drivers/md/bcache/writeback.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/writeback.c
From: Geert Uytterhoeven ge...@linux-m68k.org
drivers/md/bcache/btree.c: In function ‘bch_btree_node_read’:
drivers/md/bcache/btree.c:259: warning: format ‘%lu’ expects type ‘long
unsigned int’, but argument 3 has type ‘size_t’
Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org
GFP_NOIO means we could be getting called recursively - mca_alloc() -
mca_data_alloc() - definitely can't use mutex_lock(bucket_lock) then.
Whoops.
Signed-off-by: Kent Overstreet k...@daterainc.com
Cc: linux-stable sta...@vger.kernel.org # = v3.10
---
drivers/md/bcache/btree.c | 2 +-
1 file
Hi,
Adding Russell and l.a.k ML.
Another question: is this linked to the following build warning?
CC arch/arm/kernel/return_address.o
arch/arm/kernel/return_address.c:63:2: warning: #warning TODO:
return_address should use unwind tables
Regards,
Jean
On 24 September 2013 07:23, Anurag
Hi Jean,
I don't think that it is related to the warning that you have suggested
On Tue, Sep 24, 2013 at 11:58 AM, Jean Pihet jean.pi...@linaro.org wrote:
Hi,
Adding Russell and l.a.k ML.
Another question: is this linked to the following build warning?
CC
On 04/12/2013 04:27 AM, Steven Rostedt wrote:
On linux with stable kernel v3.4.39, when this patch (ipv6: fix bad free
of addrconf_init_net) is applied. Then I run the following commands:
1. the default value of ipv6 forwarding is 0
2. we change it to 1 firstly via:
# vi /etc/sysctl.conf
we are donating £1.5 Million Pounds to you to help the Less Privileged in our
ongoing lucky draws donations. Please get back to us with your Name, Age, Tel,
Country and i will send you more details how your funds will be sent to
you.Please read the article -
From d4eb97e8d5def76d46167c91059147e2c7d33433 Mon Sep 17 00:00:00 2001
When using PTP_SYS_OFFSET ioctl to measure the time offset between the
PHC and system clock, we need to specify the number of measurements, the
valid value of n_samples is between 1 to 25. If n_samples = 0 or 25
it makes no
Hi James,
Can you please help to review the patch and comment it?
Thanks,
Joe
On 09/20/13 08:16, Joe Jin wrote:
When do disk pull/insert test we encountered below:
WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0xbc/0xe0()
Hardware name: SUN FIRE X4370 M2 SERVER
sysfs: cannot create
Hi all,
I have couple of build warnings. Not sure if this happened with rc1, as I
only have moved across to the rc trees:
gcc (GCC) 4.2.4 on amd64 - no modules build:
1)
...
GEN lib/crc32table.h
CC lib/crc32.o
lib/crc32.c: In function ‘crc32_be’:
lib/crc32.c:263: warning:
On 09/23/2013 05:33 PM, Maarten Lankhorst wrote:
Hey,
Op 13-09-13 11:00, Peter Zijlstra schreef:
On Fri, Sep 13, 2013 at 10:41:54AM +0200, Daniel Vetter wrote:
On Fri, Sep 13, 2013 at 10:29 AM, Peter Zijlstra pet...@infradead.org wrote:
On Fri, Sep 13, 2013 at 09:46:03AM +0200, Thomas
* Christoph Lameter c...@linux.com wrote:
These location triggered during testing with KVM.
These are fetches without preemption off where we judged that
to be more performance efficient or where other means of
providing synchronization (BH handling) are available.
Signed-off-by:
(netdev Cc:-ed)
* Christoph Lameter c...@linux.com wrote:
These location triggered during testing with KVM.
These are fetches without preemption off where we judged that
to be more performance efficient or where other means of
providing synchronization (BH handling) are available.
* Christoph Lameter c...@linux.com wrote:
Index: linux/kernel/hrtimer.c
===
--- linux.orig/kernel/hrtimer.c 2013-09-12 13:26:29.216103951 -0500
+++ linux/kernel/hrtimer.c2013-09-12 13:26:29.212103994 -0500
@@ -538,7
Op 24-09-13 09:22, Thomas Hellstrom schreef:
On 09/23/2013 05:33 PM, Maarten Lankhorst wrote:
Hey,
Op 13-09-13 11:00, Peter Zijlstra schreef:
On Fri, Sep 13, 2013 at 10:41:54AM +0200, Daniel Vetter wrote:
On Fri, Sep 13, 2013 at 10:29 AM, Peter Zijlstra pet...@infradead.org
wrote:
On Fri,
On 09/24/2013 12:11 AM, Joe Perches wrote:
There are a mix of function prototypes with and without extern
in the kernel sources. Standardize on not using extern for
function prototypes.
Function prototypes don't need to be written with extern.
extern is assumed by the compiler. Its use is
Hi,
On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130923 10:09]:
On 09/23/2013 06:45 PM, Tony Lindgren wrote:
Hmm does this still work for legacy platform data based
drivers that are doing gpio_request() first?
Yes it
* Christoph Lameter c...@linux.com wrote:
We do not care about races for the expiration logic in
refresh_cpu_vm_stats(). Draining is a rare act after all.
No need to create too much overhead for that.
Use raw_cpu_ops there.
Signed-off-by: Christoph Lameter c...@linux.com
Index:
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/pinctrl/pinctrl-adi2.c | 38 ++
1 file changed, 6 insertions(+), 32 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-adi2.c b/drivers/pinctrl/pinctrl-adi2.c
index 7a24e59..f2aa877 100644
---
Current code hold port-lock spinlock and then try to grab the lock again
in adi_gpio_set_value(). Fix it.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/pinctrl/pinctrl-adi2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-adi2.c
Hm, do you test-build your patches? This series produces the following
annoying warning:
arch/x86/platform/uv/uv_nmi.c: In function ‘uv_nmi_setup’:
arch/x86/platform/uv/uv_nmi.c:664:2: warning: the address of ‘uv_nmi_cpu_mask’
will always evaluate as ‘true’ [-Waddress]
This:
On 09/24/2013 09:39 AM, Sricharan R wrote:
Hi,
On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130923 10:09]:
On 09/23/2013 06:45 PM, Tony Lindgren wrote:
Hmm does this still work for legacy platform data based
drivers
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully configured/enabled as an IRQ if a driver solely
uses IRQ APIs such
Le 20/09/2013 23:22, Scott Wood a écrit :
The hardware wants to decrement; why fight it?
I see your point.
However it is not clear in the documentation if the decrement is done
really after the update, or at xTLB interrupt. So I propose to still set
the CTR ourself as described in the
On Tue, Sep 24, 2013 at 07:52:06AM +0200, Knut Petersen wrote:
Hi Daniel!
This patch is definitely needed for 3.12, but it is still missing in 3.12-rc2
...
Oops, that one fell through the cracks. Applied to -fixes, thanks for
poking.
-Daniel
cu,
Knut
On 10.09.2013 11:44, Daniel
* Christoph Lameter c...@linux.com wrote:
--- linux.orig/kernel/sched/core.c2013-09-23 10:24:47.371629684 -0500
+++ linux/kernel/sched/core.c 2013-09-23 10:24:47.371629684 -0500
@@ -2566,6 +2566,29 @@ asmlinkage void __sched preempt_schedule
exception_exit(prev_state);
}
On Tue, Sep 24, 2013 at 11:52:07AM +1000, Benjamin Herrenschmidt wrote:
So if that holds, we have a solid way to do per-cpu. On one side, I tend
to think that r13 being task/thread/thread_info is probably a better
overall choice, I'm worried that going in a different direction than x86
means
now the leds-gpio driver will create every child led node without
checking the status is disabled or not.
for example, if we have a led node like d3, and its status is disabled:
leds {
d3 {
label = d3;
gpios = pioE 24 0;
On Mon, Sep 23, 2013 at 08:05:23PM +0200, Stephen Warren wrote:
On 09/18/2013 08:40 AM, Peter De Schrijver wrote:
Many clocks are common between several Tegra SoCs. Define an enum to list
them so we can move them to separate files which can be shared between
SoCs. Each SoC specific file
On Mon, Sep 23, 2013 at 02:18:27PM -0700, Paul E. McKenney wrote:
Passes light testing, but I am confused about why the change to
resched_task() when only resched_cpu() is invoked elsewhere in the patch.
Enlightenment?
-#ifdef CONFIG_SMP
void resched_task(struct task_struct *p)
{
The TMU data definition is now separated to Exynos4412 and Exynos5250.
Now SOC_ARCH_EXYNOS only refers to Exynos5250. Hence the name
SOC_ARCH_EXYNOS has been changed to SOC_ARCH_EXYNOS5250.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_tmu.c |
The commit d0a0ce3e77c795258d47f9163e92d5031d0c5221 (thermal: exynos: Add
missing definations and code cleanup) has removed setting of test MUX address
value at TMU configuration setting.
This field is not present on Exynos4210 and Exynos5 SoCs. However on Exynos4412
SoC it is required to set
The TMU device tree node definition for Exynos4x12 family of SoCs.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos4x12.dtsi | 10 ++
1 file
Hi Boris,
On Mon, 23 Sep 2013 11:26:59 +0200, Borislav Petkov wrote:
On Mon, Sep 23, 2013 at 06:15:09PM +0900, Namhyung Kim wrote:
I replaced them to a single -w option since all we want to do is
suppress any warning, right?
Do we? And besides, -w is a big hammer as it shuts up all warnings.
This patch enables support for TMU at Exynos4412 based Trats2 board.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos4412-trats2.dts |5 +
1 file
This patch series is divided into two parts:
1. Device tree node definition and enabelement for TMU at Exynos4412 (Trats2)
2. Exynos thermal subsystem regressions for v3.12-rc1. Several commits were
necessary to properly fix regression for TMU test MUX address setting after
reset.
Test HW:
The commit 4de0bdaa9677d11406c9becb70c60887c957e1f0
(thermal: exynos: Add support for instance based register/unregister)
broke check for presence of therm_dev at global thermal zone in
exynos_report_trigger().
The resulting wrong test prevents thermal_zone_device_update() call, which
calls
Up till now Exynos5250 and Exynos4412 had the same definitions for TMU
data. Following commit changes that, by introducing separate
exynos4412_default_tmu_data structure.
Since Exynos4412 was chronologically first, the corresponding name for
TMU registers and default data was renamed.
On 09/23/2013 06:40 PM, Mark Rutland wrote:
Hi Eduardo,
Apologies for having taken so long to get back you on this.
I have several comments on the binding and the way it's parsed.
On Wed, Sep 18, 2013 at 10:35:36PM +0100, Eduardo Valentin wrote:
This patch introduces a device tree bindings
Thanks Stephen,
On 23/09/13 21:40, Stephen Warren wrote:
On 09/19/2013 02:59 AM, Srinivas KANDAGATLA wrote:
This patch adds support to ST RC driver, which is basically a IR/UHF
receiver and transmitter. This IP (IRB) is common across all the ST
parts for settop box platforms. IRB is embedded
[ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
This series adds the ability to specify a GPIO and a power supply to
enable a backlight.
Patch 1 refactors the power on and power off sequences into
* Mike Travis tra...@sgi.com wrote:
This patch adds a kgdb_nmicallin() interface that can be used by
external NMI handlers to call the KGDB/KDB handler. The primary need
for this is for those types of NMI interrupts where all the CPUs
have already received the NMI signal. Therefore no
On Tue, 2013-09-24 at 10:04 +0200, Peter Zijlstra wrote:
On Tue, Sep 24, 2013 at 11:52:07AM +1000, Benjamin Herrenschmidt wrote:
So if that holds, we have a solid way to do per-cpu. On one side, I tend
to think that r13 being task/thread/thread_info is probably a better
overall choice, I'm
Activating CONFIG_PIN_TLB is supposed to pin the IMMR and the first three
8Mbytes pages. But the setting of MD_CTR to a pinnable entry was missing before
the pinning of the third 8Mb page. As the index is decremented module 28
(MD_RSV4D is set) after every DTLB update, the third 8Mbytes page was
On Mon, Sep 23, 2013 at 08:31:43PM +0200, Stephen Warren wrote:
On 09/18/2013 08:41 AM, Peter De Schrijver wrote:
Introduce a new file for peripheral clocks common between several Tegra
SoCs and move Tegra114 to this new infrastructure. Also PLLP and the
PLLP_OUT
clocks will be
* Maarten Lankhorst maarten.lankho...@canonical.com wrote:
I think the Nouveau guys need to comment further on this, but
returning -EFAULT might break existing user-space, and that's not
allowed, but IIRC the return value of presumed is only a hint, and
if it's incorrect will only
On Tue, Sep 24, 2013 at 06:16:53PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-24 at 10:04 +0200, Peter Zijlstra wrote:
On Tue, Sep 24, 2013 at 11:52:07AM +1000, Benjamin Herrenschmidt wrote:
So if that holds, we have a solid way to do per-cpu. On one side, I tend
to think that
On Mon, Sep 23, 2013 at 10:12 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/23/2013 01:53 PM, Linus Walleij wrote:
I think the kernel should prevent such things.
It might be nice if it could do that.
However, that is 100% unrelated to the problem at hand.
I don't think it is
On Mon, Sep 23, 2013 at 10:21 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/23/2013 02:01 PM, Linus Walleij wrote:
And how to you block the same line from being gpio_request()ed
and set as output?
To be honest, I really don't think this problem is terribly likely to
occur, so I'm
On Mon, Sep 23, 2013 at 08:34:48PM +0200, Stephen Warren wrote:
On 09/18/2013 08:41 AM, Peter De Schrijver wrote:
Introduce a new file for fixed clocks common between several Tegra
SoCs and move Tegra114 to this new infrastructure.
diff --git a/drivers/clk/tegra/clk-tegra-fixed.c
On Fri, Sep 20, 2013 at 09:54:07AM -0700, Darrick J. Wong wrote:
On Fri, Sep 20, 2013 at 09:28:07AM +0100, Mel Gorman wrote:
On Fri, Sep 20, 2013 at 09:06:37AM +0100, Mel Gorman wrote:
On Thu, Sep 19, 2013 at 08:06:02PM -0700, Darrick J. Wong wrote:
The force parameter in
Commit-ID: 1e019421bca68cfae1a61a09d9d49cf6a9e2143b
Gitweb: http://git.kernel.org/tip/1e019421bca68cfae1a61a09d9d49cf6a9e2143b
Author: Mike Travis tra...@sgi.com
AuthorDate: Mon, 23 Sep 2013 16:25:00 -0500
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:02:02
Commit-ID: 12ba6c990fab50fe568f3ad8715e81e356552428
Gitweb: http://git.kernel.org/tip/12ba6c990fab50fe568f3ad8715e81e356552428
Author: Mike Travis tra...@sgi.com
AuthorDate: Mon, 23 Sep 2013 16:25:03 -0500
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:02:03
Commit-ID: 8eba18428ac926f436064ac281e76d36d51bd631
Gitweb: http://git.kernel.org/tip/8eba18428ac926f436064ac281e76d36d51bd631
Author: Mike Travis tra...@sgi.com
AuthorDate: Mon, 23 Sep 2013 16:25:06 -0500
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:02:04
Commit-ID: 3c121d9a21dc16ef030ad6ca3ebb159b5726fab9
Gitweb: http://git.kernel.org/tip/3c121d9a21dc16ef030ad6ca3ebb159b5726fab9
Author: Mike Travis tra...@sgi.com
AuthorDate: Mon, 23 Sep 2013 16:25:02 -0500
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:02:03
Commit-ID: 8a1f4653f27ffd5d61088cf6b95c39bb13bf6132
Gitweb: http://git.kernel.org/tip/8a1f4653f27ffd5d61088cf6b95c39bb13bf6132
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Tue, 24 Sep 2013 09:52:40 +0200
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:52:40
Commit-ID: 0d12ef0c900078cc1f4e78dff2245521aa5d0c89
Gitweb: http://git.kernel.org/tip/0d12ef0c900078cc1f4e78dff2245521aa5d0c89
Author: Mike Travis tra...@sgi.com
AuthorDate: Mon, 23 Sep 2013 16:25:01 -0500
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Sep 2013 09:02:02
On Tuesday 24 September 2013 01:24 PM, Javier Martinez Canillas wrote:
On 09/24/2013 09:39 AM, Sricharan R wrote:
Hi,
On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130923 10:09]:
On 09/23/2013 06:45 PM, Tony Lindgren
On Mon, Sep 23, 2013 at 01:34:05PM -0700, Joe Perches wrote:
Maybe adding a mechanism to MAINTAINERS would be better.
Maybe a default B: (backport?) of sta...@vger.kernel.org
with a per-subsystem override?
Sounds fine to me.
--
To unsubscribe from this list: send the line unsubscribe
Han Pingtian found a typo in Documentation/kernel-parameters.txt
about kernelcore=, that kernelcore should be replaced with Movable here.
I sent this patch a 8 months ago and got ack from Mel Gorman,
http://marc.info/?l=linux-mmm=135756720602638w=2
but it has not been merged so I resent it again.
Hi Linus,
On 09/24/2013 03:22 AM, Linus Torvalds wrote:
On Mon, Sep 23, 2013 at 5:04 PM, Davidlohr Bueso davidl...@hp.com wrote:
Ok, so here's the code - again I've tested it with LTP on the resources
I have.
This looks good to me.
Manfred, mind giving this a look-over and see if this
On Wed, Sep 18, 2013 at 12:39:16AM +0200, Lubomir Rintel wrote:
Superblock lock was replaced with (un)lock_super() removal, but left
uninitialized for Seventh Edition UNIX filesystem in the following commit
(3.7):
c07cb01 sysv: drop lock/unlock super
Signed-off-by: Lubomir Rintel
On Wed, Sep 18, 2013 at 09:33:04AM +0200, Gerd Hoffmann wrote:
While being at it rename the list head from list to work, preparing
for the addition of a second list.
Why do you even the list?
The list was already there when I took over maintainance ...
What would a ordered
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c |6
Add information about the USB OTG PHY. Without this
the OTG port on beagle will not work.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
Use a common naming scheme mode0name.modename flags for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 24
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git
Hi Simon,
# I had added wrong From:, sorry.
With this in mind I believe the strings should be:
- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2
Thank you for pointed it out. I'll fix it in v2.
To be honest I am not quite sure about the -clkdiv and -gclk
Neither am
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 26 ++
1 files changed, 2 insertions(+), 24 deletions(-)
diff --git
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver. Update
the device tree binding information.
This also makes us easy to migrate
Hin
On 17 September 2013 12:29, Will Deacon will.dea...@arm.com wrote:
Arnaldo, Ingo,
On Mon, Sep 16, 2013 at 10:17:32AM +0100, Jean Pihet wrote:
The newly added dwarf unwinding feature [1] requires:
. a recent version (= 1.1) of libunwind,
. libunwind to be configured with
On 09/24/13 at 01:23pm, Dave Young wrote:
On 09/24/13 at 12:58pm, Dave Young wrote:
On 09/24/13 at 12:57pm, Dave Young wrote:
On 09/23/13 at 08:06pm, H. Peter Anvin wrote:
Okay... I see two problems.
1. It looks like we subtract the region size after, rather than before,
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/usb-host.c | 11 +--
1 files changed, 1 insertions(+), 10 deletions(-)
diff --git
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +-
1 files changed, 1 insertions(+), 17 deletions(-)
diff --git
On Mon, Sep 23, 2013 at 12:21:30PM +0200, Thomas Richter wrote:
Hi folks,
Can you please test with
Option LinearFramebuffer true?
Thanks, Daniel
Tested again. Yes, indeed, LinearFramebuffer does make a difference.
Without it, panning to the right causes flicker, with it,
On Tue, Sep 24, 2013 at 05:14:46PM +0900, Simon Horman wrote:
[ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
This series adds the ability to specify a GPIO and a power supply to
enable a backlight.
The GPIO number of the RESET line can be passed to the
driver using the gpio_reset member.
Signed-off-by: Roger Quadros rog...@ti.com
---
include/linux/usb/usb_phy_gen_xceiv.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/include/linux/usb/usb_phy_gen_xceiv.h
Hi all,
On 09/24/2013 02:04 AM, Davidlohr Bueso wrote:
(In reality, I suspect the reference count is never elevated in
practice, so there is only one case that calls the security freeing
thing, so this may all be pretty much theoretical, but at least from a
logic standpoint the code clearly
On 09/24/2013 09:34 AM, Maarten Lankhorst wrote:
Op 24-09-13 09:22, Thomas Hellstrom schreef:
On 09/23/2013 05:33 PM, Maarten Lankhorst wrote:
Hey,
Op 13-09-13 11:00, Peter Zijlstra schreef:
On Fri, Sep 13, 2013 at 10:41:54AM +0200, Daniel Vetter wrote:
On Fri, Sep 13, 2013 at 10:29 AM,
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/adp8860_bl.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/video/backlight/adp8860_bl.c
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/adp5520_bl.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/video/backlight/adp5520_bl.c
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/aat2870_bl.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/video/backlight/aat2870_bl.c
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/adp8870_bl.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/video/backlight/adp8870_bl.c
Use devm_backlight_device_register() to make cleanup paths simpler,
and remove unnecessary remove().
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/88pm860x_bl.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git
Use devm_backlight_device_register() to make cleanup paths simpler,
and remove unnecessary remove().
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/as3711_bl.c | 26 +-
1 file changed, 5 insertions(+), 21 deletions(-)
diff --git
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/atmel-pwm-bl.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/video/backlight/atmel-pwm-bl.c
1 - 100 of 1898 matches
Mail list logo
