On 12/14/2012 01:11 AM, Yinghai Lu wrote:
> On Thu, Dec 13, 2012 at 1:36 PM, H. Peter Anvin wrote:
>>
>> : tazenda 111 ; qemu-kvm -smp 2 -m 2048 -hda ~/qemu/fc10/qemu-fc10-64.img
>> -serial stdio -kernel o.x86_64/arch/x86/boot/bzImage -append 'ro
>> root=/dev/sda1 console=ttyS0
On Fri, Dec 14, 2012 at 02:33:34PM +1100, Dave Chinner wrote:
> On Thu, Dec 13, 2012 at 06:10:49PM -0800, Darrick J. Wong wrote:
> > On Thu, Dec 13, 2012 at 05:48:06PM -0800, Andy Lutomirski wrote:
> > > On 12/13/2012 12:08 AM, Darrick J. Wong wrote:
> > > > Several complaints have been received
On 12/14/2012 03:37 AM, Michal Hocko wrote:
> On Thu 13-12-12 23:50:30, Johannes Weiner wrote:
>> On Thu, Dec 13, 2012 at 10:25:43PM +, Satoru Moriya wrote:
>>>
>>> I introduced swappiness check here with fe35004f because, in some
>>> cases, we prefer OOM to swap out pages to detect problems
On 2012-12-14 04:15, Shaohua Li wrote:
> In MD raid case, discard granularity might not be power of 2, for example, a
> 4-disk raid5 has 3*chunk_size discard granularity. Correct the calculation for
> such cases.
Thanks Shaohua, applied both.
--
Jens Axboe
--
To unsubscribe from this list:
Silicon does not support standard AHCI BAR assignment. Add
vendor/device exception to force BAR 2.
Signed-off-by: Hugh Daschbach
---
drivers/ata/ahci.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 7862d17..3cb008f 100644
---
> The "don't enqueue stuff" semantics of K_OFF shouldn't be a function of
> the keyboard map state; we should be able to switch among cooked/raw/
> unicode without changing whether events are delivered. Otherwise - if
> changing to K_UNICODE undoes K_OFF - then suddenly Alt-F2 under
> Gnome will
On Fri, Dec 14, 2012 at 01:42:00PM -0500, Dave Hansen wrote:
> I think the "Kernel Hacking" menu has gotten a bit out of hand. It
> is over 120 lines long on my system with everything enabled and
> options are scattered around it haphazardly.
>
>
On Fri, Dec 14, 2012 at 9:30 AM, Alan Cox wrote:
>> We can make this feature (passing O_DENY* flags received from clients
>> to filesystem) can be turned on/off on Samba/NFS server to let this
>> particular use case work. In general, I think we really need to be
>> sure that nobody has a read
for-james-20121214
for you to fetch changes up to e93072374112db9dc86635934ee761249be28370:
Smack: create a sysfs mount point for smackfs (2012-12-14 10:57:23 -0800)
Casey Schaufler (2):
Smack: use select not depends in Kconfig
Fix name of slink binding and address of sflash example to make it
self consistent.
Change-Id: Ia89c3017c958bdf670036caf516eabce6f893096
Signed-off-by: Allen Martin
---
Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt |2 +-
* Julia Lawall [121103 13:32]:
> From: Julia Lawall
>
> Just use WARN_ON rather than an if containing only WARN_ON(1).
Thanks applying this one into omap-for-v3.8/fixes-for-merge-window.
Regards,
Tony
> A simplified version of the semantic patch that makes this transformation
> is as
The pty driver does not obtain an ldisc reference to the linked
tty when writing. When the ldiscs are sequentially halted, it
is possible for one ldisc to be halted, and before the second
ldisc can be halted, a concurrent write schedules buffer work on
the first ldisc. This can lead to an
In order to safely call tty_ldisc_flush_works(), the ldisc must
already have been halted, so any pending buffer work has already
been cancelled or flushed as part of the halt.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On 12/14/2012 10:44 AM, Andy Lutomirski wrote:
>>
>> mremap() should work. At the same time, the code itself is not going to
>> have any stability guarantees between kernel versions -- it obviously
>> cannot.
>
> We could guarantee that the symbols in the vdso resolve to particular
> offsets
On Fri, Dec 14, 2012 at 10:43 AM, Linus Torvalds
wrote:
> On Fri, Dec 14, 2012 at 10:12 AM, Eric W. Biederman
> wrote:
>>
>> That said Serge I think I have lost track of the point of your question.
>
> .. and I'm a bit unsure what I should do about this all. Including
> pulling the pull request
On Fri, Dec 14, 2012 at 10:35 AM, H. Peter Anvin wrote:
> On 12/14/2012 12:34 AM, Pavel Emelyanov wrote:
>> On 12/14/2012 06:20 AM, Andy Lutomirski wrote:
>>> On Thu, Dec 13, 2012 at 6:18 PM, H. Peter Anvin wrote:
Wouldn't the vdso get mapped already and could be mremap()'d. If we
>>>
Hi
On Fri, 14 Dec 2012, Tony Lindgren wrote:
> Paul, what about this patch? Looks like you've acked the other clock
> patches in this series but not this one?
I commented on it briefly here:
https://patchwork.kernel.org/patch/1838111/
Maybe Benoît could comment here, but it looks to me
On Fri, Dec 14, 2012 at 10:12 AM, Eric W. Biederman
wrote:
>
> That said Serge I think I have lost track of the point of your question.
.. and I'm a bit unsure what I should do about this all. Including
pulling the pull request that actually can make this all matter.
Hmm? Any consensus?
There are quite a few of these, and we want to make sure that
there is one-stop-shopping for lock debugging.
Signed-off-by: Dave Hansen
---
linux-2.6.git-dave/lib/Kconfig.debug | 120 ++-
1 file changed, 62 insertions(+), 58 deletions(-)
diff -puN
I think the "Kernel Hacking" menu has gotten a bit out of hand. It
is over 120 lines long on my system with everything enabled and
options are scattered around it haphazardly.
http://sr71.net/~dave/linux/kconfig-horror.png
Let's try to introduce some sanity.
--
To unsubscribe from this
Again, trying to come up with some common themes of the stuff in
the kernel hacking menu... There are quite a few options to
tweak compilation in some way, or perform extra compile-time
checks. Give them their own menu.
The diff here looks a bit funny... makes it look like I'm
moving debugfs
debugfs may have started out as a kernel hacking kind of option. But,
today, it is an integral part of lots of facilities like tracing that
are far from kernel hacking. Let's move it out of the very cluttered
"Kernel Hacking" menu and but it next to its real family: other
filesystems like
These runtime tests are great, except that there are a lot of them,
and they are very rarely needed. Give them their own menu so that
only the folks who need them will have to go looking for them.
Note that there are some other runtime tests that are not in here,
like for RCU or locking. This
These were in two different places, and taking up too much of my
valuable screen real-estate. Banish them to their own menu.
Signed-off-by: Dave Hansen
---
linux-2.6.git-dave/lib/Kconfig.debug | 160 +--
1 file changed, 82 insertions(+), 78 deletions(-)
diff
There are a *LOT* of memory debugging options. They are just scattered
all over the "Kernel Hacking" menu. Sure, "memory debugging" is a very
vague term and it's going to be hard to make absolute rules about what
goes in here, but this has to be better than what we had before.
This does,
Several architectures have similar stack debugging config options.
They all pretty much do the same thing, some with slightly
differing help text.
This patch changes the architectures to instead enable a Kconfig
boolean, and then use that boolean in the generic Kconfig.debug
to present the
On 12/14/2012 12:34 AM, Pavel Emelyanov wrote:
> On 12/14/2012 06:20 AM, Andy Lutomirski wrote:
>> On Thu, Dec 13, 2012 at 6:18 PM, H. Peter Anvin wrote:
>>> Wouldn't the vdso get mapped already and could be mremap()'d. If we
>> really need more control I'd almost push for a device/filesystem
* Samuel Ortiz [121213 16:57]:
> Hi Tony,
>
> On Thu, Dec 13, 2012 at 01:49:49PM -0800, Tony Lindgren wrote:
> > Hi Samuel,
> >
> > * Roger Quadros [121210 02:23]:
> > > Instead of using cpu_is_omap..() macros in the device driver we
> > > rely on information provided in the platform data.
> >
* Roger Quadros [121210 02:23]:
> There is no such clock as utmi_p1_gfclk. It is only a clock selector
> bit to select th the parent of usb_host_hs_utmi_p1_clk.
> So we get rid of utmi_p1_gfclk and utmi_p2_gfclk by merging them into
> usb_host_hs_utmi_p1_clk and usb_host_hs_utmi_p2_clk
On Wed, Dec 12, 2012 at 3:48 PM, David Howells wrote:
> H. Peter Anvin wrote:
>
>> The following changes since commit 7e5530af11be68f3109672aed59243f82e1272f0:
>>
>> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2012-12-02
>> 16:39:00 -0800)
>>
>> are available in the git
Factor out the packet mode status change for use by follow-on patch.
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c
index 3f704a9..41e58bf 100644
---
Signed-off-by: Peter Hurley
---
drivers/tty/pty.c| 3 ++-
drivers/tty/tty_buffer.c | 2 +-
drivers/tty/tty_io.c | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/pty.c b/drivers/tty/pty.c
index be6a373..baf52b4 100644
--- a/drivers/tty/pty.c
+++
A buffer flush is both undesirable and unnecessary when the ldisc
is closing. A buffer flush performs the following:
1. resets ldisc data fields to their initial state
2. resets tty->receive_room to indicate more data can be sent
3. schedules buffer work to receive more data
4. signals a
Flip buffer work must not be scheduled after the line discipline
has been halted; issue warning.
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 6 ++
drivers/tty/tty_buffer.c | 3 +++
drivers/tty/tty_ldisc.c | 45 +
In preparation for destructing and freeing the tty, the line discipline
must first be brought to an inactive state before it can be destructed.
This line discipline shutdown must:
- disallow new users of the ldisc
- wait for existing ldisc users to finish
- only then, cancel/flush their
Flip buffer work cannot be cancelled until all outstanding ldisc
references have been released. Convert the ldisc ref wait into
a full ldisc halt with buffer work cancellation.
Note that the legacy mutex is not held while cancelling.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 40
Refactor tty_ldisc_hangup() to extract standalone function,
tty_ldisc_hangup_wait_idle(), to wait for ldisc references
to be released.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 54 -
1 file changed, 36 insertions(+), 18
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 78c3000..3d2b6d7 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -1511,6 +1511,8 @@ static void
Since the tty->ldisc is prevented from being changed by tty_set_ldisc()
when a tty is being hung up, re-testing the ldisc user count is
unnecessary -- ie, it cannot be a different ldisc and the user count
cannot have increased (assuming the caller meets the precondition that
TTY_LDISC flag is
I wasn't sure if this is something to squeeze into 3.8, so don't yell
if not. At least Sasha can apply this and re-test against trinity.
Changes in v2:
- Please review "tty: Don't flush buffer when closing ldisc".
This patch replaces the earlier
"tty: Don't reschedule buffer work while
From: Konstantin Khlebnikov
Date: Fri, 14 Dec 2012 15:03:03 +0400
> mutex_destroy() must be called before wpan_phy_free(), because it puts the
> last
> reference and frees memory. Catched as overwritten poison in kmalloc-2048.
>
> Signed-off-by: Konstantin Khlebnikov
Applied.
--
To
On 12/14/2012 01:11 AM, Yinghai Lu wrote:
>
> attached works on kvm local, but SMP does not work yet.
>
SMP should be easy... it is probably just a matter of getting through
the trampoline sequence properly. I will look at this shortly.
-hpa
--
To unsubscribe from this list: send
From: Konstantin Khlebnikov
Date: Fri, 14 Dec 2012 15:02:51 +0400
> This patch fixes platform device drivers unregistering and adds proper error
> handing on module loading.
>
> Signed-off-by: Konstantin Khlebnikov
Applied.
--
To unsubscribe from this list: send the line "unsubscribe
From: Konstantin Khlebnikov
Date: Fri, 14 Dec 2012 15:02:55 +0400
> Bonding initializes these works in bond_open() and cancels in bond_close(),
> thus in bond_uninit() they are already canceled but may be unitialized yet.
>
> Signed-off-by: Konstantin Khlebnikov
Applied.
--
To unsubscribe
From: Konstantin Khlebnikov
Date: Fri, 14 Dec 2012 15:02:36 +0400
> Using timer_pending() without additional syncronization is racy,
> del_timer_sync() must be used here for waiting in-flight handler.
> Bug caught with help from "debug-objects" during random insmod/rmmod.
>
> Signed-off-by:
From: Jason Wang
Date: Fri, 14 Dec 2012 17:53:30 +0800
> The current multiqueue API is ambigious which may confuse both user and LSM to
> do things correctly:
>
> - Both TUNSETIFF and TUNSETQUEUE could be used to create the queues of a
> tuntap
> device.
> - TUNSETQUEUE were used to disable
* oleg.matcovs...@ti.com [121126 17:04]:
> From: Oleg Matcovschi
>
> OMAP_MODE_GPIO() macro verified only OMAP_MUX_MODE4.
> It is not correct for following platforms:
> 2430 - gpio mux mode 3
> 44xx - gpio mux mode 3
> 54xx - gpio mux mode 6
>
> Patch reserves first 3 bits in
"Serge E. Hallyn" writes:
> Quoting Eric W. Biederman (ebied...@xmission.com):
>> "Serge E. Hallyn" writes:
>>
>> > Quoting Eric W. Biederman (ebied...@xmission.com):
>> >> "Serge E. Hallyn" writes:
>> >>
>> >> > Quoting Eric W. Biederman (ebied...@xmission.com):
>> >> >>
>> >> >> Andy
Hi,
Anyone has any idea about what I should try next regarding this bug?
On Mon, Dec 10, 2012 at 11:21:25PM +0100, Mathieu Chouquet-Stringer wrote:
> after enabling page alloc and slub debug, I was able to capture an error
> followed by the "usual" GPF. More below.
>
> On Thu, Dec 06,
On 12/13, Srivatsa S. Bhat wrote:
>
> On 12/13/2012 09:47 PM, Oleg Nesterov wrote:
> > On 12/13, Srivatsa S. Bhat wrote:
> >>
> >> On 12/13/2012 12:42 AM, Srivatsa S. Bhat wrote:
> >>>
> >>> Even I don't spot anything wrong with it. But I'll give it some more
> >>> thought..
> >>
> >> Since an
On 12/14/2012 03:26 PM, Roland Stigge wrote:
> This set of patches adds:
>
> * Block GPIO API to gpiolib
> * Sysfs support for GPIO API, to provide userland access
> * Device interface for userland access (alternative to sysfs)
> * Devicetree support to instantiate GPIO blocks via DT
> * Example
Resend to fix the typo issue.
Subject: [PATCH] [lmk] create a thread for low mem killer instead of using
kswapd
Currently low mem killer is registered as a shrinker and will be
invoked by kswapd. Since low mem killer and kswapd has different
criteria to invoke to work -- kswap wakes up when
Andy Lutomirski writes:
> On Thu, Dec 13, 2012 at 8:11 PM, Eric W. Biederman
> wrote:
>> Andy Lutomirski writes:
>>
>>> One more issue: the requirement that both upper and lower uids (etc.)
>>> in the maps are in order is rather limiting. I have no objection if
>>> you only require upper ids
On Fri, 2012-12-14 at 20:53 +0800, Yanchuan Nian wrote:
>
>
> 2012/12/13 Myklebust, Trond
> On Thu, 2012-12-13 at 14:37 +0800, ycn...@gmail.com wrote:
> > From: Yanchuan Nian
> >
> > The client returns unreferenced delegations in state
> management. It
On 12/14/2012 08:17 AM, Sivaram Nair wrote:
Since cpuidle_state.power_usage is a signed value, use INT_MAX (instead
of -1) to init the local copies so that functions that tries to find
cpuidle states with minimum power usage works correctly even if they use
non-negative values.
Signed-off-by:
On 13.12.2012 08:44:36, +0100, Stephan Mueller wrote:
Hi Andrew,
> On 13.12.2012 01:43:21, +0100, Andrew Morton
> wrote:
>
> Hi Andrew,
>> On Tue, 11 Dec 2012 13:33:04 +0100
>> Stephan Mueller wrote:
>>
>>> Some time ago, I noticed the fact that for every newly
>>> executed process, the
On 14 December 2012 21:43, Dongjin Kim wrote:
> Replace clock instance name of MSHC controller for BIC and CIU of Exynos4412.
>
> Signed-off-by: Dongjin Kim
> ---
> arch/arm/mach-exynos/clock-exynos4.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On 12/13, Chris Metcalf wrote:
>
> Use the newer idioms for setting PTRACE_O_xxx and PT_TRACE_xxx flags.
> Only set/clear tile-specific flags if the generic routine returns
> success, since otherwise we want to avoid setting any flags at all.
> Atomically update the ptrace flags with the new
* Tony Lindgren [121214 09:23]:
> * Thomas Weber [121115 10:14]:
> > Add i2c bus number for DVI output.
> > The driver uses this to detect if a panel is connected and to read EDID.
>
> Thanks applying into omap-for-v3.8/fixes-for-merge-window.
Oops, dropping and using Tomi's generic version
* Thomas Weber [121115 10:14]:
> Add i2c bus number for DVI output.
> The driver uses this to detect if a panel is connected and to read EDID.
Thanks applying into omap-for-v3.8/fixes-for-merge-window.
Regards,
Tony
> Signed-off-by: Thomas Weber
> ---
>
Corey,
Thanks for the thoughtful reply. Below I respond in detail to
these three points.
1) Why building a variant kernel with ipmi_si as a module is not
feasible.
2) User mode access to IPMI on Stratus systems (e.g. ipmitool).
3) ipmi_si hot removal seems to not work as needed.
Stratus
On Fri, 2012-12-07 at 11:07 +0900, Hiraku Toyooka wrote:
> Hi, Steven,
>
> (2012/11/30 23:17), Steven Rostedt wrote:
> [snip]
> >
> > Actually, I would have:
> >
> > status\input | 0 | 1 |else|
> > --++++
> > not
On 12/14/2012 10:25 AM, Evans, Robert wrote:
Corey,
Thanks for the thoughtful reply. Below I respond in detail to
these three points.
1) Why building a variant kernel with ipmi_si as a module is not
feasible.
2) User mode access to IPMI on Stratus systems (e.g. ipmitool).
3) ipmi_si hot
On Fri, Dec 14, 2012 at 06:00:02PM +0100, Jennifer Naumann wrote:
> On 12/05/2012 09:40 PM, Sebastian Hahn wrote:
> >Jennifer and I have started making the rtl8192u driver conform with the
> >CodingStyle rules a little better. We started out with a cleanfile run,
> >then did corrections for
Some of the drivers that the sb105x SystemBase handles are for parallel
port cards. If PARPORT isn't configured, the build fails. Only
initialize the parallel port cards if PARPORT is configured in.
Reported-by: Wu Fengguang
Signed-off-by: Steven Rostedt
diff --git
On Fri, Dec 14, 2012 at 2:43 AM, Peter De Schrijver
wrote:
> On Thu, Dec 13, 2012 at 07:01:31PM +0100, Stephen Warren wrote:
>> On 12/13/2012 09:27 AM, Mike Turquette wrote:
>> > On Wed, Dec 12, 2012 at 7:49 PM, Prashant Gaikwad
>> > wrote:
>> >> Adds debug file "clock_tree" in
On 12/14/2012 04:24 PM, Alexander Holler wrote:
> Am 14.12.2012 15:34, schrieb Lars-Peter Clausen:
>> On 12/14/2012 03:29 PM, Alexander Holler wrote:
>>> Am 14.12.2012 15:15, schrieb Alexander Holler:
Am 14.12.2012 14:08, schrieb Alexander Holler:
> Am 14.12.2012 10:42, schrieb Lars-Peter
Subject: [PATCH] [lmk] create a thread for low mem killer instead of using
kswapd
Currently low mem killer is registered as a shrinker and will be
invoked by kswapd. Since low mem killer and kswapd has different
criteria to invoke to work -- kswap wakes up when watermark of some
certain order in
From: Mian Yousaf Kaukab
Make it possible to set the pin configuration either as gpio or specific
functionality through the driver interface.
Signed-off-by: Lee Jones
Signed-off-by: Bengt Jonsson
Signed-off-by: Mian Yousaf Kaukab
Tested-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c
From: Bibek Basu
Read register is corrected from "AB8500_GPIO_OUT1_REG" to
"AB8500_GPIO_IN1_REG" in get_value api
Signed-off-by: Lee Jones
Signed-off-by: Bibek Basu
Signed-off-by: Mian Yousaf Kaukab
Reviewed-by: Jonas ABERG
Tested-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c |2 +-
From: Mian Yousaf Kaukab
Signed-off-by: Lee Jones
Signed-off-by: Bibek Basu
Signed-off-by: Mian Yousaf Kaukab
Reviewed-by: Jonas ABERG
Tested-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c | 17 +
include/linux/mfd/abx500/ab8500-gpio.h |3 +++
2 files
From: Michel JAOUEN
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
Signed-off-by: Alex MACRO
Signed-off-by: Michel JAOUEN
Reviewed-by: Jonas ABERG
Reviewed-by: Bengt JONSSON
Reviewed-by: Bibek BASU
---
drivers/gpio/gpio-ab8500.c | 92
From: Naga Radhesh
Number of gpio pins has been changed for AB8505, so
change gpio configurations according to AB8505.
Signed-off-by: Lee Jones
Signed-off-by: Naga Radhesh
Reviewed-by: Bibek BASU
Reviewed-by: Jonas ABERG
Reviewed-by: Srinidhi KASAGAR
---
drivers/gpio/gpio-ab8500.c | 41
From: Mian Yousaf Kaukab
AB8500 gpio numbers start from 1 and not 0 so the offset
0 represents gpio 1. Fixing cluster bounds accordingly for
irq mappings.
Signed-off-by: Lee Jones
Signed-off-by: Mian Yousaf Kaukab
Reviewed-by: Jonas ABERG
Tested-by: Jonas ABERG
---
From: Bibek Basu
Alternate function register address is actually 0x50 and thus
changed accordingly.
Signed-off-by: Lee Jones
Signed-off-by: Bibek Basu
Signed-off-by: Mian Yousaf Kaukab
Reviewed-by: Jonas ABERG
Tested-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c |2 +-
1 file
From: Philippe Langlais
The AB8500 GPIO driver is currently marked as broken, as it's still
using the old framework. This patch brings it back up to scratch and
enables it so we can make good use of it once more.
Signed-off-by: Lee Jones
Signed-off-by: Philippe Langlais
---
The ab8500 GPIO driver is currently 'BROKEN', due to a lack of
updates and recent frame-work adoption. This patch-set aims to
bring the driver back to life so we may make use of it again.
This first stage is to bring it into line with ST-Ericsson's
internal track, which has been keeping
From: Paer-Olof Haakansson
Signed-off-by: Lee Jones
Signed-off-by: Paer-Olof Haakansson
Reviewed-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-ab8500.c b/drivers/gpio/gpio-ab8500.c
index
From: Michel JAOUEN
Use is_ab9540() instead of cpu_is_u9540() when checking platform.
Signed-off-by: Lee Jones
Signed-off-by: Michel JAOUEN
Reviewed-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Yang QU
Only 4 GPIOs named GPIOx_VBAT have both internal pull up and pull
down capability on ab8540. Limit the action range for this function.
Signed-off-by: Lee Jones
Signed-off-by: Yang QU
Reviewed-by: Per FORLIN
---
drivers/gpio/gpio-ab8500.c | 54
These are no longer used and will be replaced by a simple macro.
Signed-off-by: Lee Jones
---
drivers/gpio/gpio-ab8500.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpio/gpio-ab8500.c b/drivers/gpio/gpio-ab8500.c
index 200c605..ab6ceac 100644
---
On 12/13/2012 11:09 PM, Terje Bergström wrote:
> On 13.12.2012 19:58, Stephen Warren wrote:
>> On 12/13/2012 01:57 AM, Thierry Reding wrote:
>>> After some more discussion with Stephen on IRC we came to the
>>> conclusion that the easiest might be to have tegra-drm call into
>>> host1x with
From: Yang QU
Add some GPIOs used as interrupt on ab8540 and modify the setting
strategy of the interrupt line.
Signed-off-by: Lee Jones
Signed-off-by: Yang QU
Reviewed-by: Rabin VINCENT
Reviewed-by: Xiao Mei ZHANG
Tested-by: Yang QU
---
drivers/gpio/gpio-ab8500.c | 50
From: Alexandre Torgue
Signed-off-by: Lee Jones
Signed-off-by: Alexandre Torgue
Reviewed-by: Maxime COQUELIN
Reviewed-by: Marcus COOPER
Reviewed-by: Mattias WALLIN
---
drivers/gpio/gpio-ab8500.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git
From: Philippe Langlais
Signed-off-by: Lee Jones
Signed-off-by: Philippe Langlais
---
drivers/gpio/gpio-ab8500.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-ab8500.c b/drivers/gpio/gpio-ab8500.c
index a0253ad..273f7ca 100644
---
From: Alexandre Torgue
Add 4 GPIOs named GPIOx_VBAT which have both internal pull up
and pull down capability on ab8540. We can also select different
voltage domains for GPIOx_VBAT.
Signed-off-by: Lee Jones
Signed-off-by: Yang QU
Reviewed-by: Alexandre TORGUE
Reviewed-by: Philippe LANGLAIS
From: Marcel Tunnissen
This fixes a bug in gpio_set_value(xxx, 0) for ab8500 GPIOs.
Signed-off-by: Lee Jones
Signed-off-by: Marcel Tunnissen
Reviewed-by: Jonas ABERG
Tested-by: Jonas ABERG
---
drivers/gpio/gpio-ab8500.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Yang QU
Set GpioPullUpDownSel register for direction output function as GPIO51
to GPIO54 not share the same register with other GPIOs on AB8540.
Signed-off-by: Lee Jones
Signed-off-by: Yang QU
Reviewed-by: Patrick DELAUNAY
Reviewed-by: Xiao Mei ZHANG
Reviewed-by: Philippe LANGLAIS
From: Yang QU
Missing initial value in ab8540 gpio configuration function. So
initialize it and fix this warning.
Signed-off-by: Lee Jones
Signed-off-by: Yang QU
Reviewed-by: Rabin VINCENT
---
drivers/gpio/gpio-ab8500.c |2 ++
1 file changed, 2 insertions(+)
diff --git
From: Linus Walleij
This driver is using symbols from so
include this file explicitly.
Signed-off-by: Lee Jones
Signed-off-by: Linus Walleij
Reviewed-by: Philippe LANGLAIS
---
drivers/gpio/gpio-ab8500.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-ab8500.c
From: Mian Yousaf Kaukab
This patch extends the the platform data to include gpio direction and pullups
configurations. These configurations are applied during probe().
Signed-off-by: Lee Jones
Signed-off-by: Bibek Basu
Signed-off-by: Mian Yousaf Kaukab
Reviewed-by: Jonas ABERG
Tested-by:
Replace clock instance name of MSHC controller for BIC and CIU of Exynos4412.
Signed-off-by: Dongjin Kim
---
arch/arm/mach-exynos/clock-exynos4.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-exynos/clock-exynos4.c
On Fri 14-12-12 10:43:55, Rik van Riel wrote:
> On 12/14/2012 03:37 AM, Michal Hocko wrote:
>
> >I can answer the later. Because memsw comes with its price and
> >swappiness is much cheaper. On the other hand it makes sense that
> >swappiness==0 doesn't swap at all. Or do you think we should get
On 12/14/2012 08:08 AM, Dave Jones wrote:
> On Fri, Dec 14, 2012 at 09:21:50AM +0100, Andrew Lunn wrote:
>
> > > Given this seems to be dependant on device-tree, shouldn't there be
> > > some 'depends on' in the kconfig to prevent this showing up on
> architectures
> > > that don't implement
On Fri, Dec 14, 2012 at 6:49 AM, Al Viro wrote:
> On Fri, Dec 14, 2012 at 03:14:50AM -0800, Andy Lutomirski wrote:
>
>> > Wait a minute. get_user_pages() relies on ->mmap_sem being held. Unless
>> > I'm seriously misreading your patch it removes that protection. And yes,
>> > I'm aware of
Quoting Eric W. Biederman (ebied...@xmission.com):
> "Serge E. Hallyn" writes:
>
> > Quoting Eric W. Biederman (ebied...@xmission.com):
> >> "Serge E. Hallyn" writes:
> >>
> >> > Quoting Eric W. Biederman (ebied...@xmission.com):
> >> >>
> >> >> Andy Lutomirski pointed out that the current
Set the vring addresses in the resource table so that
the remote device can read the actual addresses used.
Signed-off-by: Sjur Brændeland
---
drivers/remoteproc/remoteproc_core.c |5 +
include/linux/remoteproc.h |2 ++
2 files changed, 7 insertions(+), 0 deletions(-)
Verify that firmware name is defined in rproc_add.
Signed-off-by: Sjur Brændeland
---
drivers/remoteproc/remoteproc_core.c | 13 ++---
1 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/remoteproc/remoteproc_core.c
b/drivers/remoteproc/remoteproc_core.c
index
Changes since v1:
- Separate vring allocation and registration
- Break up patches in smaller parts to facilitate review.
(The patches here are perhaps too fine grained and can be squashed later).
This patch-set adds support for shared resource table between
Linux kernel and remote devices.
Refatcor rproc_elf_find_rsc_table and split out the scanning
for the section header named resource table. This is done to
prepare for loading firmware once.
Signed-off-by: Sjur Brændeland
---
drivers/remoteproc/remoteproc_elf_loader.c | 83 +---
1 files changed, 51
301 - 400 of 1140 matches
Mail list logo
