Enable direct access to EOI MSR of x2apic to accelerate guests.
This accelerate handling of interrupts delivered directly to guest from
passed-through PCI devices. When a virtual IRQ is injected, this feature
is disabled in order to route following EOI to virtual APIC. Then, it is
enabled again
For slave CPUs, it is inapropriate to request TLB flush using IPI.
because the IPI may be sent to a KVM guest when the slave CPU is running
the guest with direct interrupt routing.
Instead, it registers a TLB flush request in per-cpu bitmask and send a NMI
to interrupt execution of the guest.
When a PCI device is assigned to a guest running on slave CPUs, this
routes the device's MSI/MSI-X interrupts directly to the guest.
Because the guest uses a different interrupt vector from the host,
vector remapping is required. This is safe because slave CPUs only handles
interrupts for the
Add some fix-ups that proxy slab operations on online CPUs for the guest,
in order to avoid touching slab on slave CPUs where some slab functions
are not activated.
Currently, slab may be touched on slave CPUs in following 3 cases.
For each cases, the fix-ups below are introduced:
*
Split memory hotplug function from cpu_up() as cpu_memory_up(), which will
be used for assigning memory area to off-lined cpus at following patch
in this series.
Signed-off-by: Tomoki Sekiyama tomoki.sekiyama...@hitachi.com
Cc: Avi Kivity a...@redhat.com
Cc: Marcelo Tosatti mtosa...@redhat.com
Add a facility of using offlined CPUs as slave CPUs. Slave CPUs are
specialized to exclusively run functions specified by online CPUs,
which do not run user processes.
To use this feature, build the kernel with CONFIG_SLAVE_CPU=y.
A slave CPU is launched by calling cpu_slave_up() when the CPU is
Adds a facility to use hrtimer on slave CPUs.
To initialize hrtimer when slave CPUs are activated, and to shutdown hrtimer
when slave CPUs are stopped, this patch adds the slave cpu notifier chain,
which call registered callbacks when slave CPUs are up, dying, and died.
The registered callbacks
On Thu, 6 Sep 2012 15:10:14 +1000
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Greg,
After merging the tty tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/tty/serial/sccnxp.c:20:0:
include/linux/serial_core.h: In function
Hello.
On 06-09-2012 8:28, Shaohui Xie wrote:
The freescale V2 SATA controller checks if the received data length matches
the programmed length 'ttl', if not, it assumes that this is an error.
In ATAPI, the 'ttl' is based on max allocation length and not the actual
data transfer length,
Add path to migrate execution of vcpu_enter_guest to a slave CPU when
vcpu-arch.slave_cpu is set.
After moving to the slave CPU, it goes back to the online CPU when the
guest is exited by reasons that cannot be handled by the slave CPU only
(e.g. handling async page faults).
On migration,
Page faults which occured by the guest running on slave CPUs cannot be
handled on slave CPUs because it is running on idle process context.
With this patch, the page fault happened in a slave CPU is notified to
online CPU using struct kvm_access_fault, and is handled after the
user-process for
Enable virtualization when slave CPUs are activated, and disable when
the CPUs are dying using slave CPU notifier call chain.
In x86, TSC kHz must also be initialized by tsc_khz_changed when the
new slave CPUs are activated.
Signed-off-by: Tomoki Sekiyama tomoki.sekiyama...@hitachi.com
Cc: Avi
On 09/06/2012 02:27 PM, Tomoki Sekiyama wrote:
This RFC patch series provides facility to dedicate CPUs to KVM guests
and enable the guests to handle interrupts from passed-through PCI devices
directly (without VM exit and relay by the host).
With this feature, we can improve throughput and
It doesn't seem this spinlock was properly initialized.
Signed-off-by: Jean Delvare kh...@linux-fr.org
Cc: Finn Thain fth...@telegraphics.com.au
Cc: Geert Uytterhoeven ge...@linux-m68k.org
---
I can't even build-test this.
drivers/block/swim.c |1 +
1 file changed, 1 insertion(+)
---
Il 06/09/2012 13:31, Ric Wheeler ha scritto:
Both of these commands are destructive. WRITE_SAME (if done without the
discard bits set) can also take a very long time to be destructive and
tie up the storage.
FORMAT_UNIT has the same characteristics and yet it is allowed (btw, I
don't think
On Wednesday 05 September 2012 09:03 PM, Stephen Warren wrote:
On 09/05/2012 02:02 AM, Laxman Dewangan wrote:
On Wednesday 05 September 2012 02:17 AM, Stephen Warren wrote:
On 08/29/2012 09:01 AM, Laxman Dewangan wrote:
Register all TPS6586x regulators even if there is no regulator
init data
hstatus = ioread32(hcr_base + HSTATUS);
sata_fsl_scr_read(ap-link, SCR_ERROR, SError);
+ /* Read command completed register */
+ done_mask = ioread32(hcr_base + CC);
+
+ /* Workaround for data length mismatch errata */
+ if (unlikely(hstatus
On Fri, 31 Aug 2012 11:03:45 -0700
Nick Pasich n...@nickandbarb.net wrote:
On Fri, Aug 31, 2012 at 09:21:38AM -0700, Jeff Layton wrote:
On Fri, 31 Aug 2012 08:32:06 -0700
Nick Pasich n...@nickandbarb.net wrote:
On Fri, Aug 31, 2012 at 12:00:26PM +0400, Pavel Shilovsky wrote:
On Thu, Sep 6, 2012 at 1:48 PM, Jean Delvare kh...@linux-fr.org wrote:
It doesn't seem this spinlock was properly initialized.
Quiet possible. There's no SMP on m68k, so all spinlock ops expand to nothing.
Signed-off-by: Jean Delvare kh...@linux-fr.org
Cc: Finn Thain
On Wed 05-09-12 13:12:38, Tejun Heo wrote:
Hello, Michal.
On Wed, Sep 05, 2012 at 04:49:42PM +0200, Michal Hocko wrote:
Can we settle on the following 3 steps?
1) warn about flat hierarchies (give it X releases) - I will push it
to as many Suse code streams as possible (hope other
On 09/06/2012 07:49 AM, Paolo Bonzini wrote:
Il 06/09/2012 13:31, Ric Wheeler ha scritto:
Both of these commands are destructive. WRITE_SAME (if done without the
discard bits set) can also take a very long time to be destructive and
tie up the storage.
FORMAT_UNIT has the same characteristics
Hello Masami Hiramatsu
After read your mail [RFC PATCH -tip 00/16] in-kernel x86 disassember
to linux-kernel@vger.kernel.org
I am very interested in your patch for x86 disassembler. I think it is
valuable (at least, for me).
The link git://github.com/mhiramat/linux.git SEEMS for integrated
Hello,
Generated on top of:
git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/omap
Changed since v2:
- Added commit message to patch 2 (as Tero requested it)
- Fixed patch 6 (dt: Add empty...) since the previous patch caused x86_64 build
to fail due to missing struct before
To clean up the module probe and remove functions.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl4030-audio.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/mfd/twl4030-audio.c b/drivers/mfd/twl4030-audio.c
index
CFG_BOOT register's HFCLK_FREQ field hold information about the used HFCLK
frequency.
Add possibility for users to get the configured rate based on this
register.
This register was configured during boot, without it the chip would not
operate correctly, so we can trust on this information.
This commit adds an empty of_find_node_by_name() function for !CONFIG_OF
builds.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
include/linux/of.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/of.h b/include/linux/of.h
index 1b11632..5c7a158 100644
---
Remove the use of set_hs_extmute callback and let the codec driver to
handle the extmute GPIO.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 9 ++---
arch/arm/mach-omap2/include/mach/board-zoom.h | 2 --
sound/soc/omap/zoom2.c
We no longer have users for the set_hs_extmute callback which has been
replaced by hs_extmute_gpio so the codec driver can handle the external
mute if it is needed by the board.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
include/linux/i2c/twl.h| 2 --
sound/soc/codecs/twl4030.c
On 09/06/2012 04:06 PM, Michal Hocko wrote:
On Wed 05-09-12 13:12:38, Tejun Heo wrote:
Hello, Michal.
On Wed, Sep 05, 2012 at 04:49:42PM +0200, Michal Hocko wrote:
Can we settle on the following 3 steps?
1) warn about flat hierarchies (give it X releases) - I will push it
to as many Suse
When the kernel has been booted with DT blob the platform data is NULL for
the driver.
We need to construct the pdata based on the DT information for runtime use.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c | 57
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 kmalloc(GFP_ATOMIC).
Interesting.
Do you intend to develop a driver patch using
The external mute (if it is in use) is handled by a GPIO line. Prepare to
remove the set_hs_extmute callback and replace it with:
hs_extmute_gpio: the GPIO number to use for external mute
When the users of set_hs_extmute has been converted the callback can be removed.
Signed-off-by: Peter
Allocate the private data with devm_kzalloc.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/codecs/twl4030.c b/sound/soc/codecs/twl4030.c
index 27ccea4..413e698 100644
---
Access the pdata via a pointer within the twl4030_priv structure.
In preparation for DeviceTree support.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
Add support when the kernel has been booted with DT blob. In this case the
pdata is NULL, we need to reach up to the core node and check if the codec
part has been enabled to determine if we need to coexist with the codec or
not.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Support for loading the twl4030 audio module via devicetree.
Sub devices for codec and vibra will be created as mfd devices once the
core MFD driver is loaded when the kernel is booted with a DT blob.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Hi,
On Mon, Aug 6, 2012 at 6:37 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree
On Thu, Sep 06, 2012 at 12:18:31PM +0530, Naveen N. Rao wrote:
I know I'm contradicting the feedback you got from Borislav here, but
is this code churn really worth it to save 40 bytes? I don't think
so.
Well, to answer Tony's question, I wanted to have all those config
booleans at the
Place the MODULE_* lines in the same block and add MODULE_DESCRIPTION.
Rearange the platform_driver structure at the same time.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl4030-audio.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
twl-core has API to get the boot time configured HFCLK rate which has the
same rate as the audio MCLK.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl4030-audio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/twl4030-audio.c
To facilitate the device tree support the probe function need to be rearanged.
Small cleanup in the APLL frequency selection part as well.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl4030-audio.c | 34 --
1 file changed, 16
On Thu 06-09-12 16:09:20, Glauber Costa wrote:
On 09/06/2012 04:06 PM, Michal Hocko wrote:
On Wed 05-09-12 13:12:38, Tejun Heo wrote:
Hello, Michal.
On Wed, Sep 05, 2012 at 04:49:42PM +0200, Michal Hocko wrote:
Can we settle on the following 3 steps?
1) warn about flat hierarchies
Namjae Jeon linkinj...@gmail.com 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
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 setup
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
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 vikram.pand...@ti.com
Software flow control register bits were not defined correctly.
Also clarify the IXON and IXOFF logic to reflect what
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?
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, any
On Tue, Aug 21, 2012 at 3:29 AM, Mel Gorman mgor...@suse.de 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
On Thu, 06 Sep 2012 18:04:27 +0530
Naveen N. Rao naveen.n@linux.vnet.ibm.com 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
From: Philipp Zabel p.za...@pengutronix.de
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 p.za...@pengutronix.de
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
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.
It
To make the code more flexible.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Shawn Guo shawn@linaro.org
Reviewed-by: Benoît Thébaudeau benoit.thebaud...@advansee.com
---
drivers/pwm/pwm-imx.c | 145 -
1 file changed, 82
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Shawn Guo shawn@linaro.org
Reviewed-by: Benoît Thébaudeau benoit.thebaud...@advansee.com
---
drivers/pwm/pwm-imx.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/pwm/pwm-imx.c
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
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 s.ha...@pengutronix.de
Reviewed-by: Shawn Guo shawn@linaro.org
From: Philipp Zabel p.za...@pengutronix.de
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
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Shawn Guo shawn@linaro.org
Reviewed-by: Benoît Thébaudeau benoit.thebaud...@advansee.com
---
arch/arm/boot/dts/imx53.dtsi| 14 ++
arch/arm/mach-imx/clk-imx51-imx53.c |4
2 files changed, 18
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
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
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 shubhrajy...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
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
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 shubhrajy...@ti.com
Acked-by: Santosh
before removing the driver, let's make sure
to force device into a suspended state in order
to conserve power.
Tested-by: Shubhrajyoti D shubhrajy...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/tty/serial/omap-serial.c | 1 +
1
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 shubhrajy...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
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 shubhrajy...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/tty/serial/omap-serial.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 shubhrajy...@ti.com
Signed-off-by: Ruchika Kharwar
From: Ruchika Kharwar ruch...@ti.com
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
From: Vikram Pandita vikram.pand...@ti.com
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 shubhrajy...@ti.com
Signed-off-by: Vikram Pandita
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 shubhrajy...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
enable RX FIFO for 16 characters and TX FIFO
for 16 spaces.
Tested-by: Shubhrajyoti D shubhrajy...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/tty/serial/omap-serial.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/omap-serial.c
On Thu, Sep 06 2012, Lai Jiangshan wrote:
+found:
+ next_pfn = page_to_pfn(page);
+ list_for_each_entry_from(page, isolated_pages, lru) {
+ if (page_to_pfn(page) != next_pfn)
+ return false;
+ pfn = page_to_pfn(page);
+ pfn =
this driver doesn't use any from plat/dmtimer.h, so
we can remove it without any problems.
This will, however cause a problem because omap-serial.c
was relying on indirect inclusion of linux/platform_device.h,
let's fix the issue by including linux/platform_device.h
on omap-serial.c as it should
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 has been missing from OMAP UART driver
for quite a while and it's simple enough
to implement it.
Tested-by: Shubhrajyoti D shubhrajy...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/tty/serial/omap-serial.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
From: Ruchika Kharwar ruch...@ti.com
pm_runtime_enable() needs to be invoked before
pm_runtime_use_autosuspend(), and
pm_runtime_set_autosuspend_delay() functions.
Tested-by: Shubhrajyoti D shubhrajy...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Ruchika Kharwar
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
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 shubhrajy...@ti.com
Acked-by: Santosh Shilimkar
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
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()
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
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 s.ha...@pengutronix.de
Reviewed-by: Shawn Guo shawn@linaro.org
Reviewed-by: Benoît Thébaudeau benoit.thebaud...@advansee.com
---
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 shubhrajy...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
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 shubhrajy...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/tty/serial/omap-serial.c | 330
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
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, ldisc);
Baffled at this point. If you set some other
+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) (start_pfn pfn +
As the pwm driver now is devicetree only, remove the platform
support for this device.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
arch/arm/mach-imx/clk-imx21.c |1 -
arch/arm/mach-imx/clk-imx25.c |8 ---
arch/arm/mach-imx/clk-imx27.c
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 don'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
+++
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, unfortunately...
OK,
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
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 already
has
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()
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 implements the architecture backend for transparent hugepages
on s390.
Signed-off-by: Gerald Schaefer gerald.schae...@de.ibm.com
---
arch/s390/Kconfig | 1 +
arch/s390/include/asm/hugetlb.h | 18 +---
arch/s390/include/asm/pgtable.h | 189
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 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
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 places where the
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.
901 - 1000 of 1542 matches
Mail list logo
