On 09/27/2013 02:22 PM, Uwe Kleine-König wrote:
> I still have a few such fixes in the queue, but as they are all
> independant of each other I think it would be best if you took it.
Queued up for 3.12-rc3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On 27 September 2013 00:16, Grant Grundler wrote:
> On Thu, Sep 26, 2013 at 2:56 PM, Grant Grundler wrote:
>> On Wed, Sep 25, 2013 at 7:37 PM, Chris Ball wrote:
>>> Hi,
>>>
>>> On Wed, Sep 25 2013, Chris Ball wrote:
Hi,
On Fri, Sep 20 2013, Ulf Hansson wrote:
> On 19
On 9/27/2013 5:58 AM, Joel Fernandes wrote:
> On 09/26/2013 06:13 PM, Olof Johansson wrote:
>> On Thu, Sep 26, 2013 at 2:55 PM, Joel Fernandes wrote:
>>> HWMOD removal for MMC is breaking edma_start as the events are being
>>> manually
>>> triggered due to unused channel list not being clear.
Hi,
I'm interested in cross-compiling for ARM v8, and fixing some early
papercuts to begin with; my host machine is a normal x86_64 box.
Although I managed to use Linaro's toolchain [1] to build an Aarch64
kernel, and found a suitable rootfs [2] to use it with, I am not able
to find an ARM64
On 26 September 2013 17:40, Nicolas Pitre wrote:
> On Thu, 26 Sep 2013, Ulf Hansson wrote:
>
>> Suspend and resume of cards are handled by the protocol layer and
>> consequently the mmc_suspend|resume_host APIs are marked as deprecated.
>
> Having the protocol layer take care of card suspend is
Hello,
On Fri, Sep 27, 2013 at 08:26:58AM +, Vineet Gupta wrote:
> On 09/27/2013 01:47 PM, Uwe Kleine-König wrote:
> > On Thu, Sep 26, 2013 at 12:01:49PM +, Vineet Gupta wrote:
> >> On 09/25/2013 02:35 AM, Uwe Kleine-König wrote:
> >>> clockevents_config_and_register is more clever and
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/misc/mic/card/mic_x100.c: In function 'mic_init':
drivers/misc/mic/card/mic_x100.c:215:9: error: implicit declaration of function
'cpu_data' [-Werror=implicit-function-declaration]
Hi Feng,
On 2013-09-27 02:19, Feng Kan wrote:
This driver setup the AHBC for SPI and SD drivers to use.
That's a bit thin for a description. What is AHBC? How does it relate
to SPI and SD? How is it used?
Signed-off-by: Feng Kan
---
arch/arm64/boot/dts/apm-storm.dtsi |6 +
On 09/27/2013 04:24 AM, Rob Herring wrote:
From: Rob Herring
Add cpuidle support for Calxeda ecx-2000 SoC.
Signed-off-by: Rob Herring
Cc: "Rafael J. Wysocki"
Cc: Daniel Lezcano
Cc: linux...@vger.kernel.org
Acked-by: Daniel Lezcano
Shall I pick these three patches in my tree ?
--
On 09/27/2013 04:24 AM, Rob Herring wrote:
From: Rob Herring
Wnen powergating the core, we need to call cpu pm notifiers to save VFP
state (!SMP only) and resetting the breakpoint h/w.
Signed-off-by: Rob Herring
Cc: "Rafael J. Wysocki"
Cc: Daniel Lezcano
Cc: linux...@vger.kernel.org
On 09/27/2013 04:24 AM, Rob Herring wrote:
From: Rob Herring
This updates the Calxeda cpuidle driver to use PSCI calls to powergate
cores. This is needed to enable cpuidle for the ECX-2000.
This could possibly become a generic PSCI driver, but there are no other
PSCI users in the kernel other
Hi Sergei
On Thu, 26 Sep 2013, Sergei Shtylyov wrote:
> Hello.
>
> On 09/26/2013 09:21 PM, Guennadi Liakhovetski wrote:
>
> > The Lager board uses a DA9210 voltage regulator to supply DVFS power to the
> > CA15 cores on the r8a7790 SoC. This patch adds CPUFreq support for that
> > board using
On Thu, Sep 26, 2013 at 04:02:54AM +0100, Al Viro wrote:
> On Wed, Sep 25, 2013 at 05:22:51PM -0700, Linus Torvalds wrote:
> > On Wed, Sep 25, 2013 at 1:14 PM, Djalal Harouni wrote:
> > >
> > > Therefor add the f_cred field to the seq_file struct and a helper
> > > seq_f_cred() to return it.
> >
On Thu, Sep 26, 2013 at 03:51:48PM +0100, Oussama Ghorbel wrote:
> The (inner) MTU of a ipip6 (IPv4-in-IPv6) tunnel cannot be set below 1280,
> which is the minimum MTU in IPv6.
> However, there should be no IPv6 on the tunnel interface at all, so the IPv6
> rules should not apply.
> More info
On Wed, Sep 25, 2013 at 05:22:51PM -0700, Linus Torvalds wrote:
> On Wed, Sep 25, 2013 at 1:14 PM, Djalal Harouni wrote:
> >
> > Therefor add the f_cred field to the seq_file struct and a helper
> > seq_f_cred() to return it.
>
> I hate how you've split up this patch from the next one that
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from include/linux/kernel.h:14:0,
from include/linux/debug_locks.h:4,
from include/linux/lockdep.h:23,
from
Hi Linus, Yinghai !
Please consider reverting:
928bea964827d7824b548c1f8e06eccbbc4d0d7d
PCI: Delay enabling bridges until they're needed
(I'd suggest to revert now and maybe merge a better patch later)
This breaks PCI on the PowerPC "powernv" platform (which is booted via
kexec) and probably
On 09/27/2013 01:47 PM, Uwe Kleine-König wrote:
> On Thu, Sep 26, 2013 at 12:01:49PM +, Vineet Gupta wrote:
>> On 09/25/2013 02:35 AM, Uwe Kleine-König wrote:
>>> clockevents_config_and_register is more clever and correct than doing it
>>> by hand; so use it.
>>>
>>> Signed-off-by: Uwe
kbasename() returns the filename part of a pathname.
Signed-off-by: Andy Shevchenko
---
arch/tile/kernel/stack.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/arch/tile/kernel/stack.c b/arch/tile/kernel/stack.c
index 362284a..c93977a 100644
---
On Mon, 23 Sep 2013, Matthias Kaehlcke wrote:
> The ADC clock divider needs to be restored on resume as the register content
> is lost when the ADC is powered down
>
> Signed-off-by: Matthias Kaehlcke
>
> ---
> drivers/mfd/ti_am335x_tscadc.c | 10 ++
>
From: Wei Yongjun
It's not necessary to free regulator consumers allocated with
devm_regulator_bulk_get.
Signed-off-by: Wei Yongjun
---
sound/soc/codecs/wm8993.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/wm8993.c b/sound/soc/codecs/wm8993.c
index 433d59a..2ee23a3
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/tty/serial/8250/8250_dw.c: In function 'dw8250_probe':
drivers/tty/serial/8250/8250_dw.c:341:3: error: too many arguments to function
'dw8250_probe_acpi'
err = dw8250_probe_acpi(,
On Thu, Sep 26, 2013 at 12:01:49PM +, Vineet Gupta wrote:
> On 09/25/2013 02:35 AM, Uwe Kleine-König wrote:
> > clockevents_config_and_register is more clever and correct than doing it
> > by hand; so use it.
> >
> > Signed-off-by: Uwe Kleine-König
>
> Acked-by: Vineet Gupta
Thanks for the
On Fri, Sep 27, 2013 at 04:43:13AM +0200, Wolfram Sang wrote:
> On Fri, Sep 27, 2013 at 12:24:03AM +0200, Vincent Stehlé wrote:
> > Make sure i2c_dw_pci_runtime_idle() is defined only when actually used, when
> > CONFIG_PM_RUNTIME is defined.
> >
> > This fixes the following compilation warning:
From: Wei Yongjun
It's not necessary to free regulator consumers allocated with
devm_regulator_bulk_get.
Signed-off-by: Wei Yongjun
---
sound/soc/codecs/wm8993.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/wm8993.c b/sound/soc/codecs/wm8993.c
index 433d59a..2ee23a3
From: Jiang Liu
Disable lazy load if FPSIMD registers are frequently used by the thread,
so we can reduce overhead of lazy FPSIMD restore for FPU extensive
applications. The thresholds are randomly chosen without thorough
benchmarks, we may need to tune it for really systems.
Signed-off-by:
On Fri, 27 Sep 2013, Andrzej Hajda wrote:
> This patch adds only of_match_table.
> There are no device specific properties.
>
> Signed-off-by: Andrzej Hajda
> Reviewed-by: Sylwester Nawrocki
> Signed-off-by: Kyungmin Park
> ---
> Hi,
>
> Spaces added.
>
> Regards
> Andrzej
> ---
>
From: Jiang Liu
Use PF_USED_MATH flag to mark whether the thread has accessed any FPSIMD
registers, so we could avoid saving and restroing FPSIMD registers until
threads access them. This may improve performance when lazy FPSIMD restore
is disabled.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
From: Jiang Liu
Reuse FPSIMD hardware context if it hasn't been touched by other thread
yet, so we can get rid of unnecessary FPSIMD context restores. This is
especially useful when switching between kernel thread and user thread
because kernel thread usaually doesn't touch FPSIMD registers.
From: Jiang Liu
Provide tristate kernel boot option "eagerfpu" to control FPSIMD state
save and restore policy. It adopts the same scematics as x86.
The lazy FPSIMD restore policy needs to configured before any thread
makes use of FPSIMD registers, so change fpsimd_init() as arch_initcall.
From: Jiang Liu
Implement basic lazy save and restore for FPSIMD registers, which only
restore FPSIMD state on demand and save FPSIMD state if it has been
loaded on to hardware.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/include/asm/fpsimd.h | 17 ++---
arch/arm64/kernel/fpsimd.c
From: Jiang Liu
Restore FPSIMD control and status registers to default values
when creating new FPSIMD contexts for kernel and signal handling,
otherwise the stale value in FPSIMD control and status registers
may affect the new kernal or signal handling contexts.
Signed-off-by: Jiang Liu
Cc:
From: Jiang Liu
If context switching happens during executing fpsimd_flush_thread(),
stale value in FPSIMD registers will be saved into current thread's
fpsimd_state by fpsimd_thread_switch(). That may cause invalid
initialization state for the new process, so disable preemption
when executing
On Thu, 26 Sep 2013, Laxman Dewangan wrote:
> The driver only support the device tree and sub modules are populated
> through platform, the registration of sub devices through mfd_add_devices
> has been removed.
>
> Hence in remove path of the driver, it is not require to call
>
From: Jiang Liu
This patchset enables FPSIMD lazy save and restore for ARM64, you could
apply it against v3.12-rc2.
We have done basic functional tests on ARM fast model, but still lack
of detail performance benchmark on real hardware platforms. We would
appreciate if you could help to test it
Enable ARCH_USE_CMPXCHG_LOCKREF for 64 bit since it shows performance
improvements with Linus' simple stat() test case of up to 50% on a
30 cpu system.
Signed-off-by: Heiko Carstens
---
arch/s390/Kconfig| 1 +
arch/s390/include/asm/spinlock.h | 5 +
2 files changed, 6
On Thu, 26 Sep 2013, Laxman Dewangan wrote:
> Signed-off-by: Laxman Dewangan
> ---
> drivers/mfd/palmas.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mfd/palmas.c b/drivers/mfd/palmas.c
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing
Make use of cpu_relax_simple() so architectures can override the default
cpu_relax() semantics.
This is especially useful for s390, where cpu_relax() means that the we
yield() the current (virtual) cpu and therefore is very expensive.
Signed-off-by: Heiko Carstens
---
lib/lockref.c | 2 +-
1
s390 needs a special version of cpu_relax() for the new lockref code.
The new variant should be a no-op but also have memory barrier semantics,
since that is what the default cpu_relax() variant implements.
Actually s390 had the same problem already in the past where we implemented
Hi all,
enabling the new lockless lockref variant on s390 would have been trivial
until Tony Luck added a cpu_relax() call into the CMPXCHG_LOOP(), with
d472d9d9 "lockref: Relax in cmpxchg loop".
As already mentioned cpu_relax() is very expensive on s390 since it yields()
the current virtual
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/mm/init.c: In function 'memory_map_bottom_up':
arch/x86/mm/init.c:512:18: error: 'STEP_SIZE_SHIFT' undeclared (first use in
this function)
step_size <<= STEP_SIZE_SHIFT;
On Thu, 26 Sep 2013, Laxman Dewangan wrote:
> If Palams supports the system power controller and pm_power_off
> is implemented through the Palmas driver then reset the pm_power_off
> in driver remove.
>
> This will avoid the call of Palmas driver after removal of driver.
>
> Signed-off-by:
On 9/27/2013 5:58 AM, Joel Fernandes wrote:
> On 09/26/2013 06:13 PM, Olof Johansson wrote:
>> On Thu, Sep 26, 2013 at 2:55 PM, Joel Fernandes wrote:
>>> HWMOD removal for MMC is breaking edma_start as the events are being
>>> manually
>>> triggered due to unused channel list not being clear.
Hi,
On Wed, Sep 25, 2013 at 03:47:14PM -0700, Tim Kryger wrote:
> On Wed, Sep 25, 2013 at 4:42 AM, Heikki Krogerus
> wrote:
> > On Tue, Sep 24, 2013 at 05:39:09PM -0700, Tim Kryger wrote:
> >> static void dw8250_serial_out(struct uart_port *p, int offset, int value)
> >> {
> >> struct
On Thu, 26 Sep 2013, Laxman Dewangan wrote:
> Palmas device supports multiple i2c device address and the client
> for these addressed are created in the driver as i2c_new_dummy().
>
> The new devices are not getting released in error or removal path and
> so it is causing resource leak.
>
> Add
On Wed, 25 Sep 2013, David Howells wrote:
>
> Hi James,
>
> Could you pull these patches into the security tree? They're based on your
> next branch.
>
Thanks, pulled.
> The patches can be viewed as a number of sets:
>
> (1) KEYS: Skip key state checks when checking for possession
>
>
* Daniel Lezcano wrote:
> On 09/27/2013 07:49 AM, Ingo Molnar wrote:
> >
> >* Daniel Lezcano wrote:
> >
> >>Hi Thomas,
> >>
> >>this pull request contains several fixes for the clocksource/clockevent
> >>drivers:
> >>
> >> - Jean Pihet fixed a missing Kconfig option preventing the
On 09/27/2013 01:18 AM, Stephen Warren wrote:
> On 09/24/2013 01:58 AM, Javier Martinez Canillas wrote:
>> The OMAP GPIO controller HW requires a pin to be configured in GPIO
>> input mode in order to operate as an interrupt input. Since drivers
>> should not be aware of whether an interrupt pin
> The patch removes wakeup related code from
> the driver and plaftorm data - it is already
> handled by i2c core using I2C_CLIENT_WAKE flag
> from struct i2c_board_info. As a result MFD
> itself do not requires platform data.
I have expanded this to use more than 46 chars of the line
buffer.
This patch adds only of_match_table.
There are no device specific properties.
Signed-off-by: Andrzej Hajda
Reviewed-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
Hi,
Spaces added.
Regards
Andrzej
---
drivers/mfd/max77693.c | 8
1 file changed, 8 insertions(+)
diff --git
On Thu, Sep 26, 2013 at 04:54:41PM +0200, Ulf Hansson wrote:
> Suspend and resume of cards are being handled from the protocol layer
> and consequently the mmc_suspend|resume_host APIs are deprecated.
>
> This means we can simplify the suspend|resume callbacks by removing the
> use of the
Firstly, thank you for your so much contents reply.
On 09/27/2013 11:36 AM, Tejun Heo wrote:
> Hello, Chen.
>
> On Fri, Sep 27, 2013 at 09:30:13AM +0800, Chen Gang wrote:
>> As an integrator or large source code maintainer, we cannot only depend
>> on testing, or tracing log, or some short
On Wed, 21 Aug 2013, Andrzej Hajda wrote:
> This patch adds only of_match_table.
> There are no device specific properties.
>
> Signed-off-by: Andrzej Hajda
> Reviewed-by: Sylwester Nawrocki
> Signed-off-by: Kyungmin Park
> ---
> drivers/mfd/max77693.c | 8
> 1 file changed, 8
Hi,
On 18/09/13 01:29, John Tapsell wrote:
> Do not lock fb_info when calling sending the FB_EVENT_CONBLANK
> event.
>
> In fbmem.c, the semantics are that we acquire the lock_fb_info first,
> and then console_lock. However when fbcon.c fbcon_generic_blank() is
> called, the console lock could
Hi all,
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/misc/mic/host/mic_main.c: In function 'mic_probe':
drivers/misc/mic/host/mic_main.c:320:3: error: too many arguments to function
'sysfs_get_dirent'
NULL, "state");
^
In file
Fix to find the correct (as much as possible) line information
for listing probes. Without this fix, perf probe --list action
will show incorrect line information as below;
# perf probe getname_flags
# perf probe -l
probe:getname_flags (on getname_flags@ksrc/linux-3/fs/namei.c)
On 26/09/13 15:50, Thierry Reding wrote:
>> I thought the NAK was for the DT parts, not for the sequences as such. I
>> don't remember anyone shooting down the idea of defining power sequences
>> inside a driver.
>
> Yes, but the DT parts were the primary reason why they were written in
> the
Hi Arnaldo,
BTW, I also found another issue which the perf probe -l showed
incorrect line number and file name for probes on such inline
functions. :(
I found the root causes (the line info is not correct and
perf probe failed to handle nested inline functions). I'll send
the bugfix patch soon.
On 09/27/2013 07:49 AM, Ingo Molnar wrote:
* Daniel Lezcano wrote:
Hi Thomas,
this pull request contains several fixes for the clocksource/clockevent
drivers:
- Jean Pihet fixed a missing Kconfig option preventing the Armada370/XP
to boot up.
- Magnus Damm fixed the cpumask on the
* Borislav Petkov wrote:
> On Wed, Sep 25, 2013 at 08:29:36PM +0200, Ingo Molnar wrote:
> > Indeed, that should be fixed.
>
> Ok, how does a right alighment look like:
>
> [0.072399] smpboot: Booting Node 0, Processors #1 #2 #3 #4 #5
> #6 #7 OK
> [0.617005] smpboot:
Darren Hart wrote on 2013/09/27 02:15:17:
> Re: [PATCH] futex: Remove the owner check when waking task in
> handle_futex_death
>
> On Thu, 2013-09-26 at 09:09 +0800, zhang.y...@zte.com.cn wrote:
> > Hi all,
> >
> > Task processes all its owned robust futex when it is exiting,
> > to ensure
On 09/27/2013 03:46 AM, Dave Hansen wrote:
> On 09/25/2013 04:14 PM, Srivatsa S. Bhat wrote:
>> @@ -605,16 +713,22 @@ static inline void __free_one_page(struct page *page,
>> buddy_idx = __find_buddy_index(combined_idx, order + 1);
>> higher_buddy = higher_page +
Hi Greg,
On Friday 27 September 2013 12:21 AM, Greg KH wrote:
> On Wed, Aug 21, 2013 at 11:16:07AM +0530, Kishon Vijay Abraham I wrote:
>> Used the generic PHY framework API to create the PHY. Now the power off and
>> power on are done in omap_usb_power_off and omap_usb_power_on respectively.
>>
Hi Laurent
On Fri, 27 Sep 2013, Laurent Pinchart wrote:
> Hi Guennadi,
>
> Thank you for the patch.
>
> On Thursday 26 September 2013 19:21:00 Guennadi Liakhovetski wrote:
> > The Lager board uses a DA9210 voltage regulator to supply DVFS power to the
> > CA15 cores on the r8a7790 SoC. This
If this option is enabled, do we take VM steal time into account when
updating cpu_power?
As a result, there will be less load on vCPUs with smaller cpu_power ?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
* David Ahern wrote:
> On 9/26/13 11:51 AM, Jiri Olsa wrote:
> >but it's still faster, since we finally get perf a chance to sleep ;-)
> >
> >new time:
> > real0m30.392s
> > user0m0.041s
> > sys 0m0.389s
> >
> >old time:
> > real0m32.235s
> > user0m3.080s
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb->xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
On Fri, 2013-09-27 at 08:02 +0200, Ingo Molnar wrote:
> * Tim Chen wrote:
>
> > > If we prefer to optimize this a bit though, perhaps we can first move
> > > the node->lock = 0 so that it gets executed after the "if (likely(prev
> > > == NULL)) {}" code block and then delete "node->lock = 1"
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Reviewed-by: Sylwester Nawrocki
---
drivers/phy/phy-twl4030-usb.c | 57
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
---
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed. Also twl4030-usb driver is moved
to
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/h8300/include/asm/Kbuild between commit 4b0847842204 ("Drop support
for Renesas H8/300 (h8300) architecture") from the h8300-remove tree and
commit a787870924db ("sched, arch: Create asm/preempt.h") from the tip
tree.
I just
We used to use a percpu structure vq_index to record the cpu to queue
mapping, this is suboptimal since it duplicates the work of XPS and
loses all other XPS functionality such as allowing use to configure
their own transmission steering strategy.
So this patch switches to use XPS and suggest a
* Tim Chen wrote:
> > If we prefer to optimize this a bit though, perhaps we can first move
> > the node->lock = 0 so that it gets executed after the "if (likely(prev
> > == NULL)) {}" code block and then delete "node->lock = 1" inside the
> > code block.
>
> I suppose we can save one
* Tim Chen tim.c.c...@linux.intel.com wrote:
If we prefer to optimize this a bit though, perhaps we can first move
the node-lock = 0 so that it gets executed after the if (likely(prev
== NULL)) {} code block and then delete node-lock = 1 inside the
code block.
I suppose we can save
We used to use a percpu structure vq_index to record the cpu to queue
mapping, this is suboptimal since it duplicates the work of XPS and
loses all other XPS functionality such as allowing use to configure
their own transmission steering strategy.
So this patch switches to use XPS and suggest a
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/h8300/include/asm/Kbuild between commit 4b0847842204 (Drop support
for Renesas H8/300 (h8300) architecture) from the h8300-remove tree and
commit a787870924db (sched, arch: Create asm/preempt.h) from the tip
tree.
I just
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed. Also twl4030-usb driver is moved
to
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
On Fri, 2013-09-27 at 08:02 +0200, Ingo Molnar wrote:
* Tim Chen tim.c.c...@linux.intel.com wrote:
If we prefer to optimize this a bit though, perhaps we can first move
the node-lock = 0 so that it gets executed after the if (likely(prev
== NULL)) {} code block and then delete
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
* David Ahern dsah...@gmail.com wrote:
On 9/26/13 11:51 AM, Jiri Olsa wrote:
but it's still faster, since we finally get perf a chance to sleep ;-)
new time:
real0m30.392s
user0m0.041s
sys 0m0.389s
old time:
real0m32.235s
user0m3.080s
If this option is enabled, do we take VM steal time into account when
updating cpu_power?
As a result, there will be less load on vCPUs with smaller cpu_power ?
Thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
Hi Laurent
On Fri, 27 Sep 2013, Laurent Pinchart wrote:
Hi Guennadi,
Thank you for the patch.
On Thursday 26 September 2013 19:21:00 Guennadi Liakhovetski wrote:
The Lager board uses a DA9210 voltage regulator to supply DVFS power to the
CA15 cores on the r8a7790 SoC. This patch adds
Hi Greg,
On Friday 27 September 2013 12:21 AM, Greg KH wrote:
On Wed, Aug 21, 2013 at 11:16:07AM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The
On 09/27/2013 03:46 AM, Dave Hansen wrote:
On 09/25/2013 04:14 PM, Srivatsa S. Bhat wrote:
@@ -605,16 +713,22 @@ static inline void __free_one_page(struct page *page,
buddy_idx = __find_buddy_index(combined_idx, order + 1);
higher_buddy = higher_page + (buddy_idx -
Darren Hart dvh...@linux.intel.com wrote on 2013/09/27 02:15:17:
Re: [PATCH] futex: Remove the owner check when waking task in
handle_futex_death
On Thu, 2013-09-26 at 09:09 +0800, zhang.y...@zte.com.cn wrote:
Hi all,
Task processes all its owned robust futex when it is exiting,
* Borislav Petkov b...@alien8.de wrote:
On Wed, Sep 25, 2013 at 08:29:36PM +0200, Ingo Molnar wrote:
Indeed, that should be fixed.
Ok, how does a right alighment look like:
[0.072399] smpboot: Booting Node 0, Processors #1 #2 #3 #4 #5
#6 #7 OK
[0.617005]
On 09/27/2013 07:49 AM, Ingo Molnar wrote:
* Daniel Lezcano daniel.lezc...@linaro.org wrote:
Hi Thomas,
this pull request contains several fixes for the clocksource/clockevent
drivers:
- Jean Pihet fixed a missing Kconfig option preventing the Armada370/XP
to boot up.
- Magnus Damm
Hi Arnaldo,
BTW, I also found another issue which the perf probe -l showed
incorrect line number and file name for probes on such inline
functions. :(
I found the root causes (the line info is not correct and
perf probe failed to handle nested inline functions). I'll send
the bugfix patch soon.
On 26/09/13 15:50, Thierry Reding wrote:
I thought the NAK was for the DT parts, not for the sequences as such. I
don't remember anyone shooting down the idea of defining power sequences
inside a driver.
Yes, but the DT parts were the primary reason why they were written in
the first
501 - 600 of 1156 matches
Mail list logo
