of_find_node_by_name() returns a node pointer with refcount
incremented, use of_node_put() on it when done.
of_find_node_by_name() will call of_node_put() against
the node pass to from parameter, thus we also need to call
of_node_get(from) before calling of_find_node_by_name().
Signed-off-by:
From: Ajay Kumar ajaykumar...@samsung.com
disable_irq() should be moved to exynos_dp_suspend(), because
enable_irq() is called at exynos_dp_resume().
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/exynos/exynos_dp_core.c |4
Hi Eric,
Today's linux-next merge of the userns tree got a conflict in
net/sunrpc/svcauth_unix.c between commit 2d4383383b0b (SUNRPC: rework
cache upcall logic) from the nfsd tree and commit 7eaf040b720b (sunrpc:
Use kuid_t and kgid_t where appropriate) from the userns tree.
I fixed it up (see
Hi Wim,
This code not only converts the watchdog to the new framework,
but it also adds the is_enable related code changes which should
be a seperate patch.
So I took your original patch and changed it to the below at91sam9_wdt
watchdog conversion patch. Note: this is also without Fabio's
Please don't send update emails to me
Whenever I need I can check from website
Thanks Regards
Chun-Shian Tsai
- Original Message -
From: Kumar, Anil anilkuma...@ti.com
To: linux-watch...@vger.kernel.org; linux-kernel@vger.kernel.org;
Hi Wim
I rather have this after the conversion of the watchdog to the new framework.
Thanks a lot.
OK , I will do it later.
Best Regards,
Wenyou Yang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
Hi,
I'm working on Android Linux Kernel (version 3.4) and seeing a
deadlock in the ashmem driver, while handling mmap request.
I seek your support to fix the same. The locks that involved in the
dead lock are
1) mm-mmap_sem
2) ashmem_mutex
The following is the sequence of events that leads to the
On 02/17/13 17:39, Amnon Shiloh wrote:
Hello,
The code in kernel/sys.c provides the prctl(PR_SET_MM) function,
which is the only way a process can set or modify the following 11
per-process fields:
start_code, end_code, start_data, end_data, start_brk, brk,
start_stack,
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
kernel/timeconst.pl between commit 70730bca1331 (kernel: Replace
timeconst.pl with a bc script) from the kbuild tree and commit
timeconst.pl: remove deprecated defined(@array) from the akpm tree.
I just dropped the akpm tree
On 01/29/2013 05:08 PM, Michael Wang wrote:
v3 change log:
Fix small logical issues (Thanks to Mike Galbraith).
Change the way of handling WAKE.
This patch set is trying to simplify the select_task_rq_fair() with
schedule balance map.
After get rid of the complex code and
On Sat, Feb 16, 2013 at 12:14:49AM -0500, Nicolas Pitre wrote:
On Fri, 15 Feb 2013, Russell King - ARM Linux wrote:
On Thu, Feb 14, 2013 at 11:47:50PM +0100, Arnd Bergmann wrote:
Patch c08e20d24 arm: Add v7_invalidate_l1 to cache-v7.S
moves the v7_invalidate_l1 symbol out of
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc44x_defconfig) produced this warning:
net/ipv6/xfrm6_mode_tunnel.c: In function 'xfrm6_mode_tunnel_input':
net/ipv6/xfrm6_mode_tunnel.c:72:2: warning: suggest parentheses around
assignment used as truth value
On Sunday 17 February 2013 04:08 AM, Anton Vorontsov wrote:
[...]
supplied nodes sounds confusing (doesn't reflect direction), IMO. I'd
rather call it power-supply,supplied-to = some_battery;
But... I'm recalling there was a similar discussion not that long ago, and
Arnd came up with the
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 (cgroup: fix lockdep
warning for event_control) solved a deadlock by introducing a new
bug.
Move cgrp-event_list to a temporary list doesn't mean you can traverse
this list locklessly, because at the same time cgroup_event_wake() can
be called and
If we pass fd of memory.usage_in_bytes of cgroup A to cgroup.event_control
of cgroup B, then we won't get memory usage notification from A but B!
What's worse, if A and B are in different mount hierarchy, we'll end up
accessing NULL pointer!
Disallow this kind of invalid usage.
Signed-off-by:
Andrew Morton a...@linux-foundation.org writes:
The syscall should handle the common usages very well. But it
shouldn't handle uncommon usages very badly!
If the user is actually dealing with the contents of the file, following
the established mincore is preferred, since it's in the noise
On 13/02/13 04:15, Alex Williamson wrote:
On Wed, 2013-02-13 at 01:42 +1100, Alexey Kardashevskiy wrote:
On 12/02/13 16:07, Alex Williamson wrote:
On Tue, 2013-02-12 at 15:06 +1100, Alexey Kardashevskiy wrote:
Having this patch in a tree, adding new nodes in sysfs
for IOMMU groups is going to
于 2013年02月16日 05:39, Julian Anastasov 写道:
Hello,
On Thu, 14 Feb 2013, Andrew Morton wrote:
On Thu, 7 Feb 2013 10:40:26 +0200 (EET)
Julian Anastasov j...@ssi.bg wrote:
Another question about the sysctl_sync_qlen_max:
This variable is assigned as:
ipvs-sysctl_sync_qlen_max =
On Monday, 18 February 2013 06:10:02 UTC+8, Jiri Slaby wrote:
Hi,
You still feel the sour taste of the kswapd craziness in v3.7 thread,
right? Welcome to the hell, part two :{.
I believe this started happening after update from
3.8.0-rc4-next-20130125 to 3.8.0-rc7-next-20130211. The same
-Original Message-
From: Rafael J. Wysocki [mailto:r...@sisk.pl]
Sent: Friday, February 15, 2013 1:38 AM
To: Miklos Szeredi
Cc: Pavel Machek; Goswin von Brederlow; Li, Fei; Brown, Len;
mi...@redhat.com; pet...@infradead.org; Wang, Biao;
linux...@vger.kernel.org;
linux/mmzone.h included linux/memory_hotplug.h,
and linux/memory_hotplug.h also included
linux/mmzone.h, so there's a bad cirlular.
these are quite mechanical changes by a simple
script, I've tested for ARCH x86,arm,mips,
may someone help to test more.
Signed-off-by: liguang
Hi,
This series adds minimal support to boot Linux on platforms having
AM43 based SoC's.
This is being sent as an RFC to seek opinion about modification in
twd to register percpu local timer clock event for scheduler tick in
the case of one core SMP.
AM43 SoC's are based on ARM Cortex-A9. It is
Return percpu clock event on local timer register. It is the boot cpu
that calls this and it can use the returned percpu clock event to
register a clock event in the case of SMP configuration with one core.
This helps to have a booting Kernel even if no other timer is
registered for clock tick.
Selecting DEBUG_AM33XXUART1 routes low level debug messages to first
UART instance of AM335x based SoC's. This selection is valid for
upcoming AM43 based SoC's too. Make this information available upon
configuring.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/Kconfig.debug | 3 +++
1
Add Kconfig option for AM43 family of SoC's, these are ARM Cortex A9
based (SMP configuration with 1 core).
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/Kconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/mach-omap2/Kconfig
AM43 SoC is in pre-silicon stage, meanwhile it has been modelled in
a pre-silicon platform. To validate and boot Linux in pre-silicon
platform that emulates an AM43 SoC, add DT build support.
As bootloader is not used, bootargs is passed through DT.
Note: This would be replaced by an original
Add an optional property to find clock-frequency from DT. This helps
as a fallback mechanism in case there is no representation of clock
tree in DT.
Signed-off-by: Afzal Mohammed af...@ti.com
---
Documentation/devicetree/bindings/arm/twd.txt | 7 ++-
arch/arm/kernel/smp_twd.c
DT source (minimal) for AM4372 SoC. Those represented here are the
minimal DT nodes necessary to get kernel booting.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/boot/dts/am4372.dtsi | 55 +++
1 file changed, 55 insertions(+)
create mode 100644
Describe minimal DT boot machine details for AM43 based SoC's. AM43
family of SoC's are ARM Cortex-A9 based with one core in SMP
configuration. Low level debug could be achieved by selecting
DEBUG_AM33XXUART1. To boot AM43 SoC, this change is sufficient w.r.t
Kernel (considering the fact that
Register percpu local timer for scheduler tick in the case of one core
SMP configuration. In other cases - secondary cpu's as well as boot
cpu's having more than one core, this is being registered as per
existing boot flow, with a difference that they happens after delay
calibration. Registering
That is the right fix indeed.
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
Today's linux-next merge of the tip tree got a conflict in
kernel/timeconst.pl between commit 70730bca1331 (kernel: Replace
timeconst.pl with a bc script) from the kbuild tree and commit
63a3f603413f
A Regulator can be enabled by external GPIO pin.
This is configurable in the regulator_config.
At this moment, the GPIO can be owned by only one regulator device.
In some devices, multiple regulators are enabled by shared one GPIO pin.
This patch extends this limitation, enabling shared
A Regulator can be enabled by external GPIO pin which is configurable in the
regulator_config.
At this moment, the GPIO can be owned by only one regulator device.
In some devices like LP8788 LDOs, multiple regulators are enabled by shared
one GPIO pin.
This patch-set enables shared enable GPIO
Regulator core driver provides enable GPIO control for enabling/disabling a
regulator. Now, enable GPIO is shared among regulators.
Use this internal working, so unnecessary code are removed.
GPIO enable pin configurations are added in digital LDO and analog LDO drivers.
Signed-off-by:
To support shared enable GPIO pin, replace GPIO code with new static functions
Reference count: 'enable_count'
Balance the reference count of each GPIO and actual pin control.
The count is incremented with enabling GPIO.
On the other hand, it is decremented on disabling GPIO.
Actual
The regulator_dev has regulator_enable_gpio structure.
'ena_gpio' and 'ena_gpio_invert' were moved to in regulator_enable_gpio.
regulator_dev --- regulator_enable_gpio
.ena_gpio .gpio
.ena_gpio_invert .ena_gpio_invert
Pointer, 'ena_pin' is used for checking valid
I've requested a digital image or screen capture of the panic. Is
there any additional debug information you thing would be helpful?
Thanks,
Joe
On Sun, Feb 17, 2013 at 10:13 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
On 02/17/2013 04:44 AM, Tanaka Takahisa wrote:
Hi Joseph,
Hi,
On Sat, Feb 16, 2013 at 06:46:53AM -0800, Simon Glass wrote:
Hi,
On Sat, Feb 16, 2013 at 1:06 AM, Felipe Balbi ba...@ti.com wrote:
On Fri, Feb 15, 2013 at 08:16:09PM -0800, Simon Glass wrote:
This uses an I2C bus to talk to the ChromeOS EC. The protocol
is defined by the EC and is
On Sunday 17 of February 2013 10:54:20 J. Bruce Fields wrote:
On Fri, Feb 15, 2013 at 08:33:14PM +0100, Paweł Sikora wrote:
On Tuesday 12 of February 2013 15:52:17 J. Bruce Fields wrote:
On Sun, Jan 20, 2013 at 05:51:12PM -0500, Mark Lord wrote:
Got it again, this time on a different
On 02/18/2013 01:07 PM, Alex Shi wrote:
Since the simplification of fork/exec/wake balancing has much arguments,
I removed that part in the patch set.
This patch set implement/consummate the rough power aware scheduling
proposal: https://lkml.org/lkml/2012/8/13/139.
Just review the great
The size of de/compress buffer is small enough to use kmalloc.
Allocating it with kmalloc rather than vmalloc is preferred.
This patch depends on my previous patch, “btrfs: fix decompress buffer size”.
v2: Using vmalloc for workspace-mem due to the size limit.
Signed-off-by: Kyungsik Lee
601 - 641 of 641 matches
Mail list logo
