This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Jesper Nilsson
Cc: Mikael Starvik
Cc: linux-cris-ker...@axis.com
Signe
On Mon, Aug 12, 2013 at 07:05:53PM +0100, Felipe Balbi wrote:
> On Fri, Aug 09, 2013 at 01:42:15PM -0500, Kumar Gala wrote:
> >
> > On Aug 9, 2013, at 11:28 AM, Mark Rutland wrote:
> >
> > > On Fri, Aug 09, 2013 at 04:40:32PM +0100, Kumar Gala wrote:
> > >> The binding spec wasn't clear that the
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Kukjin Kim
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/exynos-cpu
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Santosh Shilimkar
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/oma
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: David S. Miller
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/p4-cl
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/pmac32-cpufreq.c | 12 +++-
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Linus Walleij
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/dbx500-
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Tony Luck
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/ia64-acpi-c
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Hans-Christian Egtvedt
Signed-off-by: Viresh Kumar
---
drivers/cpufre
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Shawn Guo
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq-cpu
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Cc: Steven Miao
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/blackfin-
Currently prototype of cpufreq_drivers target routines is:
int target(struct cpufreq_policy *policy, unsigned int target_freq,
unsigned int relation);
And most of the drivers call cpufreq_frequency_table_target() to get a valid
index of their frequency table which is closest to th
Sebastian,
On Tue, Aug 13, 2013 at 8:17 AM, Sebastian Andrzej Siewior
wrote:
> On 08/13/2013 03:03 PM, Bin Liu wrote:
>> Sebastian,
>
> Hi Bin,
>
> +if (musb->port_mode == MUSB_PORT_MODE_HOST) {
> +val = USBMODE_IDDIG_A;
> +val |= USBMODE_ID_MUX_REG;
>> I am g
CONFIG_CPU_FREQ_TABLE will be always enabled when cpufreq framework is used, as
cpufreq core depends on it. So, we don't need this CONFIG option anymore as it
is not configurable. Remove CONFIG_CPU_FREQ_TABLE and update its users.
Signed-off-by: Viresh Kumar
---
arch/arm/mach-davinci/Kconfig |
This patch converts existing .target() to newly defined light weight
.target_index() routine for this driver.
CPUFreq core will call cpufreq_frequency_table_target() before calling this
routine and will pass index to it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/acpi-cpufreq.c | 21 ++
On 13/08/2013 09:23, Pali Rohár wrote:
On Tuesday 13 August 2013 09:01:19 Martin Peres wrote:
On 13/08/2013 05:56, Pali Rohár wrote:
Hello,
after commit ad40d73ef533ab0ad16b4a1ab2f7870c1f8ab954 temperature
information from lm sensors is not available on my Nvidia 6600GT graphics
card. There is
Currently prototype of cpufreq_drivers target routines is:
int target(struct cpufreq_policy *policy, unsigned int target_freq,
unsigned int relation);
And most of the drivers call cpufreq_frequency_table_target() to get a valid
index of their frequency table which is closest to the target
This patch exposes sa11x0's frequency table to cpufreq core. It always existed
but not as an array frequencies and not in the format cpufreq core wants it to.
Also it was present in the unit of 100kHz earlier which is made consistent with
cpufreq core now, i.e. kHz.
Signed-off-by: Viresh Kumar
--
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar
---
arch/arm/mach-sa1100/g
Many fields of struct policy are filled by cpufreq core when we call
cpufreq_table_validate_and_show() and so cpufreq driver doesn't need to set them
anymore.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/sa1100-cpufreq.c | 4 +---
drivers/cpufreq/sa1110-cpufreq.c | 4 +---
2 files changed, 2
Hi Rafael/Russell,
These patches would be part of this patchset finally, sending it separately as I
didn't wanted to send other patches in that series..
https://lkml.org/lkml/2013/8/10/48
(Above series was rebased over https://lkml.org/lkml/2013/8/8/263 and hence this
patchset too)..
These firs
On Tuesday 13 August 2013 05:56 AM, Sricharan R wrote:
> Hi Tony,
>
> On Tuesday 13 August 2013 01:40 PM, Tony Lindgren wrote:
>> * Santosh Shilimkar [130724 12:06]:
>>> On Wednesday 24 July 2013 02:51 PM, Nishanth Menon wrote:
On 07/24/2013 01:43 PM, Sricharan R wrote:
> On Wednesday 24
On Tuesday 13 August 2013 04:10 AM, Tony Lindgren wrote:
> * Santosh Shilimkar [130724 12:06]:
>> On Wednesday 24 July 2013 02:51 PM, Nishanth Menon wrote:
>>> On 07/24/2013 01:43 PM, Sricharan R wrote:
On Wednesday 24 July 2013 10:17 PM, Nishanth Menon wrote:
> On 07/24/2013 11:38 AM, Sa
On 08/13/2013 08:56 AM, Maxim Patlasov wrote:
> Hi,
>
> 08/13/2013 04:05 PM, Brian Foster пишет:
>> ...
>> @@ -2478,8 +2516,11 @@ static long fuse_file_fallocate(struct file
>> *file, int mode, loff_t offset,
>> if (lock_inode) {
>> mutex_lock(&inode->i_mutex);
>> -if (mo
Hi lars,
On 07/08/2013 17:11, Lars Poeschel wrote:
On Wednesday 07 August 2013 at 16:53:09, Mark Rutland wrote:
On Wed, Aug 07, 2013 at 12:06:32PM +0100, Lars Poeschel wrote:
From: Lars Poeschel
Following commit ff5c9059 and therefore other omap platforms using
the gpio-omap driver correct t
On Tuesday 13 August 2013 09:01:19 Martin Peres wrote:
> On 13/08/2013 05:56, Pali Rohár wrote:
> > Hello,
> >
> > after commit ad40d73ef533ab0ad16b4a1ab2f7870c1f8ab954 temperature
> > information from lm sensors is not available on my Nvidia 6600GT graphics
> > card. There is no nouveau hwmon ent
On Tue, Aug 13, 2013 at 01:28:49PM +0200, Sebastian Hesselbarth wrote:
> On 08/12/13 22:04, Jason Cooper wrote:
> >On Mon, Aug 12, 2013 at 08:46:53PM +0200, Sebastian Hesselbarth wrote:
> >>This adds a node for the pcie controllers found on Dove SoCs to the
> >>SoC DT include.
> >>
> >>Signed-off-b
Hi Kishon,
On 12/08/2013 11:37, Kishon Vijay Abraham I wrote:
SMPS10 has two outputs OUT1 and OUT2. Hence SMPS10 is modeled as
two regulators. The dt node is split to reflect it.
Mmm, I'm curious. How is it supposed to work?
Do you have dedicated control on each output?
Otherwise, it should
On Fri, Aug 09, 2013 at 04:26:17PM -0700, Roy Franz wrote:
> Signed-off-by: Roy Franz
> ---
> arch/arm/Kconfig | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 43594d5..8607d03 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kco
On Tue, Aug 13, 2013 at 8:53 AM, David Vrabel wrote:
> On 12/08/13 21:26, Dario Faggioli wrote:
>>
>> Mmm... Is that the case? I tried to apply it there and I have one failed
>> hunk (#12). Anyway, could you please rebase it on the tip of some
>> relevant git tree?
>>
>> Linus' tree would be fine,
On 08/13/2013 03:03 PM, Bin Liu wrote:
> Sebastian,
Hi Bin,
+if (musb->port_mode == MUSB_PORT_MODE_HOST) {
+val = USBMODE_IDDIG_A;
+val |= USBMODE_ID_MUX_REG;
>>>
> I am going to so some tests today for this. I don't object to use the
> mode register, but am won
Hi Linus,
On Wednesday 07 August 2013 12:24 AM, Stephen Warren wrote:
On 08/06/2013 07:12 AM, Laxman Dewangan wrote:
TI Palmas series Power Management IC have multiple pins which can be
configured for different functionality. This pins can be configured
for different function. Also their proper
On Sunday, August 11, 2013 06:51:53 PM Julia Lawall wrote:
> From: Julia Lawall
>
> Replace ARRAY_AND_SIZE(e) in function argument position to avoid hiding the
> arity of the called function.
>
> The semantic match that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @
On Tue, Aug 13, 2013 at 12:17:18PM +0100, Stefano Stabellini wrote:
> On Fri, 9 Aug 2013, Konrad Rzeszutek Wilk wrote:
> > On Sun, Aug 04, 2013 at 03:39:41PM +0100, Stefano Stabellini wrote:
> > > GNTTABOP_unmap_grant_ref unmaps a grant and replaces it with a 0
> > > mapping instead of reinstating
Initially I improperly set a boundary for maximum number of input
packets to process on NAPI poll ("work") so it might be more than
expected amount ("weight").
This was really harmless but seeing WARN_ON_ONCE on every device boot is
not nice. So trivial fix ("<" instead of "<=") is here.
Signed-o
Sebastian,
On Tue, Aug 13, 2013 at 2:14 AM, Sebastian Andrzej Siewior
wrote:
> On 08/09/2013 10:30 PM, Sergei Shtylyov wrote:
>> Hello.
>
> Hi Sergei,
>
>>> +if (musb->port_mode == MUSB_PORT_MODE_HOST) {
>>> +val = USBMODE_IDDIG_A;
>>> +val |= USBMODE_ID_MUX_REG;
>>
>>Why
Hi,
08/13/2013 04:05 PM, Brian Foster пишет:
...
@@ -2478,8 +2516,11 @@ static long fuse_file_fallocate(struct file *file, int
mode, loff_t offset,
if (lock_inode) {
mutex_lock(&inode->i_mutex);
- if (mode & FALLOC_FL_PUNCH_HOLE)
- fuse
On Monday, August 12, 2013 02:27:47 PM Sudeep KarkadaNagesha wrote:
> The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:
>
> Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)
>
> are available in the git repository at:
>
> git://linux-arm.org/linux-skn.git cpu_of_node
>
>
On Mon, Aug 12, 2013 at 4:26 PM, Dario Faggioli
wrote:
> Hi Yechen.
>
> Thanks for doing and sharing this part of the thing too.
>
> See what I already told you on xen-devel about Cc-ing the relevant
> people. For Linux as well, you can check at the MAINTAINERS file. This
> exact thing (i.e., who
Hi!
> Since it is a PCIe card, it does not have the ability to host hardware
> devices for networking, storage and console. We provide these devices
> on X100 coprocessors thus enabling a self-bootable equivalent environment
> for applications. A key benefit of our solution is that it leverages
>
On Tue, Aug 13, 2013 at 04:51:33PM +0530, Naveen N. Rao wrote:
> You're right - my trace point makes all the data provided by apei
> as-is to userspace. However, ghes_edac seems to squash some of this
> data into a string when reporting through mc_event.
Right, for systems which don't need EDAC to
Em Tue, 13 Aug 2013 17:11:18 +0530
"Naveen N. Rao" escreveu:
> On 08/12/2013 08:14 PM, Mauro Carvalho Chehab wrote:
> >> But, this only seems to expose the APEI data as a string
> >> and doesn't look to really make all the fields available to user-space
> >> in a raw manner. Not sure how well thi
On Tue, Aug 13, 2013 at 09:21:54AM -0300, Mauro Carvalho Chehab wrote:
> > > More specifically, what are those gdata_fru_id and gdata_fru_text
> > > things?
> >
> > My understanding was that this provides the DIMM serial number, but I'm
> > double checking just to be sure.
Hm, ok, then.
If this
Oliver Neukum [mailto:oneu...@suse.de]
> Sent: Tuesday, August 13, 2013 4:49 PM
> To: Hayeswang
> Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org
> Subject: Re: [PATCH net-next 1/3] net/usb/r8152: support aggregation
>
[...]
> > + len_used = 0
On 08/02/2013 10:45 AM, Daniel Lezcano wrote:
> The following changes since commit 07862c1cd6675cde2dd4bd64e64d704ea2185b79:
>
> ARM: clocksource: Add support for MOXA ART SoCs (2013-07-18 15:27:47
> +0200)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/dlezcano/
The clock passed to PCI controller found on MVEBU SoCs may come from a
clock gate. This requires the clock to be enabled before any registers
are accessed. Therefore, move the clock enable before register iomap to
ensure it is enabled.
Signed-off-by: Sebastian Hesselbarth
---
Changelog:
v1->v2:
-
This patch adds a check for DT passed reset-gpios property and deasserts/
asserts reset pin on probe/remove with configurable delay. Corresponding
binding documentation is also updated.
Signed-off-by: Sebastian Hesselbarth
---
Changelog:
v1->v2:
- use reset API compatible bindings (Reported by Ku
The number of ports is probed by counting the number of available child nodes.
Later on, the registration of a port can fail and cause a mismatch between
the ->nports counter and registered ports. This patch modifies the counting
strategy, to make ->nports represent the number of registered ports i
This patch set adds support for the PCIe controllers found on Marvell
Dove SoCs. It depends on mvebu-pci patches sent by Thomas Petazzoni.
The ARM Dove related patches have already been taken by Jason Cooper
and have been removed from v2 of this patch set. Changelog is added
to the individual patch
On Tue, Aug 13, 2013 at 12:30:56PM +0200, Ingo Molnar wrote:
> But we could perhaps do something else and push the overhead into
> resched_task(): instead of using atomics we could use the resched IPI to
> set the local preempt_count(). That way preempt_count() will only ever be
> updated CPU-l
This patch adds a compatible for the PCIe controller found on Marvell
Dove SoCs. Binding documentation and Kconfig entry are also updated.
Signed-off-by: Sebastian Hesselbarth
---
Changelog:
v1->v2:
- nothing changed
Cc: Russell King
Cc: Jason Cooper
Cc: Andrew Lunn
Cc: Bjorn Helgaas
Cc: Tho
This removes the subsys_initcall from the driver and converts it to
a normal platform_driver. Also, drvdata is set and a remove functions
is added to disable the clock and free resources. As pci driver removal
currently is not supported, set .suppress_bind_attrs to permit unbinding.
Signed-off-by:
Em Tue, 13 Aug 2013 17:06:14 +0530
"Naveen N. Rao" escreveu:
> On 08/12/2013 11:26 PM, Borislav Petkov wrote:
> > On Mon, Aug 12, 2013 at 02:25:57PM -0300, Mauro Carvalho Chehab wrote:
> >> Userspace still needs the EDAC sysfs, in order to identify how the
> >> memory is organized, and do the pro
On Tue, Aug 13, 2013 at 8:29 AM, Yan, Zheng wrote:
> From: "Yan, Zheng"
>
> This patch adds support for the SNB-EP PCU uncore PMU extra_sel_bit
> (bit 21) which is missing from the documentation in Table-2.75 of
> Intel Xeon Processor E5-2600 Product Family Uncore Performance
> Monitoring Guide.
In case of devicetree, we currently don't have a way to append pdata for
the codec. This patch makes it possible to probe the codec without pdata
for that case.
Signed-off-by: Michael Grzeschik
---
drivers/mfd/mc13xxx-core.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff
In case of devicetree, we currently don't have a way to append pdata for
the touchscreen. The current approach is to bail out in that case.
This patch makes it possible to probe the touchscreen without pdata
and use zero as default values for the atox and ato adc conversion.
Signed-off-by: Michael
On 08/12/2013 05:54 PM, Peter Wu wrote:
On Thursday 18 July 2013 16:28:01 Peter Hurley wrote:
Before we revert to using the workaround, I'd like to suggest that
this new "hidden" problem may be an interaction with the xhci_hcd host
controller driver only.
Looking at the related bug, the OP indi
On Fri, Aug 9, 2013 at 2:30 PM, Andreas Schwab wrote:
> Andreas Schwab writes:
>> Josef Bacik writes:
>>> So stripe_len shouldn't be 0, if it is you have bigger problems :).
[ lost context: this is about the first do_div() in __btrfs_map_block() ]
>> The bigger problem is that stripe_nr is u64
Em Tue, Aug 13, 2013 at 12:48:21PM +0200, Ingo Molnar escreveu:
> To resolve this situation you could help us out by doing either of these:
> 1) integrate your tests into tools/, there's 'perf test' that has a ton
> of testcases already
I think Jiri is working on merging some of those tests
On Tue, Jul 30, 2013 at 05:09:11PM +0900, Jingoo Han wrote:
> Use the wrapper function for retrieving the platform data instead of
> accessing dev->platform_data directly.
>
> Signed-off-by: Jingoo Han
Applied, Thanks
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kern
On 08/12/2013 12:39 PM, Maxim Patlasov wrote:
> The patch fixes a race between mmap-ed write and fallocate(PUNCH_HOLE):
>
> 1) An user makes a page dirty via mmap-ed write.
> 2) The user performs fallocate(2) with mode == PUNCH_HOLE|KEEP_SIZE
>and covering the page.
> 3) Before truncate_pagec
On Tue, 13 Aug 2013 12:54:26 +0200 (CEST)
Thomas Gleixner wrote:
> On Tue, 13 Aug 2013, Carsten Emde wrote:
> > On 08/13/2013 02:47 AM, Paul Gortmaker wrote:
> > > On Mon, Aug 12, 2013 at 3:48 PM, Steven Rostedt
> > > wrote:
> > > > I'm behind on 3.4-rt, 3.2-rt and of course 3.0-rt. Hopefully,
On Tue, Aug 06, 2013 at 07:35:13PM +0900, Jingoo Han wrote:
> mmp_pdma_alloc_descriptor() is used only in this file.
> Fix the following sparse warning:
>
> drivers/dma/mmp_pdma.c:359:25: warning: symbol 'mmp_pdma_alloc_descriptor'
> was not declared. Should it be static?
>
> Signed-off-by: Jing
On Tuesday 13 August 2013 05:07 PM, Tomasz Figa wrote:
> On Tuesday 13 of August 2013 16:14:44 Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Wednesday 31 July 2013 11:45 AM, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Wed, Jul 31, 2013 at 11:14:32AM +0530, Kishon Vijay Abraham I wrote:
> IMHO we
On Tue, Aug 13, 2013 at 01:49:53AM +0200, Tomasz Figa wrote:
> I've been testing this without any significant patches, like PWM, CCF or
> DT support, just everything from the branch I pointed to and some board-
> specific patches to help in debugging.
I retested with the SPI patches you sent sep
On 08/13/2013 01:22 PM, Oleksandr Kravchenko wrote:
On Tue, Aug 13, 2013 at 1:01 PM, Peter Meerwald wrote:
This patch adds IIO driver for Bosch BMA180 triaxial
acceleration sensor.
http://omapworld.com/BMA180_111_1002839.pdf
the DS is preliminary, more up-to-date version available
comments
Borislav Petkov wrote:
On Sun, Aug 11, 2013 at 01:10:11PM +0200, Rolf Eike Beer wrote:
The RAM seems fine. It looks like it is the mainboard or a harddisk.
The issues have magically disappeared since 3 weeks, but I have not
done any suspend2disk since then anymore. Before that I had suspended
th
On 08/12/2013 11:33 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.7 release.
There are 60 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
Adds a new PERF_RECORD_MMAP2 record type.
Used to request mmap records with more information about
the mapping, including device major, minor and the inode
number for mappings associated with files or shared memory
segments. Works for code and data (with attr->mmap_data set).
Existing PERF_RECORD
This patch adds support for the new PERF_RECORD_MMAP2
record type exposed by the kernel. This is an extended
PERF_RECORD_MMAP record. It adds for each file-backed
mapping the device major, minor number and the inode
number. This triplet uniquely identifies the source
of a file-backed mapping. It ca
This patch series introduces a new record type for mmaps. This
new record is called PERF_RECORD_MMAP2. It provides more information
than the existing PERF_RECORD_MMAP. For each file-backed or
shared memory segment mapping, the device major, minor and the
inode numbers are recorded. This triplet may
On Monday, August 12, 2013 07:02:44 PM Toshi Kani wrote:
> On Tue, 2013-08-13 at 02:45 +0200, Rafael J. Wysocki wrote:
> > On Monday, August 12, 2013 02:40:43 PM Toshi Kani wrote:
> > > On Sun, 2013-08-11 at 23:13 +0200, Rafael J. Wysocki wrote:
> > > > On Thursday, August 08, 2013 04:50:42 PM Tosh
On 08/12/2013 11:35 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.58 release.
There are 17 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
Salut Alexandre,
On 03/08/2013 20:00, Alexandre Belloni wrote:
ARM Performance Monitor Units are available on the am33xx, add the support in
the dtsi.
Tested with perf and oprofile on a regular beaglebone.
Signed-off-by: Alexandre Belloni
Thanks, applied for 3.12.
Regards,
Benoit
--
To un
On 08/12/2013 11:35 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.91 release.
There are 12 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Tue, Aug 13, 2013 at 01:06:18PM +0200, Ingo Molnar wrote:
>
> * Steven Rostedt wrote:
>
> > On Mon, 12 Aug 2013 22:39:22 -0400
> > Dave Jones wrote:
> >
> >
> > > I'm not sure why I got cc'd on this, but for my part, the perf/tracing
> > > related bugs I've found recently may hav
On 08/12/2013 08:14 PM, Mauro Carvalho Chehab wrote:
But, this only seems to expose the APEI data as a string
and doesn't look to really make all the fields available to user-space
in a raw manner. Not sure how well this can be utilised by a user-space
tool. Do you have suggestions on how we can
On Tuesday 13 of August 2013 16:14:44 Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 31 July 2013 11:45 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Jul 31, 2013 at 11:14:32AM +0530, Kishon Vijay Abraham I wrote:
> >>> IMHO we need a lookup method for PHYs, just like for clocks,
> >>
On Monday, August 12, 2013 06:55:03 PM Toshi Kani wrote:
> On Tue, 2013-08-13 at 02:43 +0200, Rafael J. Wysocki wrote:
> > On Monday, August 12, 2013 09:45:52 AM Toshi Kani wrote:
> > > CPU system maps are protected with reader/writer locks. The reader
> > > lock, put_online_cpus(), assures that t
On 08/12/2013 11:26 PM, Borislav Petkov wrote:
On Mon, Aug 12, 2013 at 02:25:57PM -0300, Mauro Carvalho Chehab wrote:
Userspace still needs the EDAC sysfs, in order to identify how the
memory is organized, and do the proper memory labels association.
What edac_ghes does is to fill those sysfs n
On Tue, 13 Aug 2013 11:09:34 +0530
anish singh wrote:
> > Instead, it calls irq_work() to do the event within a normal interrupt
> > context. Some architectures have the ability to trigger an interrupt on
>
> irq_work processes event in normal interrupt context as you said but
> why interrupt c
On Tue, Aug 13, 2013 at 03:37:31AM -0500, Rob Landley wrote:
> Because working with old and new qemu, like it used to before everybody
> fiddled with it to not actually match hardware nobody _has_, is
> definitely not an interesting goal.
It appears that people *do* have the hardware.
What is
On Monday, August 12, 2013 01:34:31 PM Toshi Kani wrote:
> lock_device_hotplug() serializes hotplug & online/offline operations.
> The lock is held in common sysfs online/offline interfaces and ACPI
> hotplug code paths.
>
> try_offline_node() off-lines a node if all memory sections and cpus
> are
On 08/12/13 22:04, Jason Cooper wrote:
On Mon, Aug 12, 2013 at 08:46:53PM +0200, Sebastian Hesselbarth wrote:
This adds a node for the pcie controllers found on Dove SoCs to the
SoC DT include.
Signed-off-by: Sebastian Hesselbarth
---
Cc: Russell King
Cc: Jason Cooper
Cc: Andrew Lunn
Cc: Th
The Palmas device contains only a USB VID detector, so added a
compatible type *ti,palmas-usb-vid*. Dint remove the existing compatible
types for backward compatibility.
Signed-off-by: Kishon Vijay Abraham I
---
Changes from v1:
rebased on extcon-next
Documentation/devicetree/bindings/extcon/ex
On Tue, Aug 13, 2013 at 1:01 PM, Peter Meerwald wrote:
>
>> This patch adds IIO driver for Bosch BMA180 triaxial
>> acceleration sensor.
>> http://omapworld.com/BMA180_111_1002839.pdf
>
> the DS is preliminary, more up-to-date version available
>
> comments inline
>
>> ---
>> .../devicetree/bindi
On Thu, Aug 08, 2013 at 06:15:44PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Use the existing weight reporting facility to report the transaction
> abort cost, that is the number of cycles wasted in aborts.
> Haswell reports this in the PEBS record.
>
> This was in fact the original user f
On 08/12/2013 06:23 PM, Borislav Petkov wrote:
On Mon, Aug 12, 2013 at 06:11:49PM +0530, Naveen N. Rao wrote:
So, I looked at ghes_edac and it basically seems to boil down to
trace_mc_event. But, this only seems to expose the APEI data as a
string and doesn't look to really make all the fields a
On Fri, 9 Aug 2013, Konrad Rzeszutek Wilk wrote:
> On Sun, Aug 04, 2013 at 03:39:41PM +0100, Stefano Stabellini wrote:
> > GNTTABOP_unmap_grant_ref unmaps a grant and replaces it with a 0
> > mapping instead of reinstating the original mapping.
> > Doing so separately would be racy.
> >
> > To unm
fb_notifier_callback is called on any event fired by fb_notifier_call_chain.
Events may, or may not contain some data (fb_event.data).
In case of FB_EVENT_BLANK fb_event.data contains a pointer to an integer
holding the blank state. The Problem is, that in ledtrig-backlight.c -
fb_notifier_callb
In order to support building PCI host drivers as modules, functionality
is required to undo the steps performed by pci_common_init(). The PCI
core provides much of the functionality already, so add a function that
can be called by drivers to wrap the ARM specific bits.
This patch does a number of
Implement the platform driver's .remove() callback to free all resources
allocated during driver setup and call pci_common_exit() to cleanup ARM
specific datastructures. Unmap the fixed PCI I/O mapping by calling the
new pci_iounmap_io() function in the new .teardown() callback.
Finally, no longer
The new pci_iounmap_io() function can be used to unmap a fixed PCI I/O
mapping as established by pci_ioremap_io(). This will be useful to
support unbinding of PCI host drivers.
Signed-off-by: Thierry Reding
---
arch/arm/include/asm/io.h | 1 +
arch/arm/mm/ioremap.c | 6 ++
2 files change
Hi,
This is a set of experimental patches that allow ARM PCI host drivers to
be unloaded. The first two patches enhance the ARM core PCI code with
functions to tear down fixed PCI I/O mappings and unregister a PCI host
bridge. The third patch uses the new functionality to allow the Tegra
PCIe driv
Thomas Backlund writes:
> 12.08.2013 17:27, Jordi Pujol skrev:
>> Hello,
>>
>> zram shows an error when mounting a swap partition,
>> current version Linux kernel 3.10.6,
>> previous versions worked, I suppose that latest zram patches have some
>> problem,
>>
>> machine is an AMD64 dual core, 4GB
On Tue, Aug 13, 2013 at 09:17:12AM +0200, Ionut Nicu wrote:
> Do you have any feedback for this patch?
Not yet, please allow some time for response especially over weekends.
> If you think the change is too complex, I have a simpler solution that could
> make
> things work with devices th
* Steven Rostedt wrote:
> On Mon, 12 Aug 2013 22:39:22 -0400
> Dave Jones wrote:
>
>
> > I'm not sure why I got cc'd on this, but for my part, the perf/tracing
> > related bugs I've found recently may have been there for ages, but
> > they were triggerable as non-root users.
>
> Which bug
Hi Sebastian,
Am Dienstag, den 13.08.2013, 12:40 +0200 schrieb Sebastian Hesselbarth:
> On 08/13/13 12:03, Thierry Reding wrote:
> > On Tue, Aug 13, 2013 at 10:30:30AM +0200, Thomas Petazzoni wrote:
> >> Dear Thierry Reding,
> >>
> >> On Tue, 13 Aug 2013 10:09:56 +0200, Thierry Reding wrote:
> >>
* Nathan Zimmer wrote:
> We are still restricting ourselves ourselves to 2MiB initialization.
> This was initially to keep the patch set a little smaller and more
> clear. However given how well it is currently performing I don't see a
> how much better it could be with to 2GiB chunks.
>
> A
On 08/06/2013 05:19 PM, HATAYAMA Daisuke wrote:
> Hello,
>
> I've addressing kdump restriction that there's only one cpu available
> on the kdump 2nd kernel. Now I need to check if the following CPU0 SMI
> corruption issue fixed in the following commit can again be reproduced
> by unsetting BSP fl
601 - 700 of 813 matches
Mail list logo
