Em Mon, Dec 10, 2012 at 02:44:34PM +0100, Jiri Olsa escreveu:
> On Mon, Dec 10, 2012 at 05:29:54PM +0900, Namhyung Kim wrote:
> > When comparing entries for collapsing put the given entry first, and then
> > the iterated entry. This is not the case of hist_entry__cmp() when called
> > if given
This patch follows the discussion about reinitializing the power usage
when a C-state is added/removed.
https://lkml.org/lkml/2012/10/16/518
We realized the power usage field is never filled and when it is
filled for tegra, the power_specified flag is not set making all these
values to be
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Wednesday, December 12, 2012 6:52 PM
> > It looks like azx_runtime_suspend() is new in 3.7 and it returns
> > -EAGAIN to indicate that it actually can't be suspended (if my
> > understanding the code is
On 2012-12-12 11:11, Jan Kara wrote:
> On Wed 12-12-12 10:55:15, Shaohua Li wrote:
>> 2012/12/11 Jan Kara :
>>> Hi,
>>>
>>> I was looking into IO starvation problems where streaming sync writes (in
>>> my case from kjournald but DIO would look the same) starve reads. This is
>>> because reads
On 12/11/2012 06:37 PM, Liu Bo wrote:
> On Tue, Dec 11, 2012 at 09:33:15AM -0700, Jim Schutt wrote:
>> On 12/09/2012 07:04 AM, Liu Bo wrote:
>>> On Wed, Dec 05, 2012 at 09:07:05AM -0700, Jim Schutt wrote:
>>> Hi Jim,
>>>
>>> Could you please apply the following patch to test if it works?
>>
>> Hi,
On Friday 30 November 2012 19:07:53 Vinod Koul wrote:
> On Fri, 2012-11-30 at 11:59 +0100, Bartlomiej Zolnierkiewicz wrote:
> > > Acked-by: Jassi Brar
> >
> > Vinod/Dan could you please pick this patch for 3.8? Thanks!
> I will check and queue it up today
ping? [ I can't find the patch in
On Wed, Dec 12, 2012 at 09:56:16AM +0100, Benedikt Spranger wrote:
> Am Wed, 12 Dec 2012 09:50:54 +0100
> schrieb "Hans J. Koch" :
>
> > On Tue, Dec 11, 2012 at 08:46:48PM -0800, Greg KH wrote:
> > > Yes, but what does that have to do with this in-kernel, internal api?
> >
> > Ah, OK. You're
On 12/12/2012 10:34 PM, Yijing Wang wrote:
> 于 2012-12-12 2:30, Rafael J. Wysocki 写道:
>> Hi Gerry,
>>
>> On Tuesday, December 11, 2012 11:09:06 PM Jiang Liu wrote:
>>> Hi Rafael,
>>> I have worked out a patch set to clean up ACPI/PCI related
>>> notifications,
>>> please refer to
>>>
On Wed, Dec 12, 2012 at 3:37 PM, Namjae Jeon wrote:
> + /* dot and dotdot dentries should have zero-value hash code */
> + if (!memcmp(name, ".", 1) || !memcmp(name, "..", 2))
> + return 0;
That looks suspicious. If memcmp(name, "..", 2) == 0 then always
memcmp(name,
Hi Miklos,
11/16/2012 09:04 PM, Maxim Patlasov пишет:
Hi,
This is the second iteration of Pavel Emelyanov's patch-set implementing
write-back policy for FUSE page cache. Initial patch-set description was
the following:
One of the problems with the existing FUSE implementation is that it uses
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
v4l_for_linus
On patch series:
- Missing MAINTAINERS entries were added for several drivers;
- Adds V4L2 support for DMABUF handling, allowing zero-copy buffer
sharing
On Tue, Dec 11, 2012 at 08:40:40AM -0800, Arjan van de Ven wrote:
> >Let me try to understand what this means: so "performance" above with
> >8 threads means that those threads are spread out across more than one
> >socket, no?
> >
> >If so, this would mean that you have a smaller amount of tasks
From: Namjae Jeon
Test Case:
[NFS Client]
ls -lR .
[NFS Server]
while [ 1 ]
do
echo 3 > /proc/sys/vm/drop_caches
done
Error on NFS Client: "No such file or directory"
When cache is dropped at the server, it results in lookup failure at the
NFS client due to non-connection with the parent. The
Wen Congyang wrote:
> At 12/08/2012 06:19 AM, Rafael J. Wysocki Wrote:
>> On Tuesday, December 04, 2012 01:39:54 AM Liu, Jinsong wrote:
>>> Resend it, add Rafael and linux-a...@vger.kernel.org
>>
>> I wonder what memory hotplug people think about that.
>>
>> Thanks,
>> Rafael
>>
>>
>>>
On Wed, 2012-12-12 at 17:59 +1100, Alexey Kardashevskiy wrote:
> On 08/12/12 04:01, Alex Williamson wrote:
> >> + case VFIO_IOMMU_MAP_DMA: {
> >> + vfio_iommu_spapr_tce_dma_map param;
> >> + struct iommu_table *tbl = container->tbl;
> >> + enum dma_data_direction
于 2012-12-12 2:30, Rafael J. Wysocki 写道:
> Hi Gerry,
>
> On Tuesday, December 11, 2012 11:09:06 PM Jiang Liu wrote:
>> Hi Rafael,
>> I have worked out a patch set to clean up ACPI/PCI related
>> notifications,
>> please refer to
>> http://www.spinics.net/lists/linux-pci/msg17822.html
>>
On Wed, 2012-12-12 at 17:14 +1100, Alexey Kardashevskiy wrote:
> On 08/12/12 04:38, Alex Williamson wrote:
> >> +static int __init tce_iommu_init(void)
> >> +{
> >> + struct pci_dev *pdev = NULL;
> >> + struct iommu_table *tbl;
> >> + struct iommu_group *grp;
> >> +
> >> + /* Allocate and
2012/12/7 JoonSoo Kim :
> 2012/11/28 Joonsoo Kim :
>> In current implementation, we used ARM-specific flag, that is,
>> VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
>> The purpose of static mapped area is to re-use static mapped area when
>> entire physical address
On Wed, Dec 12, 2012 at 8:56 AM, Kasatkin, Dmitry
wrote:
> I have done few tests.
> Ratio between lookups is different, but I do not really remember what
> exactly it was.
> Probably I did measurement with directory integrity protection...
>
> First test is done using upstream IMA.
>
>
From: Julia Lawall
The function at91_dt_node_to_map is ultimately called by the function
pinctrl_get, which is an exported function. Since it is possible that this
function is not called from within a probe function, for safety, the kfree
is converted to a devm_kfree, to both free the data and
On 12 December 2012 14:55, Alex Shi wrote:
>
>
> well... it's not always beneficial to group or to spread out
> it depends on cache behavior mostly which is best
Let me try to understand what this means: so "performance" above with
8 threads means that those
On Mon, Dec 10, 2012 at 10:32:39AM -0700, Alex Williamson wrote:
> v2: Update 02/10 to not check userspace_addr when slot is removed.
> Yoshikawa-san withdrew objection to increase slot_bitmap prior
> to his series to remove slot_bitmap.
>
> This series does away with any kind of
Hello, Atsushi.
2012/12/12 Atsushi Kumagai :
> Hello,
>
> On Tue, 11 Dec 2012 17:17:05 -0500 (EST)
> Dave Anderson wrote:
>
>>
>>
>> - Original Message -
>> > On Mon, Dec 10, 2012 at 11:40:47PM +0900, JoonSoo Kim wrote:
>> >
>> > [..]
>> > > > So without knowing details of both the data
Two separate de-init functions are merged into one common function.
And it is used in err_post_init of lp55xx_init_device().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c| 16
drivers/leds/leds-lp5523.c| 16
Use lp55xx_unregister_leds() rather than duplicate code.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp55xx-common.c |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/leds/leds-lp55xx-common.c
b/drivers/leds/leds-lp55xx-common.c
index
This patch provides additional device attributes which enable
loading the firmware. ('select_engine' and 'run_engine')
To run a LED pattern, two parts of driver should be enabled.
Common features : lp55xx-common
===
Firmware interface for loading LED patterns
LED current is configurable via the sysfs.
Max current is a read-only attribute.
These attributes code can be shared in lp55xx common driver.
show_max_current() => lp55xx_show_max_current()
show_current() => lp55xx_show_current()
store_current() => lp55xx_store_current()
Current
The LP55xx common driver provides a new header, leds-lp55xx.h.
This driver enables removing duplicate code for both drivers and
making coherent driver structure.
LP5521 and LP5523/55231 platform data were merged into one common file.
Therefore, the LP5521/5523 platform code need to be fixed.
Now LP5521 and LP5523 drivers are based on new lp55xx structure.
So the author and copyrights are updated.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c |3 +++
drivers/leds/leds-lp5523.c |3 +++
2 files changed, 6 insertions(+)
diff --git
To support device specific attributes, new common driver function is added.
Eventually those are created on registering the sysfs with common dev attrs.
Furthermore, this patch makes adding device attributes simple in each driver.
Signed-off-by: Milo(Woogyom) Kim
---
Remove unused headers and sort them alphabetically
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 19 ++-
drivers/leds/leds-lp5523.c | 19 ++-
2 files changed, 12 insertions(+), 26 deletions(-)
diff --git a/drivers/leds/leds-lp5521.c
On Wed, 2012-12-12 at 19:44 +0800, Hillf Danton wrote:
> On Wed, Dec 12, 2012 at 10:46 AM, Steven Rostedt wrote:
> > On Tue, 2012-12-11 at 20:54 -0500, Steven Rostedt wrote:
> >
> >> I'm actually thinking that that test should always fail. The
> >> cpupri_find() does a scan of all priorities up
LP5521 and LP5523 have a selftest function which is run via the sysfs.
Use lp55xx driver data and r/w functions rather than lp5521/5523 private data
and functions.
Additionally, if-statements are changed for code simplicity.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c |
During the cleanup, Dan Carpenter's patch was removed.
This patch recovers his patch based on the latest lp5521 driver.
[PATCH] leds: leds-lp5521: return an error code on error in probe()
If "buf" wasn't equal to LP5521_REG_R_CURR_DEFAULT the probe fails but
we still return zero. I've
Update changed platform data information.
Add leds-lp55xx.txt which includes the firmware interface description.
Signed-off-by: Milo(Woogyom) Kim
---
Documentation/leds/00-INDEX|2 +
Documentation/leds/leds-lp5521.txt | 63 +++-
Documentation/leds/leds-lp5523.txt
Remove unused definitions and change hex values to capital letters
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 26 +++-
drivers/leds/leds-lp5523.c | 56 +++-
2 files changed, 12 insertions(+), 70 deletions(-)
LP55XX common device attributes, 'led_current' and 'max_current' are created
while loading the driver.
Those are LED device attributes which are removed automatically on releasing
led class devices - led_classdev_unregister().
Therefore, this duplicate code should be removed.
Signed-off-by:
lp55xx_unregister_sysfs() is used for removing lp55xx device attributes.
Chip specific and engine attributes are removed on unloading the driver.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp55xx-common.c | 12
drivers/leds/leds-lp55xx-common.h |1 +
2 files
Replaced lp5521_unregister_sysfs() and lp5523_unregister_sysfs()
with lp55xx_unregister_sysfs().
On unloading the driver, running LED pattern should be stopped.
Use explicit driver functions rather than old functions and direct access code.
Signed-off-by: Milo(Woogyom) Kim
---
Old data structures and I2C functions are not used any more.
Each driver uses the lp55xx common data and functions.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 110
drivers/leds/leds-lp5523.c | 35 --
2 files
LP55xx common driver provides generic firmware interface
for running a LED pattern.
LP5521 and LP5523 have many device attributes for running patterns.
This patch cleans up those complex code.
Removed device attributes for LP5521
engine1_mode
engine2_mode
engine3_mode
engine1_load
Use lp55xx_register_sysfs() rather than lp5521_register_sysfs()
and lp5523_register_sysfs().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 17 +++--
drivers/leds/leds-lp5523.c | 23 +++
2 files changed, 14 insertions(+), 26 deletions(-)
lp5521_set_brightness() and lp5523_set_brightness() are replaced with
common lp55xx_set_brightness().
This common function is invoked when the brightness of each LED channel
is updated.
LP5521 and LP5523 have different register address for the brightness control,
so this work is done by chip
To unregister led class devices and sysfs attributes,
LP5521 and LP5523 have each driver function.
This patch makes both drivers simple using common driver function,
lp55xx_unregister_leds().
And some unused variables are removed.
Signed-off-by: Milo(Woogyom) Kim
---
LP55xx family chips have internal program memory which run various patterns.
Using this memory, LEDs continue on blinking/dimming without continuous I2C
commands. That means the I2C HOST can be entered into sleep once the memory
is updated.
An application can get hex data from a file and
lp5521_init_led() and lp5523_init_led() are replaced with one common function,
lp55xx_init_led().
Max channels is configurable, so it's used in lp55xx_init_led().
'LP5523_LEDS' are changed to 'LP5523_MAX_LEDS'.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c| 50
LED class devices are registered in lp5521_register_leds() and
lp5523_register_leds().
Two separate functions are merged into consolidated lp55xx function,
lp55xx_register_leds().
Error handling fix:
When LED registration failure occurs, device should be de-initialized
rather than
LP5521 and LP5523 data structures have common features.
Use common lp55xx data structures rather than chip specific data.
lp55xx_chip : Common data between lp5521_chip and lp5523_chip
lp55xx_led : Common LED structure bettwen lp5521_led and lp5523_led
lp55xx_platform_data
LP5521 and LP5523 driver have separate device init function, but
they can be merged into one common init function.
Driver specific functions are replaced with consolidated functions.
lp5521/lp5523_init_device() => lp55xx_init_device()
lp5521/lp5523_reset_device() =>
This patch supports basic common driver code for LP5521, LP5523/55231 devices.
( Driver Structure Data )
lp55xx_led and lp55xx_chip
In lp55xx common driver, two different data structure is used.
o lp55xx_led
control multi output LED channels such as led current, channel index.
o
Change name of chip data structure and platform data.
This patch is a preceding step for cleaning up lp5521/5523 probe and remove.
These data will be replaced with new lp55xx common data structures
in next patch.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 36
Use explicit each driver function rather than raw command.
These function will be merged into the lp55xx common driver.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 10 +-
drivers/leds/leds-lp5523.c | 10 +-
2 files changed, 18 insertions(+), 2
Chip specific function is configured during the device initialization.
So _configure() is moved to each device init function.
If chip configuration gets failed, the device is de-initialized in
each _init_device(), not probe().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c
Device de-initialization code is moved to _deinit_device() at each driver.
This patch is a preceding step for lp55xx common driver architecture.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 20
drivers/leds/leds-lp5523.c | 20
To make LED unregistration code simple, new function, _unregister_leds()
is added at each driver.
This patch is a preceding step for lp55xx common driver architecture.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 23 +--
drivers/leds/leds-lp5523.c |
To make LED initialization code simple, new function, _register_leds()
is added at each driver.
This patch is a preceding step for lp55xx common driver architecture.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 69 +
To make _probe() simple, device initialization code is moved to
_init_device() at each driver.
This patch is a preceding step for lp55xx common driver architecture.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 102
LP5521, LP5523 and L55231 have common features as below.
Register access via the I2C.
Device initialization/de-initialization.
Create LED class devices for multiple output channels.
Device attributes for user-space interface.
Therefore, this patch-set removes duplicate code for LP5521/5523
On Wed, Dec 12, 2012 at 1:02 AM, Eric Paris wrote:
> Linus made it clear he likes per-inode. Do a test with per-inode
> S_NOIMA. See how that compares to your 100,000 vs 10,000 lookups.
> Then we can discuss with facts if per sb is worth it or not. We still
> don't actually know if 100,000
well... it's not always beneficial to group or to spread out
it depends on cache behavior mostly which is best
>>>
>>>
>>> Let me try to understand what this means: so "performance" above with
>>> 8 threads means that those threads are spread out across more than one
>>>
Bool initializations should use true and false. Bool tests don't need
comparisons. Based on contributions from Joe Perches, Rusty Russell
and Bruce W Allan.
The semantic patch that makes this output is available
in scripts/coccinelle/misc/boolinit.cocci.
More information about semantic
On Tue, Dec 11, 2012 at 10:57:03PM -0800, H. Peter Anvin wrote:
> @@ -372,46 +394,21 @@ ENTRY(name)
> i = i + 1 ; \
> .endr
>
> - .data
> - /*
> - * This default setting generates an ident mapping at address 0x10
> - * and a
The ARM platforms take advantage of packing small tasks on few cores.
This is true even when the cores of a cluster can't be power gated
independantly. So we clear SD_SHARE_POWERDOMAIN at MC and CPU level.
Signed-off-by: Vincent Guittot
---
arch/arm/kernel/topology.c |9 +
1 file
If a CPU accesses the runnable_avg_sum and runnable_avg_period fields of its
buddy CPU while the latter updates it, it can get the new version of a field
and the old version of the other one. This can generate erroneous decisions.
We don't want to use a lock mechanism for ensuring the coherency
This new flag SD_SHARE_POWERDOMAIN is used to reflect whether groups of CPU in
a sched_domain level can or not reach a different power state. If clusters can
be power gated independently, as an example, the flag should be cleared at CPU
level. This information is used to decide if it's worth
Look for an idle CPU close to the pack buddy CPU whenever possible.
The goal is to prevent the wake up of a CPU which doesn't share the power
domain of the pack buddy CPU.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 18 ++
1 file changed, 18 insertions(+)
diff
Hi,
This patchset takes advantage of the new per-task load tracking that is
available in the kernel for packing the small tasks in as few as possible
CPU/Cluster/Core. The main goal of packing small tasks is to reduce the power
consumption by minimizing the number of power domain that are
This reverts commit f4e26b120b9de84cb627bc7361ba43cfdc51341f
Signed-off-by: Vincent Guittot
---
include/linux/sched.h |8 +---
kernel/sched/core.c |7 +--
kernel/sched/fair.c |3 +--
kernel/sched/sched.h |9 +
4 files changed, 4 insertions(+), 23
On Tuesday, December 11, 2012 04:45:31 PM H. Peter Anvin wrote:
> Looks good to me. Alan/Rafael/Dmitry, OK for me to commit this?
No objections from me.
Thanks,
Rafael
> On 12/11/2012 01:18 PM, Ondrej Zary wrote:
> > Some MSI laptop BIOSes are broken - INT 15h code uses port 92h to enable A20
At Wed, 12 Dec 2012 13:13:45 +0100,
Borislav Petkov wrote:
>
> On Wed, Dec 12, 2012 at 11:58:41AM +0100, Takashi Iwai wrote:
> > Borislav, could you test the patch below?
>
> [ … ]
>
> > From: Takashi Iwai
> > Subject: [PATCH] ALSA: hda - Move runtime PM check to runtime_idle callback
> >
> >
On Wed 12-12-12 12:23:29, Michal Hocko wrote:
> On Wed 12-12-12 18:44:13, Xishi Qiu wrote:
[...]
> > Hi Michal,
> >
> > __initcall functions will be called in
> > start_kernel()
> > rest_init() // -> slab is already
> > kernel_init()
> > kernel_init_freeable()
On 12/12/2012 12:45 PM, Grant Likely wrote:
> I will take a look at it this week
Thanks
> but I cannot pick it up for v3.8 unless it is a regression bug fix from
> v3.6. It will have to wait for v3.9 and it can be merged into linux-next
> after the v3.8 merge window closes.
3.9 is fine. the
Ping ?
2012/11/30, Stefan Hajnoczi :
> Changes are fine.
>
> In the future, please split changes into individual patches. For example:
> Patch 1 - Rename 'rv' to 'ret'
> Patch 2 - Replace decprecated simple_strtoul() with kstrtoint() in
> pcm_set_impulse_period()
> Patch 3 - Realign comment in
Hi Alex,
I posted other pair of patches. While debugging and testing my stuff I
implemented some rough hack to support IOMMU mappings without passing those
hypercalls to the QEMU, this is why I moved pieces of code around - want to
support both QEMU-VFIO and kernel optimized H_PUT_TCE
Add a simple serial connection driver called
VIRTIO_ID_RPROC_SERIAL (11) for communicating with a
remote processor in an asymmetric multi-processing
configuration.
This implementation reuses the existing virtio_console
implementation, and adds support for DMA allocation
of data buffers and
This patch-set introduces a new virtio type "rproc_serial" for communicating
with remote processors over shared memory. The driver depends on the
the remoteproc framework. As preparation for introducing "rproc_serial"
I've done a refactoring of the transmit buffer handling.
NOTE: These two
Refactoring the splice functionality by unifying the approach for
sending scatter-lists and regular buffers. This simplifies
buffer handling and reduces code size. Splice will now allocate
a port_buffer and send_buf() and free_buf() can always be used
for any buffer.
Signed-off-by: Sjur
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/kvm-3.8-1
to receive the KVM updates for the 3.8 merge window, including
considerable KVM/PPC work, x86 kvmclock vsyscall support, IA32_TSC_ADJUST
MSR emulation, amongst others.
Alex Williamson (2):
KVM:
VFIO implements platform independent stuff such as
a PCI driver, BAR access (via read/write on a file descriptor
or direct mapping when possible) and IRQ signaling.
The platform dependent part includes IOMMU initialization
and handling. This patch implements an IOMMU driver for VFIO
which does
This patch initializes IOMMU groups based on the IOMMU
configuration discovered during the PCI scan on POWERNV
(POWER non virtualized) platform. The IOMMU groups are
to be used later by VFIO driver (PCI pass through).
It also implements an API for mapping/unmapping pages for
guest PCI drivers and
Hi Ulf,
Sorry for the late response.
See my reply below.
Thanks,
Maya
On Thu, December 6, 2012 2:18 am, Ulf Hansson wrote:
> Hi Maya,
>
> On 4 December 2012 22:17, wrote:
>> Hi Ulf,
>>
>> Let me try to better explain:
>> The idea behind the periodic BKOPS is to check the card's need for BKOPS
> Amit Shah [mailto:amit.s...@redhat.com] writes:
> On (Wed) 12 Dec 2012 [10:31:04], Rusty Russell wrote:
> > Amit Shah writes:
> > > On (Tue) 11 Dec 2012 [09:39:41], Rusty Russell wrote:
> > >> Amit Shah writes:
> > >> > On (Fri) 16 Nov 2012 [11:22:09], Rusty Russell wrote:
> > >> >> Amit Shah
3 is an invalid value for the CAN1_IPP_IND_CANRX_SELECT_INPUT
register. Set it to 2, which correctly selects the GPIO_8 pad.
Signed-off-by: Philipp Zabel
---
drivers/pinctrl/pinctrl-imx53.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-imx53.c
On 10:13 Tue 11 Dec , Greg Kroah-Hartman wrote:
> On Tue, Dec 11, 2012 at 02:40:46PM +0100, Linus Walleij wrote:
> > diff --git a/include/linux/device.h b/include/linux/device.h
> > index 86ef6ab..dc399ab 100644
> > --- a/include/linux/device.h
> > +++ b/include/linux/device.h
> > @@ -21,6
On Wed, Dec 12, 2012 at 11:58:41AM +0100, Takashi Iwai wrote:
> Borislav, could you test the patch below?
[ … ]
> From: Takashi Iwai
> Subject: [PATCH] ALSA: hda - Move runtime PM check to runtime_idle callback
>
> The runtime_idle callback is the right place to check the suspend
> capability,
On (Wed) 12 Dec 2012 [10:31:04], Rusty Russell wrote:
> Amit Shah writes:
>
> > On (Tue) 11 Dec 2012 [09:39:41], Rusty Russell wrote:
> >> Amit Shah writes:
> >>
> >> > On (Fri) 16 Nov 2012 [11:22:09], Rusty Russell wrote:
> >> >> Amit Shah writes:
> >> >> > From: Sjur Brændeland
> >> >> >
>
On Tue, 2012-12-11 at 23:39 +, Axel Lin wrote:
> I was thinking below patch to fix the issue:
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index cd1b201..891bc96 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -1885,9 +1885,14 @@ int
On 11:58 Tue 11 Dec , Julia Lawall wrote:
> From: Julia Lawall
>
> The function at91_dt_node_to_map is ultimately called by the function
> pinctrl_get, which is an exported function. Since it is possible that this
> function is not called from within a probe function, for safety, the kfree
And after a second look it's clear what's going on:
[...]
[5.575744] cpu cpu0: cpufreq-omap: 300 MHz, -1 mV --> 800 MHz, 1325 mV
[5.582946] voltdm_scale: No voltage scale API registered for vdd_mpu_iva
[5.590332] cpu cpu0: omap_target: unable to scale voltage up.
[1]
[5.596649]
On Wed, Dec 12, 2012 at 11:12 AM, Peter Ujfalusi wrote:
> Hi Grant,
>
> On 12/07/2012 09:09 AM, Linus Walleij wrote:
>> On Thu, Dec 6, 2012 at 11:52 AM, Peter Ujfalusi
>> wrote:
>>
>>> As Grant commneted on the first version:
>>> https://lkml.org/lkml/2012/12/5/53
>>>
>>> Introduce bitfields to
Signed-off-by: Paolo Pisati
---
drivers/regulator/core.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index e872c8b..c347fd0 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@
On Wed, Dec 12, 2012 at 10:46 AM, Steven Rostedt wrote:
> On Tue, 2012-12-11 at 20:54 -0500, Steven Rostedt wrote:
>
>> I'm actually thinking that that test should always fail. The
>> cpupri_find() does a scan of all priorities up to but not including the
>> current task's priority. If
On Wed, Dec 12, 2012 at 11:11 AM, Benoit Cousson wrote:
> Hi Javier,
>
> On 12/12/2012 09:25 AM, Javier Martinez Canillas wrote:
>> On Mon, Dec 3, 2012 at 1:41 PM, Javier Martinez Canillas
>> wrote:
>>> IGEP technology devices are TI OMAP3 SoC based industrial embedded
>>> and computer-on-module
From: Ville Syrjälä
Implement __get_user_8() for x86-32. It will return the
64bit result in edx:eax register pair, and ecx is used
to pass in the address and return the error value.
For consistency, change the register assignment for all
other __get_user_x() variants, so that address is passed
On Wed, Dec 12, 2012 at 07:24:30PM +1100, NeilBrown wrote:
>
>
> This patch is based on an earlier patch by Grant Erickson
> which provided pwm devices using the 'legacy' interface.
>
> This driver instead uses the new framework interface.
I'd prefer some kind of description about the driver
On Wed 12-12-12 18:44:13, Xishi Qiu wrote:
> On 2012/12/12 18:19, Michal Hocko wrote:
>
> > On Wed 12-12-12 16:25:59, Jianguo Wu wrote:
> >> Build kernel with CONFIG_HUGETLBFS=y,CONFIG_HUGETLB_PAGE=y
> >> and CONFIG_CGROUP_HUGETLB=y, then specify hugepagesz=xx boot option,
> >> system will boot
Initial support for TI's AIC platform and TLV320AIC3262 CODEC device.
The AIC platform provides common interface to series of low power audio CODECS.
This MFD core driver instantiates subdevices that help in supporting range of
features
provided by AIC family of devices.
Signed-off-by: Mehar
On 12/10/2012 12:13 PM, Philip, Avinash wrote:
> On Fri, Dec 07, 2012 at 16:07:23, Nori, Sekhar wrote:
>> On 11/29/2012 5:16 PM, Philip, Avinash wrote:
[...]
>>> +struct device *elm_request(enum bch_ecc bch_type)
>>> +{
>>> + struct elm_info *info;
>>> +
>>> + list_for_each_entry(info,
This driver makes the time from HID sensors (hubs) which are offering
such available like any other RTC does.
Currently the time can only be read. Setting the time must be done
through sending a report, which currently isn't supported by
hid-sensor-hub. (I've planned to submit patches.)
It is
Hi Grant,
On 12/07/2012 09:09 AM, Linus Walleij wrote:
> On Thu, Dec 6, 2012 at 11:52 AM, Peter Ujfalusi wrote:
>
>> As Grant commneted on the first version:
>> https://lkml.org/lkml/2012/12/5/53
>>
>> Introduce bitfields to cache the directionand output status of the pins so we
>> can report
401 - 500 of 1170 matches
Mail list logo
