Cpufreq governor's stop and start operation should be kept in sequence.
If not, there will be unexpected behavior, for example:
There are 4 CPUs and policy->cpu=CPU0, CPU1/2/3 are linked to CPU0.
The normal sequence is as below:
1) Current governor is userspace, One application tries to set
gover
Commit-ID: 29ce3785b22da47c49f4ef6e14b9014fa5dee261
Gitweb: http://git.kernel.org/tip/29ce3785b22da47c49f4ef6e14b9014fa5dee261
Author: James Bottomley
AuthorDate: Wed, 8 May 2013 14:05:34 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 14 Jun 2013 23:01:05 +0200
idle: Enable interrup
On Tue, 18 Jun 2013 18:35:40 +0100
Ben Hutchings wrote:
> On Tue, Jun 18, 2013 at 09:17:39AM -0700, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman
> >
> > 3.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Ben Hutchings
On 17/06/13 23:05, Jiri Slaby wrote:
> The last point I inclined to the Greg's argument to remove the EXPERT
> dependency.
>
> So currently I have what is attached... Comments?
The patch looks a bit odd with the USB_CHIPIDEA_IMX parts. You're not
adding COMPILE_TEST there, but you're adding a to
On Wed, 19 Jun 2013 14:55:13 +0800 Chen Gang wrote:
>
> 'lru' may be used without initialized, so need regressing part of the
> related patch.
>
> The related patch:
> "3abf380 mm: remove lru parameter from __lru_cache_add and
> lru_cache_add_lru"
>
> ...
>
> --- a/mm/vmscan.c
> +++ b/mm/vms
Signed-off-by: Jianpeng Ma
---
fs/ceph/addr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
index 3e68ac1..25fa8b8 100644
--- a/fs/ceph/addr.c
+++ b/fs/ceph/addr.c
@@ -677,8 +677,8 @@ static int ceph_writepages_start(struct address_space
On 06/19/2013 09:10 AM, Tomi Valkeinen wrote:
> On 17/06/13 23:05, Jiri Slaby wrote:
>
>> The last point I inclined to the Greg's argument to remove the
>> EXPERT dependency.
>>
>> So currently I have what is attached... Comments?
>
> The patch looks a bit odd with the USB_CHIPIDEA_IMX parts. Yo
Hi Greg,
On Wed, 19 Jun 2013 15:32:25 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the driver-core tree got a conflict in
> drivers/base/firmware_class.c between commit 875979368eb4 ("firmware
> loader: fix use-after-free by double abort") from the driver-core.current
> tree and
On Tue 18-06-13 10:26:24, Glauber Costa wrote:
[...]
> Michal, would you mind testing the following patch?
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 00b804e..48eafa6 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -419,6 +419,8 @@ void inode_add_lru(struct inode *inode)
>
> static void
On 06/19/2013 02:31 PM, Eric Dumazet wrote:
> On Wed, 2013-06-19 at 13:40 +0800, Jason Wang wrote:
>> Currently, we use kcalloc to allocate rx/tx queues for a net device which
>> could
>> be easily lead to a high order memory allocation request when initializing a
>> multiqueue net device. We can
On Tue, 18 Jun 2013 15:44:56 +0200, Lukasz Majewski wrote:
Dear Viesh, Rafael,
> >
> > I'd recommend you both to read Documentation/cpu-freq/boost.txt
> > now. :-)
>
>
> According to the documentation:
> "Reading the file is always supported, even if the processor does not
> support boosting
On 06/19/2013 02:34 PM, Eric Dumazet wrote:
> On Wed, 2013-06-19 at 13:40 +0800, Jason Wang wrote:
>> Since we've reduce the size of tun_struct and use flex array to allocate
>> netdev
>> queues, it's safe for us to increase the limit of queues in tuntap.
> Its already safe to increase max queues
On 06/19/2013 03:10 PM, Andrew Morton wrote:
> On Wed, 19 Jun 2013 14:55:13 +0800 Chen Gang wrote:
>
>> >
>> > 'lru' may be used without initialized, so need regressing part of the
>> > related patch.
>> >
>> > The related patch:
>> > "3abf380 mm: remove lru parameter from __lru_cache_add and
On 19/06/13 10:12, Jiri Slaby wrote:
> On 06/19/2013 09:10 AM, Tomi Valkeinen wrote:
>> On 17/06/13 23:05, Jiri Slaby wrote:
>>
>>> The last point I inclined to the Greg's argument to remove the
>>> EXPERT dependency.
>>>
>>> So currently I have what is attached... Comments?
>>
>> The patch looks a
On Wed, Jun 19, 2013 at 3:12 PM, Stephen Rothwell wrote:
> Hi Greg,
>
> On Wed, 19 Jun 2013 15:32:25 +1000 Stephen Rothwell
> wrote:
>>
>> Today's linux-next merge of the driver-core tree got a conflict in
>> drivers/base/firmware_class.c between commit 875979368eb4 ("firmware
>> loader: fix use
Hi Vasilis, Yinghai,
On 06/19/2013 01:05 AM, Vasilis Liaskovitis wrote:
..
This could be a design problem of part3: if we allow local pagetable memory
to not be offlined but allow the offlining to return successfully, then
hot-remove is going to succeed. But the direct mapped pagetable page
On Tue, Jun 18, 2013 at 12:37:45AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 781d737 (ACPI: Drop power resources driver) introduced a
> bug in the power resources initialization error code path causing
> a NULL pointer to be referenced in acpi_release_power_resource()
>
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
fs/ext4/extents_status.c between commit 6480bad916be ("ext4: improve
extent cache shrink mechanism to avoid to burn CPU time") from the ext
tree and commit 1f42d0934b4e ("fs: convert fs shrinkers to new scan/count
API") from th
On Wed, Jun 19, 2013 at 09:13:46AM +0200, Michal Hocko wrote:
> On Tue 18-06-13 10:26:24, Glauber Costa wrote:
> [...]
> > Michal, would you mind testing the following patch?
> >
> > diff --git a/fs/inode.c b/fs/inode.c
> > index 00b804e..48eafa6 100644
> > --- a/fs/inode.c
> > +++ b/fs/inode.c
> >
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
> Hi Roger,
>
> On 06/18/2013 11:04 AM, Roger Quadros wrote:
>> Provide the RESET and Power regulators for the USB PHY,
>> the USB Host port mode and the PHY device.
>>
>> Also provide pin multiplexer information for the USB host
>> pins.
>
On 19.06.2013 07:20, Linus Torvalds wrote:
>> No crash in 2 days running with preempt none...
>
> Is this UP?
Yes it is.
> There's the fast_tlb race that Peter fixed in commit 29eb77825cc7
> ("arch, mm: Remove tlb_fast_mode()"). I'm not seeing how it would
> cause infinite TLB faults, but it de
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
arch/arm/kernel/process.c between commit 19ab428f4b79 ("ARM: 7759/1:
decouple CPU offlining from reboot/shutdown") from the tree and commit
("reboot: move arch/x86 reboot= handling to generic kernel") from the
akpm tree.
I fi
On Tue, Jun 18, 2013 at 07:09:48PM +0100, Mark Brown wrote:
> On Tue, Jun 18, 2013 at 05:29:45PM +0300, Mika Westerberg wrote:
> > Current code calls pm_runtime_suspended() in the interrupt handler to check
> > if the device is suspended or not. However, runtime PM status of the device
> > is only
> Quoting Arnd Bergmann (2013-06-12 07:46:30)
> > On Tuesday 11 June 2013, Lee Jones wrote:
> > > This patch enables clocks to be specified from Device Tree via phandles
> > > to the "prcc-kernel-clock" node.
> > >
> > > Cc: Mike Turquette
> > > Cc: Ulf Hansson
> > > Signed-off-by: Lee Jones
>
On Wed, Jun 19, 2013 at 05:27:21PM +1000, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got a conflict in
> fs/ext4/extents_status.c between commit 6480bad916be ("ext4: improve
> extent cache shrink mechanism to avoid to burn CPU time") from the ext
> tree and
Hi Tushar,
On Wednesday 19 of June 2013 10:20:14 Tushar Behera wrote:
> On 06/17/2013 10:20 AM, Tushar Behera wrote:
> > On 06/11/2013 12:23 AM, Tomasz Figa wrote:
> >> On Monday 10 of June 2013 09:13:11 Tushar Behera wrote:
> >>> On 06/08/2013 05:20 PM, Tomasz Figa wrote:
> On Thursday 06 of
* Roger Quadros [130619 00:42]:
> Hi Benoit,
>
> On 06/19/2013 04:17 AM, Benoit Cousson wrote:
> > Hi Roger,
> >
> > On 06/18/2013 11:04 AM, Roger Quadros wrote:
> >> Provide the RESET and Power regulators for the USB PHY,
> >> the USB Host port mode and the PHY device.
> >>
> >> Also provide pi
Hi,
On Wed, 19 Jun 2013 11:44:04 +0400 Glauber Costa wrote:
>
> I believe the resolution is okay, at least from our PoV.
Thanks for checking.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpBSc9vjcXZb.pgp
Description: PGP signature
Hi Chao,
On 06/19/2013 05:31 AM, Chao Xie wrote:
> Some controller need software to initialize PHY before add
> host controller, and shut down PHY after remove host controller.
> Add the generic code for these controllers so they do not need
> do it in its own host controller driver.
>
> Signed-o
In build, we open a file, read that but do not close it. Fix that by
sticking fclose at the right place.
Signed-off-by: Jiri Slaby
Cc: "H. Peter Anvin"
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: x...@kernel.org
---
arch/x86/boot/tools/build.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/a
Hi Stephen,
On Jun 19, 2013, at 3:27 PM, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got a conflict in
> fs/ext4/extents_status.c between commit 6480bad916be ("ext4: improve
> extent cache shrink mechanism to avoid to burn CPU time") from the ext
> tree an
On 19 June 2013 12:30, Xiaoguang Chen wrote:
> Cpufreq governor's stop and start operation should be kept in sequence.
> If not, there will be unexpected behavior, for example:
>
> There are 4 CPUs and policy->cpu=CPU0, CPU1/2/3 are linked to CPU0.
> The normal sequence is as below:
>
> 1) Current
On Wed, 19 Jun 2013, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Replace probe-time ioremap_nocache() call with devm_ioremap_nocache()
> to avoid iounmap() missing and get rid of the corresponding iounmap()
> call on remove.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/mfd/htc-egpio.c | 4 ++
On Tue, 18 Jun 2013, Sachin Kamat wrote:
> devm_* APIs are device managed and make code simpler.
>
> Signed-off-by: Sachin Kamat
> Cc: Miguel Aguilar
> ---
> drivers/mfd/davinci_voicecodec.c | 48
> +++-
> include/linux/mfd/davinci_voicecodec.h |2 --
>
Hi all,
After merging the final tree, today's linux-next build (powerpc
allnoconfig among others) produced these warnings:
drivers/base/firmware_class.c:1254:12: warning: 'cache_firmware' defined but
not used [-Wunused-function]
static int cache_firmware(const char *fw_name)
^
drive
On Wed, Jun 19, 2013 at 09:36:39AM +0200, Stanislav Meduna wrote:
> On 19.06.2013 07:20, Linus Torvalds wrote:
>
> >> No crash in 2 days running with preempt none...
> >
> > Is this UP?
>
> Yes it is.
>
> > There's the fast_tlb race that Peter fixed in commit 29eb77825cc7
> > ("arch, mm: Remove
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from
drivers/staging/lustre/include/linux/libcfs/libcfs.h:203:0,
from drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h:67,
from drivers/st
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
This is based off of current Linus tree.
Signed-off-by: Alexey Brodkin
Cc: Andy Shevchenko
Cc: Francois Romieu
Cc: Joe Perches
Cc: Vineet Gupta
Cc
On 06/18/2013 05:44 PM, Alex Shi wrote:
>
>>
>> Paul, could I summary your point here:
>> keep current weighted_cpu_load, but add blocked load avg in
>> get_rq_runnable_load?
>>
>> I will test this change.
>
> Current testing(kbuild, oltp, aim7) don't show clear different on my NHM EP
> box
> be
On Tue, 18 Jun 2013, Tuomas Tynkkynen wrote:
> Commit "i2c: core: make it possible to match a pure device tree driver"
> changed semantics of the i2c probing for device tree devices.
> Device tree probed devices now get a NULL i2c_device_id pointer.
> This caused kernel panics due to NULL derefere
* Andi Kleen wrote:
> v13:
> Various white space changes.
> v14:
> Rebased to 3.10-rc6
FYI, I'll have a look at your patches in the coming days.
As I warned you in the past your very slow, piecemail-wise, feet-dragging
response to review feedback which has resulted in a supposedly simple perf
On Wed, Jun 19, 2013 at 12:25:14PM +0930, Rusty Russell wrote:
> But it's quite OK to ignore OOM errors in builtin init functions.
I think it'd be cleaner to let those use cases use BUG_ON() around it.
We really want most users to be checking its return value.
> It would be neatest to have it fai
Dear Chao Xie,
> Signed-off-by: Chao Xie
> ---
> .../devicetree/bindings/input/pxa27x-keypad.txt| 60 +
> drivers/input/keyboard/pxa27x_keypad.c | 232
> +++- 2 files changed, 288 insertions(+), 4 deletions(-)
> create mode 100644
> Documentation/devicetree
Hi Florian,
On Tue, Jun 18, 2013 at 03:17:55PM +0200, Florian Vaussard wrote:
> Hello,
>
> This series enables a partial DT support for twl4030-power. The
> missing part is the power management scripts, as the required
> binding should be defined first. It however enables the complete
> shutdown
On Wed, Jun 19, 2013 at 09:31:10AM +0800, Li Zefan wrote:
> Hi Tejun,
>
> Could you apply this patch?
Oops, I thought I applied this one. Apparently not.
> On 2013/6/14 11:17, Li Zefan wrote:
> > Cont is short for container. control group was named process container
> > at first, but then peopl
Hi Stephen,
On Tue, Jun 18, 2013 at 05:19:57PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/88pm800.c: In function 'pm800_pages_init':
> drivers/mfd/88pm800.c:434:2: error: implicit
On Wed, Jun 19, 2013 at 10:44:09AM +1000, Stephen Rothwell wrote:
> Hi Lorenzo,
>
> Today's linux-next merge of the arm-mpidr tree got a conflict in
> arch/arm/kernel/suspend.c between commit aa1aadc3305c ("ARM: suspend: fix
> CPU suspend code for !CONFIG_MMU configurations") from the arm tree and
Hi Lee,
On Wed, Jun 19, 2013 at 09:18:59AM +0100, Lee Jones wrote:
> On Tue, 18 Jun 2013, Tuomas Tynkkynen wrote:
>
> > Commit "i2c: core: make it possible to match a pure device tree driver"
> > changed semantics of the i2c probing for device tree devices.
> > Device tree probed devices now get
From 35607dd0607bca5322860703143c31cb04377764 Mon Sep 17 00:00:00 2001
From: Stephen Moorby
Date: Wed, 19 Jun 2013 08:22:51 +0100
Subject: [PATCH 1/1] drivers/net: param for lapbether for specific ethernet
device
The lapbether driver binds to the first ethernet device that comes up.
This causes
On 06/19/2013 03:55 PM, Viresh Kumar wrote:
On 19 June 2013 12:30, Xiaoguang Chen wrote:
Cpufreq governor's stop and start operation should be kept in sequence.
If not, there will be unexpected behavior, for example:
There are 4 CPUs and policy->cpu=CPU0, CPU1/2/3 are linked to CPU0.
The norma
On Fri, 07 Jun 2013, Oleksandr Kozaruk wrote:
> From: Graeme Gregory
>
> The TWL6025 was never released beyond sample form and was replaced by
> the PhoenixLite range of chips - TWL6032. Change the references to
> reference the TWL6032 class and name the registers to twl6032 in line with
> an ac
On Tue, Jun 18, 2013 at 11:04 PM, Kevin Strasser
wrote:
> Add gpio support for the on-board PLD found on some Kontron embedded modules.
>
> Signed-off-by: Guenter Roeck
> Signed-off-by: Kevin Strasser
> Signed-off-by: Michael Brunner
> Acked-by: Darren Hart
This is looking good.
Reviewed-by:
Please no module parameters, provide a run-time, programmatic way
to configure this aspect.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please rea
On Wed, Jun 19, 2013 at 4:22 PM, Marek Vasut wrote:
> Dear Chao Xie,
>
>> Signed-off-by: Chao Xie
>> ---
>> .../devicetree/bindings/input/pxa27x-keypad.txt| 60 +
>> drivers/input/keyboard/pxa27x_keypad.c | 232
>> +++- 2 files changed, 288 insertions(+), 4
On Tue, Jun 18, 2013 at 11:04 PM, Kevin Strasser
wrote:
> Add core MFD driver for the on-board PLD found on some Kontron embedded
> modules. The PLD device may provide functions like watchdog, GPIO, UART
> and I2C bus.
>
> The following modules are supported:
> * COMe-bIP#
> * COMe
On Wed, Jun 19, 2013 at 3:02 AM, Rohit Vaswani wrote:
> Remove stray usage of __devinit as it has been removed.
>
> Signed-off-by: Rohit Vaswani
A patch for this is already merged.
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wed, 19 Jun 2013, Chen Gang wrote:
>
> When CONFIG_LOCKDEP is not defined, spin_lock_irqsave() is not equal to
> spin_lock() + local_irq_save().
>
> In __mod_timer(), After call spin_lock_irqsave() with 'base->lock' in
> lock_timer_base(), it may use spin_lock() with the 'new_base->lock'.
>
On Wed, Jun 19, 2013 at 12:03:38PM +0800, Chen Gang wrote:
>
> Since "WARN_ON(worker->task)", we can not assume that 'worker->task'
> will be NULL before set 'current' to it.
>
> So need let 'worker' lock protected too, just like it already lock
> protected all time in main looping.
That synchro
On Wed, 19 Jun 2013, Chen Gang wrote:
>
> Since "WARN_ON(worker->task)", we can not assume that 'worker->task'
> will be NULL before set 'current' to it.
It better is NULL and all that WARN_ON does is to verify that.
> So need let 'worker' lock protected too, just like it already lock
> protec
On Tue, 18 Jun, at 10:12:22PM, Zachary Bobroff wrote:
> > Okay, I'm fine with that aspect then. Let's hope everyone plays by
> > that rule.
> This is all according to specification, so if they are not following
> these rules they should be corrected. The link to where the current
> public version
fixed checkpatch error:
added parenthesis around complex macro.
Macro with return was only used once in the code,
so I expandet it in-place.
Signed-off-by: Lorenz Haspel
Signed-off-by: Michael Banken
---
v2: expanded macro in-place
---
drivers/staging/silicom/bpctl_mod.c | 11 ---
1
On 19/06/13 09:26, Russell King wrote:
On Wed, Jun 19, 2013 at 10:44:09AM +1000, Stephen Rothwell wrote:
Hi Lorenzo,
Today's linux-next merge of the arm-mpidr tree got a conflict in
arch/arm/kernel/suspend.c between commit aa1aadc3305c ("ARM: suspend: fix
CPU suspend code for !CONFIG_MMU config
Fixes checkpatch error:
There were assignments in if conditions, so I extracted them.
Signed-off-by: Lorenz Haspel
Signed-off-by: Michael Banken
---
v2: removed some buggy extra lines and fixed white space issues
v3: fixed some more extra lines
---
drivers/staging/silicom/bpctl_mod.c | 179 +++
On Fri, Jun 07, 2013 at 02:19:09PM +0200, Paul Walmsley wrote:
> Add DFLL DVCO reset line control functions to the CAR IP block driver.
>
> The DVCO present in the DFLL IP block has a separate reset line,
> exposed via the CAR IP block. This reset line is asserted upon SoC
> reset. Unless someth
There were few noticeable formatting issues present in core cpufreq code. This
patch tries to fix them to make code look better. These are:
- Removing few extra blank lines
- Adding few blank lines
- replacing spaces with tabs
- removing unnecessary spaces
- rearranging code a bit
- Fixing multilin
On Sat, Apr 20, 2013 at 12:19:23PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Add support to perf stat to print the basic transactional execution
> statistics:
> Total cycles, Cycles in Transaction, Cycles in aborted transsactions
> using the intx and intx_checkpoint qualifiers.
> Transacti
__cpufreq_notify_transition() is used only in cpufreq.c, make it static.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 7c38842..8a9a23a 100644
--- a/drivers
On Wed, Jun 19, 2013 at 11:35:27AM +0400, Glauber Costa wrote:
> On Wed, Jun 19, 2013 at 09:13:46AM +0200, Michal Hocko wrote:
> > On Tue 18-06-13 10:26:24, Glauber Costa wrote:
> > [...]
> > > Michal, would you mind testing the following patch?
> > >
> > > diff --git a/fs/inode.c b/fs/inode.c
> >
>
> However, it still does not work, commit
> 42f132febff3b7b42c6c9dbfc151f29233be3132 does not seem to help enough
> on my hardware.
>
> Still just unbinding and rebinding with
> echo :00:03.0 > /sys/bus/pci/drivers/mei_me/unbind
> echo :00:03.0 > /sys/bus/pci/drivers/mei_me/bind
>
> tr
On Wed, Jun 19, 2013 at 04:00:32PM +0800, Wanpeng Li wrote:
> On Wed, Jun 19, 2013 at 03:33:55PM +0900, Joonsoo Kim wrote:
> >In free path, we don't check number of cpu_partial, so one slab can
> >be linked in cpu partial list even if cpu_partial is 0. To prevent this,
> >we should check number of
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
On Wed, Jun 19, 2013 at 02:55:13PM +0800, Chen Gang wrote:
>
> 'lru' may be used without initialized, so need regressing part of the
> related patch.
>
> The related patch:
> "3abf380 mm: remove lru parameter from __lru_cache_add and
> lru_cache_add_lru"
>
>
> Signed-off-by: Chen Gang
> ---
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller with the
PHY using device names. After the device names are created using
PLATFORM_DEVID_AUTO, our original method of binding by device names doesn't
work reliably
The 0xa restriction applies to BIOS really...
"m...@console-pimps.org" wrote:
>On Tue, 18 Jun, at 10:12:22PM, Zachary Bobroff wrote:
>> > Okay, I'm fine with that aspect then. Let's hope everyone plays by
>> > that rule.
>> This is all according to specification, so if they are not following
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
Whenever we are changing frequency of a cpu, we are calling PRECHANGE and
POSTCHANGE notifiers. They must be serialized. i.e. PRECHANGE or POSTCHANGE
shouldn't be called twice contiguously.
This can happen due to bugs in users of __cpufreq_driver_target() or actual
cpufreq drivers who are sending
Hi all,
I've been trying to get "xsysace" driver working properly on ARC
architecture.
And I was able to get it built and running, but it required me to do 2
changes - please refer to description below. Now I'd like to get this
driver working for me righ from upstream sources and this is where
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
On 6/19/2013 2:22 PM, Viresh Kumar wrote:
> PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
> should be called or both shouldn't be.
>
> In case we have started PRECHANGE notifier and found an error, we must call
> POSTCHANGE notifier with freqs.new = freqs.old to guar
Now that MUSB for OMAP started using devm_usb_get_phy_by_name
which does not require PHY library to already have the binding
information, removed usb_bind_phy calls that binds the MUSB controller
with the PHY from the board files.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Test
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So used the
new API devm_usb_get_phy_by_name to get the PHY reference.
Signed-off-by: Kishon Vijay Abraham I
Acked-by:
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So
added a new API to get the PHY reference by PHY label (PHY label
should be filled which creating the PHY).
Signed-off
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Tested-by: Tomi Valkeinen
---
arch/arm/mach-omap2/usb-musb.c |6 +-
i
Hi Tomas,
Am 19.06.2013 10:52, schrieb Winkler, Tomas:
>> So it is not yet fixed, unfortunately.
>
> Not sure I understand how to reproduce it. it is still falling on
> suspend/resume or just unbind/bind?
> Would you be so kind and send me the whole log.
Both is still broken. I'm actually not
FYI, Since you intend to resubmit anyway I just dropped the entire series
from patchwork.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Pleas
From: Geert Uytterhoeven
Date: Tue, 7 May 2013 11:55:55 +0200
> Signed-off-by: Geert Uytterhoeven
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/maj
On 06/19/2013 12:56 PM, Alexey Brodkin wrote:
[]
> For (2) I may expect that plain change of used accessor from "le" to
> "be" will break "xsysace" on PPC/Micropblaze.
Just recalled that discussion of the first patch continued in another
thread: https://patchwork.kernel.org/patch/2130081/
It has
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 23 +++
arch/x86/include/asm/kvm_host.h | 5 +
2 files changed, 28 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virt
On Tue, Jun 18, 2013 at 11:31:58PM -0700, Eric Dumazet wrote:
> On Wed, 2013-06-19 at 13:40 +0800, Jason Wang wrote:
> > Currently, we use kcalloc to allocate rx/tx queues for a net device which
> > could
> > be easily lead to a high order memory allocation request when initializing a
> > multique
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 25 +
1 file changed, 25 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virtual/kvm/mmu.txt
index f5c4de9..9b7cfb3 100644
1 - 100 of 859 matches
Mail list logo
