On Thu, 6 Sep 2012, Paolo Bonzini wrote:
> Date: Thu, 06 Sep 2012 14:36:53 +0200
> From: Paolo Bonzini
> To: Ric Wheeler
> Cc: ax...@kernel.dk, Mike Snitzer ,
> Alan Cox ,
> Martin K. Petersen ,
> linux-kernel@vger.kernel.org, linux-s...@vger.kernel.org
> Subject: Re: [Ping^3] Re:
On 09/06/2012 02:53 PM, Sasha Levin wrote:
> So I think that for the hash iterator it might actually be simpler.
>
> My solution to making 'break' work in the iterator is:
>
> for (bkt = 0, node = NULL; bkt < HASH_SIZE(name) && node == NULL; bkt++)
>
On Thu, 2012-09-06 at 13:40 +0800, Jeremy Kerr wrote:
> From: Matthew Garrett
>
> The existing EFI variables code only supports variables of up to 1024
> bytes. This limitation existed in version 0.99 of the EFI specification,
> but was removed before any full releases. Since variables can now
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> Moving the RCU grace-period processing to a kthread and adjusting the
> tracing resulted in two of the rcu_state structure's fields being unused.
> This commit therefore removes them.
>
> Signed-off-by:
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> Some uses of RCU benefit from shorter grace periods, while others benefit
> more from the greater efficiency provided by longer grace periods.
> Therefore, this commit allows the durations to be controlled
Hi Alexander,
Am Freitag, 31. August 2012, 13:34:03 schrieb Alexandre Courbot:
> Some device drivers (panel backlights especially) need to follow precise
> sequences for powering on and off, involving gpios, regulators, PWMs
> with a precise powering order and delays to respect between each
On Thu, Sep 06, 2012 at 10:22:19AM +0300, Pekka Enberg wrote:
> On Wed, Sep 5, 2012 at 1:02 AM, Pekka Enberg wrote:
> > > How significant is the speed gain? The "isa_done" flag makes code flow
> > > more difficult to follow.
>
> On Wed, 5 Sep 2012, Yinghai Lu wrote:
> > Not really much.
> >
> >
Hit this in overnight fuzz testing..
BUG: unable to handle kernel NULL pointer dereference at 0020
IP: [] audit_log_d_path+0x35/0xf0
PGD 12fded067 PUD 142c06067 PMD 0
Oops: [#1] SMP
Modules linked in: tun fuse ipt_ULOG binfmt_misc nfnetlink nfc caif_socket caif
phonet can llc2
On 2012年09月06日 18:09, David Sterba wrote:
> On Thu, Sep 06, 2012 at 02:40:41PM +0800, Wang Sheng-Hui wrote:
>> The memory allocation failure is BUG_ON in add_excluded_extent (following
>> the code path) and btrfs_rmap_block. No need to BUG_ON -ENOMEM inside
>> exclude_super_stripes itself.
>
> No
On Thursday 06 September 2012 12:32 PM, NeilBrown wrote:
> From: NeilBrown
> Subject: [PATCH] OMAP GPIO - don't wake from suspend unless requested.
>
> Current kernel will wake from suspend on an event on any active
> GPIO even if enable_irq_wake() wasn't called.
>
> There are two reasons that
On 08/22/2012 03:47 PM, Xiao Guangrong wrote:
> On 08/22/2012 08:06 PM, Avi Kivity wrote:
>> On 08/21/2012 06:03 AM, Xiao Guangrong wrote:
>>> Introduce write_readonly_mem in mmio-exit-info to indicate this exit is
>>> caused by write access on readonly memslot
>>
>> Please document this in
On Thu, Sep 06, 2012 at 02:00:04PM +, maximilian attems wrote:
> On Wed, Sep 05, 2012 at 08:26:05PM +, maximilian attems wrote:
> > On Wed, Sep 05, 2012 at 07:40:09PM +0300, Tzafrir Cohen wrote:
> > >
> > > $ grep CROSS_COMPILE .config
> > > CONFIG_CROSS_COMPILE="arm-linux-gnueabihf-"
> >
Hi,
On Sep 6, 2012, at 5:01 PM, Peter Ujfalusi wrote:
> Hi,
>
> On 09/05/2012 07:43 PM, Pantelis Antoniou wrote:
>> The driver in question (twl4030.c) does not call
>> snd_soc_codec_set_cache_io().
>> However the snd-soc core does call it in sound/soc/soc-core.c in
>> soc_probe_codec.
>>
>>
On 09/06/2012 01:27 AM, Ben Hutchings :
> On Wed, 2012-09-05 at 11:00 +0200, Nicolas Ferre wrote:
>> Add an indication about which revision of the hardware we are running in
>> info->driver string.
>>
>> Signed-off-by: Nicolas Ferre
>> ---
>> drivers/net/ethernet/cadence/macb.c |4
>> 1
Hi,
On 09/05/2012 07:43 PM, Pantelis Antoniou wrote:
> The driver in question (twl4030.c) does not call snd_soc_codec_set_cache_io().
> However the snd-soc core does call it in sound/soc/soc-core.c in
> soc_probe_codec.
>
> I do see that there's a commit 98d3088e534a2a61f6690b5426909b0c3b57a785
On Wed, Sep 05, 2012 at 08:26:05PM +, maximilian attems wrote:
> On Wed, Sep 05, 2012 at 07:40:09PM +0300, Tzafrir Cohen wrote:
> >
> > $ grep CROSS_COMPILE .config
> > CONFIG_CROSS_COMPILE="arm-linux-gnueabihf-"
> >
> > Command:
> >
> > KBUILD_DEBARCH=armhf make ARCH=arm
On Tue, Sep 4, 2012 at 6:45 AM, Matthew Garrett wrote:
> On Thu, Aug 23, 2012 at 05:44:22PM -0600, Bjorn Helgaas wrote:
>> On Thu, Aug 23, 2012 at 10:36 AM, Matthew Garrett wrote:
>> > EFI provides support for providing PCI ROMs via means other than the ROM
>> > BAR. This support vanishes after
On 09/04/2012 06:07 PM, Liu, Jinsong wrote:
> From 728a17e2de591b557c3c8ba31076b4bf2ca5ab42 Mon Sep 17 00:00:00 2001
> From: Liu, Jinsong
> Date: Wed, 5 Sep 2012 03:18:15 +0800
> Subject: [PATCH] KVM: tsc deadline timer works only when hrtimer high
> resolution configured
>
> This is for 2
Hi Vaihbav,
On 08/27/2012 02:31 PM, Vaibhav Hiremath wrote:
> This series is trivial patch-series and should be considered as
> preparation for the future where we supposed to get rid of
> hwmod dependency.
>
> 1/2: Converts all hex numbers to lowercase, fixing inconsistency
> 2/2: Add reg and
Em Thu, Sep 06, 2012 at 10:11:22AM +0800, Liang Li escreveu:
> On 2012-09-06 06:41, Arnaldo Carvalho de Melo wrote:
> > > Does:
> > >
> > > SLANG_INC ?= -I=/usr/include/slang
> > >
> > > work any better? Its hard to tell from the above error which bit of the
> >
> > I'll try later
> >
> > >
On 09/04/2012 07:01 PM, Mathieu Desnoyers wrote:
>> #define do_for_each_ftrace_rec(pg, rec)
>> \
>> > for (pg = ftrace_pages_start, rec = >records[pg->index];
>> > \
>> > pg && rec == >records[pg->index];
2012/9/6 Ninja Tekkaman :
> This is a Chinese translated version of Documentation/arm/Booting
>
> Signed-off-by: Fu Wei
> ---
Acked-by: Harry Wei
Good job ;-)
--
Thanks
Harry Wei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 2012-09-06 at 15:46 +0200, Peter Zijlstra wrote:
> On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> > + get_online_cpus();
> > + for_each_online_cpu(cpu)
> > + for_each_rcu_flavor(rsp)
> > + smp_call_function_single(cpu,
Em Thu, Sep 06, 2012 at 11:10:46AM +0900, Namhyung Kim escreveu:
> From: Namhyung Kim
>
> Current perf_evlist__set_tracepoint_names is a misnomer because it
> finds and sets correspoding event_format in addition to the name. So
> skipping it when a event has set name already caused a trouble.
>
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> + get_online_cpus();
> + for_each_online_cpu(cpu)
> + for_each_rcu_flavor(rsp)
> + smp_call_function_single(cpu, rcu_oom_notify_cpu,
> +rsp,
On Thu, Sep 6, 2012 at 3:24 PM, Linus Walleij wrote:
> 2012/9/5 Dong Aisheng :
>
> Thanks for your help Dong, Wei can you please check Dong's
> comments and submit a version with his ACK, and I'll apply it.
>
Acked-by: Harry Wei
This patch is made by Wei Fu, so i think he is the best one to
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> +static int rcu_gp_kthread(void *arg)
> +{
> + struct rcu_state *rsp = arg;
> + struct rcu_node *rnp = rcu_get_root(rsp);
> +
> + for (;;) {
> +
> + /* Handle grace-period start. */
> + for
2012/9/6 OGAWA Hirofumi :
> Namjae Jeon writes:
>
In this long discusstion about the FAT acceptance over NFS, our belief
is still that the objective should be to reduce errors as much as
possible and then if there are certain scenarios - at least that could
be highlighted as a
Dave - I couldn't find this patch in your git repo at
git://people.freedesktop.org/~airlied/linux in the drm-next or drm-fixes
branches.
https://patchwork.kernel.org/patch/1379071/
It appears to fix a real problem for Mac users -
http://bugs.launchpad.net/bugs/1039157. See
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> static void rcu_report_qs_rsp(struct rcu_state *rsp, unsigned long flags)
> __releases(rcu_get_root(rsp)->lock)
> {
> + raw_spin_unlock_irqrestore(_get_root(rsp)->lock, flags);
> + wake_up(>gp_wq); /* Memory
On Thu, Sep 6, 2012 at 1:48 PM, Sedat Dilek wrote:
> On Thu, Sep 6, 2012 at 9:23 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20120905:
>>
>> New tree: arm64
>>
>> The powerpc tree gained a build failure for which I reverted 3 commits.
>>
>> The net-next tree lost its build
On Thu, 2012-08-30 at 11:18 -0700, Paul E. McKenney wrote:
> +static int rcu_gp_kthread(void *arg)
> +{
> + unsigned long flags;
> + struct rcu_data *rdp;
> + struct rcu_node *rnp;
> + struct rcu_state *rsp = arg;
> +
> + for (;;) {
> +
> + /* Handle
Hi,
On Thu, Sep 06, 2012 at 05:02:45PM +1000, NeilBrown wrote:
> On Thu, 6 Sep 2012 11:18:09 +0530 "Shilimkar, Santosh"
> wrote:
>
> > On Thu, Sep 6, 2012 at 8:35 AM, NeilBrown wrote:
> > > On Mon, 3 Sep 2012 22:59:06 -0700 "Shilimkar, Santosh"
> > > wrote:
>
> > >> After thinking bit more
Hi,
On Mon, Aug 06, 2012 at 06:53:11PM +0530, Kishon Vijay Abraham I wrote:
> This patch series adds dt data for MUSB and related modules to
> get MUSB working
>
> These patches were initially part of
> [PATCH v6 00/11] omap: musb: Add device tree support
>
> These patches can be tested by
Hi Matt,
On 27.08.2012 17:33, Daniel Mack wrote:
> On 23.08.2012 03:09, Matt Porter wrote:
>> This series begins the conversion of the DaVinci private EDMA API
>> implementation to a DMA engine driver and converts two of the three
>> in-kernel users of the private EDMA API to DMA engine.
>>
>>
Software events (sw,tracepoints,...) do not need to be
multiplexed. However, when using a SW event, the SW PMU
(TYPE_SOFTWARE, TYPE_TRACEPOINT) was added to the per-cpu
rotation_list. That list is used by perf_rotate_context()
to iterate over all the PMUs to rotate event lists and
multiplex.
From: Matt Fleming
Some firmware still needs a 1:1 (virt->phys) mapping even after we've
called SetVirtualAddressMap(). So install the mapping alongside our
existing kernel mapping whenever we make EFI calls in virtual mode.
This bug was discovered on ASUS machines where the firmware
> Even if we decide not to remove these tunables from under their current
> per-cpu location, I still think it is much cleaner to have them
> available under /sys/devices/system/machinecheck.
"much cleaner" is not sufficient justification to break an ABI.
-Andi
--
a...@linux.intel.com --
On Thu, Sep 06, 2012 at 01:03:02PM +, Arnd Bergmann wrote:
> On Thursday 06 September 2012, ABRAHAM, KISHON VIJAY wrote:
> > > diff --git a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > > b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > > index d2fe064..bb0c7f4 100644
On 2012.09.06 at 15:08 +0200, Takashi Iwai wrote:
> At Thu, 6 Sep 2012 11:43:48 +0200,
> Markus Trippelsdorf wrote:
> >
> > On 2012.09.06 at 10:21 +0200, Takashi Iwai wrote:
> > > At Thu, 06 Sep 2012 09:35:26 +0200,
> > > Takashi Iwai wrote:
> > >
> > > In short, a patch like below may fix the
On Thu, 2012-09-06 at 12:04 +0200, Robert Richter wrote:
> please take a look at this. Not sure if Linus want to look at this too
> and if we need more optimization here.
It could probably go either way. Although the function has several
lines, it looks like the actual assembly produced wouldn't
This patch is part of the architecture backend for thp on s390.
It disables thp for kvm hosts, because there is no kvm host hugepage
support so far. Existing thp mappings are split by follow_page() with
FOLL_SPLIT, and future thp mappings are prevented by setting
VM_NOHUGEPAGE in mm->def_flags.
On s390, a valid page table entry must not be changed while it is
attached to any CPU. So instead of pmd_mknotpresent() and set_pmd_at(),
an IDTE operation would be necessary there. This patch introduces the
pmdp_invalidate() function, to allow architecture-specific
implementations.
Il 06/09/2012 14:51, Michael S. Tsirkin ha scritto:
> On Thu, Sep 06, 2012 at 02:13:14PM +0200, Paolo Bonzini wrote:
>> Il 06/09/2012 12:53, Michael S. Tsirkin ha scritto:
It is useful because it lets guests inflate the balloon aggressively,
and then use ballooned-out pages even in
This patch is part of the architecture backend for thp on s390.
It provides the functions related to thp splitting, including
serialization against gup. Unlike other archs, pmdp_splitting_flush()
cannot use a tlb flushing operation to serialize against gup on s390,
because that wouldn't be stopped
This patch is part of the architecture backend for thp on s390.
It provides the pagetable pre-allocation functions
pgtable_trans_huge_deposit() and pgtable_trans_huge_withdraw(). Unlike
other archs, s390 has no struct page * as pgtable_t, but rather a
pointer to the page table. So instead of
This implements the architecture backend for transparent hugepages
on s390.
Signed-off-by: Gerald Schaefer
---
arch/s390/Kconfig | 1 +
arch/s390/include/asm/hugetlb.h | 18 +---
arch/s390/include/asm/pgtable.h | 189
The thp page table pre-allocation code currently assumes that pgtable_t
is of type "struct page *". This may not be true for all architectures,
so this patch removes that assumption by replacing the functions
prepare_pmd_huge_pte() and get_pmd_huge_pte() with two new functions
that can be defined
This adds a check to hugepage_madvise(), to refuse MADV_HUGEPAGE
if VM_NOHUGEPAGE is set in mm->def_flags. On s390, the VM_NOHUGEPAGE
flag will be set in mm->def_flags for kvm processes, to prevent any
future thp mappings. In order to also prevent MADV_HUGEPAGE on such an
mm, hugepage_madvise()
Cleanup patch in preparation for transparent hugepage support on s390.
Adding new architectures to the TRANSPARENT_HUGEPAGE config option can
make the "depends" line rather ugly, like "depends on
(X86 || (S390 && 64BIT)) && MMU".
This patch adds a HAVE_ARCH_TRANSPARENT_HUGEPAGE instead. x86
This patch series adds support for transparent hugepages on s390.
Small changes to common code are necessary with regard to a different
pgtable_t, tlb flushing and kvm behaviour on s390, see patches 2 to 4.
Also, (x86) Kconfig is touched by patch 1.
Changes since RFC v2:
[PATCH 1/8] introduce
At Thu, 6 Sep 2012 11:43:48 +0200,
Markus Trippelsdorf wrote:
>
> On 2012.09.06 at 10:21 +0200, Takashi Iwai wrote:
> > At Thu, 06 Sep 2012 09:35:26 +0200,
> > Takashi Iwai wrote:
> >
> > In short, a patch like below may fix the issue (note: completely
> > untested!)
>
> No it doesn't,
On Thursday 06 September 2012, ABRAHAM, KISHON VIJAY wrote:
> > diff --git a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > index d2fe064..bb0c7f4 100644
> > --- a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> >
> On Wed, Sep 05, 2012 at 07:28:23PM +0200, Michal Nazarewicz wrote:
>> If you ask me, I'm not convinced that this improves anything.
On Thu, Sep 06 2012, Minchan Kim wrote:
> At least, it removes MIGRATE_ISOLATE type in free_area->free_list
> which is very irony type as I mentioned. I really
As the pwm driver now is devicetree only, remove the platform
support for this device.
Signed-off-by: Sascha Hauer
---
arch/arm/mach-imx/clk-imx21.c |1 -
arch/arm/mach-imx/clk-imx25.c |8 ---
arch/arm/mach-imx/clk-imx27.c |1 -
>> +pfn = page_to_pfn(page);
>> +if (pfn >= end_pfn)
>> +return false;
>> +if (pfn >= start_pfn)
>> +goto found;
On Thu, Sep 06 2012, Lai Jiangshan wrote:
> this test is wrong.
>
> use this:
>
> if ((pfn <= start_pfn) &&
On Wed, 05 Sep 2012 12:56:03 +0200
khal...@piap.pl (Krzysztof Hałasa) wrote:
> Hi,
>
> I'm trying to use GSM tty line discipline. Basically
>
> echo AT+CMUX=0 > /dev/ttyS0
>
> set termios (speed etc.)
> int ldisc = N_GSM0710;
> ioctl(fd, TIOCSETD, );
Baffled at this point. If you set some
The driver doesn't need to know about its platform_device.
Everything the driver needs can be done through the
struct device pointer. In case we need to use the
OMAP-specific PM function pointers, those can make
sure to find the device's platform_device pointer
so they can find the struct
The current support is known to be broken and
a later patch will come re-adding it using
dma engine API.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 330 ++-
1 file changed, 12
quite a few changes here, though they are
pretty obvious. In summary we're making sure
to detect which interrupt type we need to
handle before calling the underlying interrupt
handling procedure.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by: Felipe Balbi
---
The pwm core makes sure that pwm_enable/disable are called only
once. Still keep the enabled state since we will need it in
pwm_config.
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
drivers/pwm/pwm-imx.c | 25 +++--
1 file changed,
The following is the third version of the i.MX pwm series. I integrated
the remaining comments from Shawn and Benoît and added their tags.
So Thierry, please pull the attached patches. The pull request only
contains the pwm framework specific patches, the remaining two I'd
like to push via the
> Sorry, I don't see anyone explained clearly why request_firmware()
> can't be called inside module_init() in module case, so maybe it is
> a bit early to say it is a fix on 'bug', :-)
Because the firmware load may trigger a need to load a driver to load the
firmware.
> > dev_discard_firmware()
since all other IRQ types now do all necessary
checks inside their handlers, transmit_chars()
was the only one left expecting serial_omap_irq()
to check THRE for it. We can move THRE check to
transmit_chars() in order to make serial_omap_irq()
more uniform.
Tested-by: Shubhrajyoti D
Acked-by:
by the time we call our first pm_runtme_get_sync()
after enable pm_runtime, our resume method might
be called. To avoid problems, we must make sure
that our dev->drvdata is set correctly before
our resume method gets called.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by:
When we're running our hardirq handler, there's
not need to disable IRQs with spin_lock_irqsave()
because IRQs are already disabled. It also makes
no difference if we save or not IRQ flags.
Switch over to simple spin_lock/spin_unlock and
drop the "flags" variable.
Tested-by: Shubhrajyoti D
From: Ruchika Kharwar
pm_runtime_enable() needs to be invoked before
pm_runtime_use_autosuspend(), and
pm_runtime_set_autosuspend_delay() functions.
Tested-by: Shubhrajyoti D
Signed-off-by: Nishanth Menon
Signed-off-by: Ruchika Kharwar
Signed-off-by: Felipe Balbi
---
This has been missing from OMAP UART driver
for quite a while and it's simple enough
to implement it.
Tested-by: Shubhrajyoti D
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/tty/serial/omap-serial.c
if we would reach serial_omap_get_char() while
Data Ready bit isn't set, we would return from
it without kicking our pm timer. This would mean
we would, eventually, have an unbalanced
pm_runtime_get on our device which would prevent
it from ever sleeping again.
Tested-by: Shubhrajyoti D
this driver doesn't use any from , so
we can remove it without any problems.
This will, however cause a problem because omap-serial.c
was relying on indirect inclusion of ,
let's fix the issue by including
on omap-serial.c as it should be.
Tested-by: Shubhrajyoti D
Signed-off-by: Felipe Balbi
On Thu, Sep 06 2012, Lai Jiangshan wrote:
> +found:
> + next_pfn = page_to_pfn(page);
> + list_for_each_entry_from(page, _pages, lru) {
> + if (page_to_pfn(page) != next_pfn)
> + return false;
> + pfn = page_to_pfn(page);
+ pfn =
enable RX FIFO for 16 characters and TX FIFO
for 16 spaces.
Tested-by: Shubhrajyoti D
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/omap-serial.c
nobody needs to access the uart_omap_port structure
other than omap-serial.c file. Let's move that
structure definition to the C source file in order
to prevent anyone from accessing our structure.
Tested-by: Shubhrajyoti D
Acked-by: Tony Lindgren
Signed-off-by: Felipe Balbi
---
From: Vikram Pandita
Software flow control register bits were not defined correctly.
Also clarify the IXON and IXOFF logic to reflect what userspace wants.
Cc: sta...@vger.kernel.org
Tested-by: Shubhrajyoti D
Signed-off-by: Vikram Pandita
Signed-off-by: Shubhrajyoti D
Acked-by: Tony
From: Ruchika Kharwar
This patch unlocks the port lock before calling a serial_core API
and re-acquires the port lock after calling it.
This patch fixes a system freeze issue seen when the serial_core
API uart_write_wakeup() eventually attempts to acquire the port lock
already acquired by omap
it makes no sense to mark our IRQ handler inline
since it's passed as a function pointer when
enabling the IRQ line.
Tested-by: Shubhrajyoti D
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Two functions:
omap_serial_fill_features_erratas() and
of_get_uart_port_info() are only called from probe().
Marking them as __devinit gives us another
oportunity to free some code after .init.text
is done.
Tested-by: Shubhrajyoti D
Signed-off-by: Ruchika Kharwar
Signed-off-by: Felipe Balbi
if platform_get_drvdata() returns NULL, that's
quite a nasty bug on the driver which we want to
catch ASAP. Otherwise, that check is hugely
unneeded.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 9 +++--
1 file
before removing the driver, let's make sure
to force device into a suspended state in order
to conserve power.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 1 +
1 file changed, 1 insertion(+)
diff --git
receive_chars() was getting too big and too difficult
to follow. By splitting it into separate RDI and RSLI
handlers, we have smaller functions which are easy
to understand and only touch the pieces which they need
to touch.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by:
Everytime we're done using our TTY, we want
the pm timer to be reinitilized. By sticking
to pm_runtime_pm_autosuspend() we make sure
that this will always be the case.
The idea behind this patch is to make sure we
will always reinitialize the pm timer so that
we don't fall into a situation where
OMAP has some extra Interrupt types which can
be really useful for SW. Let's define them
so we can later use those in OMAP's serial driver.
Tested-by: Shubhrajyoti D
Acked-by: Santosh Shilimkar
Signed-off-by: Felipe Balbi
---
include/linux/serial_reg.h | 4
1 file changed, 4
Hi guys,
here's v4 of the omap uart patchset. No changes other than a rebase on top of
Greg's tty-next branch and Tony's Acked-by being added to a couple patches
Note: I'm resending the series with Vikram's Software Flow Control fix anyway
as it can just be ignored if it's decided it needs to go
On Thu, Sep 06, 2012 at 02:13:14PM +0200, Paolo Bonzini wrote:
> Il 06/09/2012 12:53, Michael S. Tsirkin ha scritto:
> >> It is useful because it lets guests inflate the balloon aggressively,
> >> and then use ballooned-out pages even in places where the guest OS
> >> cannot sleep, such as
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
arch/arm/boot/dts/imx53.dtsi| 14 ++
arch/arm/mach-imx/clk-imx51-imx53.c |4
2 files changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/imx53.dtsi
From: Philipp Zabel
The i.MX pwm core has two clocks: The ipg clock and the ipg highfreq
(peripheral) clock. The ipg clock has to be enabled for this hardware
to work. The actual pwm output can either be driven by the ipg clock
or the ipg highfreq. The ipg highfreq has the advantage that it runs
We used to enable/disable the pwm only by switching the
clock on or off. Instead, use the dedicated register bits.
These differ on different SoCs, so introduce a SoC specific
function for this.
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
The i.MX pwm core has two clocks: The ipg clock and the ipg highfreq
(peripheral) clock. The ipg clock has to be enabled for this hardware
to work. The actual pwm output can either be driven by the ipg clock
or the ipg highfreq. The ipg highfreq has the advantage that it runs
even when the SoC is
To make the code more flexible.
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
drivers/pwm/pwm-imx.c | 145 -
1 file changed, 82 insertions(+), 63 deletions(-)
diff --git a/drivers/pwm/pwm-imx.c
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
drivers/pwm/pwm-imx.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/pwm/pwm-imx.c b/drivers/pwm/pwm-imx.c
index 242a30d..97f385e 100644
--- a/drivers/pwm/pwm-imx.c
On Thu, Sep 06 2012, Minchan Kim wrote:
> Normally, MIGRATE_ISOLATE type is used for memory-hotplug.
> But it's irony type because the pages isolated would exist
> as free page in free_area->free_list[MIGRATE_ISOLATE] so people
> can think of it as allocatable pages but it is *never* allocatable.
From: Philipp Zabel
At the same time remove platform based support. No user for
this driver has made it into mainline so far, so all we break
is out of tree stuff.
Signed-off-by: Philipp Zabel
Signed-off-by: Sascha Hauer
Reviewed-by: Shawn Guo
Reviewed-by: Benoît Thébaudeau
---
On Thu, 06 Sep 2012 18:04:27 +0530
"Naveen N. Rao" wrote:
> On 09/06/2012 05:58 PM, Andi Kleen wrote:
> >> The change is still under discussion. Stage one is to add the new global
> >> pathnames in addition to keeping the old per-cpu ones. Also fix all
> >> utilities
> >> (just mcelog(8) as far
On Tue, Aug 21, 2012 at 3:29 AM, Mel Gorman wrote:
> On Mon, Aug 20, 2012 at 05:36:29PM +0100, Mel Gorman wrote:
>> This is a rebase with some small changes to Kosaki's "mempolicy memory
>> corruption fixlet" series. I had expected that Kosaki would have revised
>> the series by now but it's been
Il 06/09/2012 14:08, Ric Wheeler ha scritto:
>> According to the standard, the translation layer can write a
>> user-provided pattern to every sector in the disk. It's an optional
>> feature and libata doesn't do that, but it is still possible.
>
> It is not possible today with our stack though,
On 09/06/2012 05:58 PM, Andi Kleen wrote:
The change is still under discussion. Stage one is to add the new global
pathnames in addition to keeping the old per-cpu ones. Also fix all utilities
(just mcelog(8) as far as we know) to prefer the new paths.
But why do you even want to change it?
On Wed, Sep 05, 2012 at 01:27:49PM -0700, Greg KH wrote:
> On Thu, Aug 23, 2012 at 01:33:00PM +0300, Felipe Balbi wrote:
> > From: Vikram Pandita
> >
> > Software flow control register bits were not defined correctly.
> >
> > Also clarify the IXON and IXOFF logic to reflect what userspace
On Wed, Sep 05, 2012 at 01:27:21PM -0700, Greg KH wrote:
> On Thu, Aug 23, 2012 at 01:32:43PM +0300, Felipe Balbi wrote:
> > The driver doesn't need to know about its platform_device.
> >
> > Everything the driver needs can be done through the
> > struct device pointer. In case we need to use the
> The change is still under discussion. Stage one is to add the new global
> pathnames in addition to keeping the old per-cpu ones. Also fix all utilities
> (just mcelog(8) as far as we know) to prefer the new paths.
But why do you even want to change it? Does it fix anything?
AFAIK the old
Namjae Jeon writes:
>>> In this long discusstion about the FAT acceptance over NFS, our belief
>>> is still that the objective should be to reduce errors as much as
>>> possible and then if there are certain scenarios - at least that could
>>> be highlighted as a limitation in Documentation
501 - 600 of 1542 matches
Mail list logo
