On 17 July 2013 17:01, Rafael J. Wysocki wrote:
> First off, I'm not sure how many applications actually use it and I think,
> if any, they should be able cope with the attribute not being present.
>
> Of course, if it turns out that yes, there are applications using it and no,
> they cannot cope
On 07/17/2013 06:15 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
Instead of halt we started with a sleep hypercall in those
versions. Changed to halt() once Avi suggested to reuse existing sleep.
If we use older hypercall with few changes like below
On 07/16/2013 09:29 PM, Matt Turner wrote:
> I've got five patches in a for-linus branch on kernel.org that I was
> planning to send a pull request for soon. Would you like me to add
> these to that branch?
Yes, please.
r~
--
To unsubscribe from this list: send the line "unsubscribe linux-kerne
Hi Felipe,
On Wed, Jul 17, 2013 at 3:57 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
>> > The question is since we default GADGET, so the g_mass_storage.ko is
>> > installed early but connecting to a host PC
>> > is randomly, But the udev has no idea
On Wed, 2013-07-17 at 13:30 +0100, Ricardo Ferreira wrote:
> Slashdot is just a cesspool of trolls, not a good comparison.
Point taken.
I posted this privately, and I think I'll repost it here. I need to
modify it a bit as it wasn't meant to be public.
When I started sending patches to LKML it
On 07/17/2013 07:13 AM, Neil Horman wrote:
Recently we added an early quirk to detect 5500/5520 chipsets with early
revisions that had problems with irq draining with interrupt remapping enabled:
commit 03bbcb2e7e292838bb0244f5a7816d194c911d62
Author: Neil Horman
Date: Tue Apr 16 16:38:32 2013
On Wed, Jul 17, 2013 at 1:20 PM, Niels de Vos wrote:
> I can confirm that your patch fixes the original panic/BUG() with both
> Brian's test-case and the GlusterFS regression tests.
>
> Feel free to add my Tested-by/Reviewed-by signoff for this patch.
Thanks for the review and testing, patches pu
On Wednesday 17 July 2013 01:18:00 Paul Bolle wrote:
> On Wed, 2013-07-17 at 00:34 +0200, Martin Walch wrote:
> > As I am working on yet another project for analyzing LKC's input files, I
> > have some intermediate results from simple syntactical checks.
>
> Naive question: LKC?
Sorry, I thought
On 07/16/2013 10:17 PM, Matt Turner wrote:
> On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson wrote:
>> Use WTINT to wait for the next interrupt. Squash the WTINT call
>> if the PALcode doesn't support it (e.g. MILO). No attempt is yet
>> made to skip clock ticks during normal scheduling in o
On Wed, Jul 17, 2013 at 09:03:35AM -0400, Steven Rostedt wrote:
> On Wed, 2013-07-17 at 13:30 +0100, Ricardo Ferreira wrote:
> > Slashdot is just a cesspool of trolls, not a good comparison.
>
> Point taken.
>
> I posted this privately, and I think I'll repost it here. I need to
> modify it a bit
This patch adds MOXA ART SoCs clock driver support.
Signed-off-by: Jonas Jensen
---
Notes:
Changes since v2:
1. add devicetree bindings document
Applies to next-20130716
.../bindings/clock/moxa,moxart-core-clock.txt | 19 +
drivers/clk/Makefile
On Wed, Jul 17, 2013 at 06:25:05PM +0530, Raghavendra K T wrote:
> On 07/17/2013 06:15 PM, Gleb Natapov wrote:
> >On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
> Instead of halt we started with a sleep hypercall in those
> versions. Changed to halt() once Avi suggested
On Mon, 15 Jul 2013, Julien Grall wrote:
> Even if uncompress debug is disabled, some board will continue to print
> information during uncompress step.
Are you talking about DEBUG_UNCOMPRESS?
Should I read the sentence as "even if DEBUG_UNCOMPRESS is not selected,
some board will continue to prin
On Wed, Jul 17, 2013 at 09:04:54PM +0800, Rong Wang wrote:
> Hi Felipe,
>
> On Wed, Jul 17, 2013 at 3:57 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
> >> > The question is since we default GADGET, so the g_mass_storage.ko is
> >> > installed ea
On Mon, 15 Jul 2013, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 03:21:41PM +0100, Julien Grall wrote:
> > When linux is running as dom0, Xen doesn't show the physical cpu but a
> > virtual CPU.
> > On some ARM SOC (for instance the exynos 5250), linux registers callbacks
> > for cpuidle
From: Ruchika Kharwar
Ensure the Interrupt handling routine return IRQ_HANDLED vs
IRQ_NONE.
Signed-off-by: Ruchika Kharwar
Signed-off-by: Alexander Savchenko
---
drivers/tty/serial/omap-serial.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/tty/serial/omap-
On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote:
> If this is really miscelaneous code that really doesn't fit
> anywhere else, it should rather go into drivers/misc/ as a last resort.
Interestingly enough drivers/misc was my first choice for all the
vexpress stuff, but it wasn't received
On 7/17/13 2:08 AM, Namhyung Kim wrote:
From: Namhyung Kim
If an user gives both of --symfs and --vmlinux option, the vmlinux
will be searched under the symfs directory. This is somewhat
confusing since vmlinux often lives in kernel build directory or
somewhere other than user space binaries.
On 13-07-16 01:33 PM, Jonathan Corbet wrote:
> On Mon, 15 Jul 2013 19:34:44 -0400
> Paul Gortmaker wrote:
>
>> The last mainline release of a v2.6.x kernel was back in May 2011.
>> Here we update references to be 3.x based, which also means updating
>> some dates and statistics.
>
> Ccing the au
Andy Lutomirski wrote:
I'm rather confused here. In SMBUS, the "read word" operation returns
two bytes. Just to be confusing, the SMBUS spec calls the first byte
"Data Byte Low" and the second byte "Data Byte High". But they really
are the first and second bytes -- Read Word will return whatev
This patch moves at91_pmc.h header from machine specific directory
(arch/arm/mach-at91/include/mach/at91_pmc.h) to clk include directory
(include/linux/clk/at91.h).
We need this to avoid reference to machine specific headers in clk
drivers.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/a
On Mon, 15 Jul 2013, Julien Grall wrote:
> Enable power management from the toolstack for ARM guest.
>
> Signed-off-by: Julien Grall
Considering that now we support both ARM and ARM64, could you please
add an ifneq ($(CONFIG_ARM64),y) too around cpu_hotplug.o, since you are
at it?
> drivers/x
This is the at91 main oscillator clock implementation using common
clk framework.
If rate is not provided during clock registraction it is computed using
the slow clock (main clk parent in this case) rate and the MCFR register.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/Makefile |
Hello,
This patch series is a proposal to move at91 clock implementation
to common clk framework.
Most of the clock provided by the PMC (Power Management Controller) are
implemented :
- main clock (main oscillator)
- pll clocks
- master clock
- programmable clocks
- utmi clock
- peripheral clocks
Hello,
On 7/17/2013 11:43 AM, Ricardo Ribalda Delgado wrote:
Hi Marek
alloc_pages_exact returns pages of order 0, every single page is
filled into buf->pages, that then is used by vb2_dma_sg_mmap(), that
also expects order 0 pages (its loops increments in PAGE_SIZE). The
code has been tested
This is the at91 master clock implementation using common clk framework.
The pll clock layout describe the MCKR register layout.
There's four pll clock layouts:
- at91rm9200
- at91sam9x5
Master clocks are given characteristics:
- min/max clock output rate
These characteristics are checked during
On Wed, Jul 17, 2013 at 05:22:30PM +0800, Gu Zheng wrote:
> As the aio job will pin the ring pages, that will lead to mem migrated
> failed. In order to fix this problem we use an anon inode to manage the aio
> ring
> pages, and setup the migratepage callback in the anon inode's address space,
>
Arnd
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 2013年7月15日 3:30
> To: Neil Zhang
> Cc: Jason Cooper; Matt Sealey; grant.lik...@linaro.org;
> haojian.zhu...@gmail.com; devicetree-disc...@lists.ozlabs.org;
> linux-kernel@vger.kernel.org; linux-arm-ker...@lists.
This is the at91 system clock implementation using common clk framework.
Some peripheral needs to enable a "system" clock in order to work properly.
Each system clock is given an id which is the bit offset used in SCER/SCDR
registers.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/Makefile
Hello Stephen, (actually a greeting this time!)
On Wed, Jul 17, 2013 at 01:41:24PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
>
> fs/aio.c: In function 'aio_migratepage':
> fs/aio.c:196:2: error: i
(Resending with wider distribution list since my earlier email to
linux-wireless didn't get a response)
I updated the kernel on my fedora rawhide KVM guest, and noticed that
the ethernet interface wasn't coming up at all. While poking around, I
saw this stack trace pop up:
Jul 12 07:29:25 rawhide
This is the at91 utmi clock implementation using common clk framework.
This clock is a pll with a fixed factor (x40).
It is used as a source for usb clock.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |7 +++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-utmi.
This is the at91 pll clock implementation using common clk framework.
The pll clock layout describe the PLLX register layout.
There's four pll clock layouts:
- at91rm9200
- at91sam9g20
- at91sam9g45
- sama5d3
PLL clocks are given characteristics:
- min/max clock source rate
- ranges of valid cloc
This is the at91 smd (Soft Modem) clock implementation using common clk
framework.
Not used by any driver right now.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |5 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-smd.c | 157 ++
This is the at91 usb clock implementation using common clk framework.
This clock is used to clock usb ports (ohci, ehci and udc).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig | 11 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-usb.c | 303 ++
This is the documentation of the dt bindings used by at91 clks.
Signed-off-by: Boris BREZILLON
---
.../devicetree/bindings/clock/at91-clock.txt | 262
1 file changed, 262 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/at91-clock.txt
diff --
On Wed, Jul 17, 2013 at 4:17 AM, Stefano Stabellini
wrote:
> On Tue, 16 Jul 2013, H. Peter Anvin wrote:
>> Linux took off in a way that the other OSS operating systems didn't, and
>> several of them had started earlier and with way more funding available.
>>
>> You really have to think about why
On 13-07-16 07:38 PM, Steven Rostedt wrote:
> On Tue, 2013-07-16 at 16:12 -0700, Sarah Sharp wrote:
>
[...]
>
>> We need to define what behavior we want
>> from both maintainers and patch submitters. E.g. "No regressions" and
>> "don't break userspace"
>
> Yes, those do need to be documente
This is the at91 programmable clocks implementation using common clk
framework.
A programmable clock is a clock which can be exported on a given pin to clock
external devices.
Each programmable clock is given an id (from 0 to 8).
The number of available programmable clocks depends on the SoC you're
Hello again
I have made some experiments and have replaced alloc_pages_exact with
alloc_pages of order N. Unfortunatelly vm_insert_page and vm_map_ram
does not work as expected.
vm_insert_page, only insert the PAGE_SIZE bytes of the higher order
page, if I try to add the other pages manually, the
From: Sudeep KarkadaNagesha
OF/DT core library now provides architecture specific hook to match the
logical cpu index with the corresponding physical identifier. Most of the
cpu DT node parsing and initialisation is contained in devtree.c. So it's
better to define ARM specific arch_match_cpu_phys
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Acked-by: Shawn Guo
Acked-by: Viresh Kumar
Signed-off-by: Sudeep K
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Acked-by: Viresh Kumar
Signed-off-by: Sudeep KarkadaNagesha
---
d
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Benjamin Herrenschmidt
Signed-off-by: Sudeep Kark
On Mon, Jul 15, 2013 at 01:33:53PM +0200, Lars-Peter Clausen wrote:
> On 07/15/2013 01:09 PM, Kozaruk, Oleksandr wrote:
> [...]
> >
> >>> + ret = devm_request_threaded_irq(dev, irq, NULL,
> >>> + twl6030_gpadc_irq_handler,
> >>> + IRQF_ONESHOT, "twl6030_gpadc", gpadc);
> >>
> >> You access mem
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Acked-by: Shawn Guo
Acked-by: Viresh Kumar
Signed-off-by: Sudeep K
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Andrew Lunn
Cc: Jason Cooper
Acked-by: Viresh Kumar
Signed-of
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Mark Langsdorf
Acked-by: Viresh Kumar
Signed-off-by: Sudeep Ka
This is the at91 peripheral clock implementation using common clk framework.
Almost all peripherals provided by an at91 SoC need a clock to work properly.
This clock is enabled/disabled using PCER/PCDR resgisters.
Each peripheral is given an id (see atmel's datasheets) which is used as bit
positi
From: Sudeep KarkadaNagesha
Since the CPU device nodes can be retrieved using arch_of_get_cpu_node,
we can use it to avoid parsing the cpus node searching the cpu nodes and
mapping to logical index.
This patch removes parsing DT for cpu nodes by using of_get_cpu_node.
Cc: Lorenzo Pieralisi
Sig
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Deepak Sikri
Acked-by: Viresh Kumar
Signed-off-by: Sudeep Kark
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Benjamin Herrenschmidt
Signed-off-by: Sudeep
From: Sudeep KarkadaNagesha
Now that the cpu device registration initialises the of_node(if available)
appropriately for all the cpus, parsing here is redundant.
This patch removes all DT parsing and uses cpu->of_node instead.
Cc: Viresh Kumar
Cc: Dmitry Eremin-Solenikov
Signed-off-by: Sudeep
From: Sudeep KarkadaNagesha
Currently different drivers requiring to access cpu device node are
parsing the device tree themselves. Since the ordering in the DT need
not match the logical cpu ordering, the parsing logic needs to consider
that. However, this has resulted in lots of code duplicatio
From: Sudeep KarkadaNagesha
Currently set_secondary_cpus_clock assume the CPU logical ordering
and the MPDIR in DT are same, which is incorrect.
Since the CPU device nodes can be retrieved in the logical ordering
using the DT helper, we can remove the devices tree parsing.
This patch removes DT
On Wed, 2013-07-17 at 15:16 +0100, Nicolas Pitre wrote:
> On Wed, 17 Jul 2013, Pawel Moll wrote:
>
> > On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote:
> > > If this is really miscelaneous code that really doesn't fit
> > > anywhere else, it should rather go into drivers/misc/ as a last re
Hello again Marek
In my system I am doing the scatter gather compaction on device
driver... But I agree that it would be better done on the vb2 layer.
For the oversize sglist we could do one of this two things.
If we want to have a simple pass processing we have to allocate an
structure A for th
From: Sudeep KarkadaNagesha
CPUs are also registered as devices but the of_node in these cpu
devices are not initialized. Currently different drivers requiring
to access cpu device node are parsing the nodes themselves and
initialising the of_node in cpu device.
The of_node in all the cpu device
On 17 July 2013 16:29, Mark Brown wrote:
> From: Mark Brown
>
> This avoids polluting the global namespace and silences lots of sparse
> warnings. The change pushes us over 80 columns a lot but I couldn't see
> a tasteful place to break the lines as-is.
>
> Signed-off-by: Mark Brown
I have alre
On 07/17/2013 06:55 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 06:25:05PM +0530, Raghavendra K T wrote:
On 07/17/2013 06:15 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
Instead of halt we started with a sleep hypercall in those
versions. Chang
On Wed, 17 Jul 2013, sudeep.karkadanage...@arm.com wrote:
> From: Sudeep KarkadaNagesha
>
> Currently different drivers requiring to access cpu device node are
> parsing the device tree themselves. Since the ordering in the DT need
> not match the logical cpu ordering, the parsing logic needs to
On 17 July 2013 16:29, Mark Brown wrote:
> From: Mark Brown
>
> As the comment says exynos4_clk_register_fixed_ext() was only used by
> non-DT platforms. Since Exynos is now DT only it is no longer referenced
> and can be removed.
>
> Signed-off-by: Mark Brown
Similar patch has already been pos
zbud_alloc() incorrectly verifies the size of allocation limit. It
should deny the allocation request greater than (PAGE_SIZE -
ZHDR_SIZE_ALIGNED - CHUNK_SIZE), not (PAGE_SIZE - ZHDR_SIZE_ALIGNED)
which has no remaining spaces for its buddy. There is no point in
spending the entire zbud page storin
On 16/07/13 10:03, Sudeep KarkadaNagesha wrote:
> On 15/07/13 20:10, Rob Herring wrote:
>> On 07/15/2013 05:22 AM, sudeep.karkadanage...@arm.com wrote:
>>> From: Sudeep KarkadaNagesha
>>>
>>> CPU subsystem now provides architecture specific hook to retrieve the
>>> of_node. Most of the cpu DT node
Myron,
On Tue, Jul 16, 2013 at 8:21 PM, Myron Stowe wrote:
>
> Shuah - You brought up the idea about "Converting drivers from Legacy
> PM ops to dev_pm_ops"; would you like to present what you have
> done/encountered so far?
>
Awesome. Yes, I would like to present what I have done so far and I
Hello.
On 17-07-2013 15:12, Oleksandr Kozaruk wrote:
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk
---
arch/arm/boot/dts/twl6030.dtsi | 6 ++
1 file changed, 6 insertions(+)
dif
This patch removes the old at91 clk implementation, and keep the
PMC initialization and sam9idle functions in pmc.c.
The at91_initialize function no longer initiliaze at91 clks: the new clk
registration process requires kzalloc which is not available when early_init
is called.
The clk registration
On 07/17/2013 07:43 PM, Raghavendra K T wrote:
On 07/17/2013 06:55 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 06:25:05PM +0530, Raghavendra K T wrote:
On 07/17/2013 06:15 PM, Gleb Natapov wrote:
On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
Instead of halt we started w
On Tue, Jul 16, 2013 at 8:02 PM, Sarah Sharp
wrote:
> I've provided examples and personal stories in an attempt to give
> incentive to change.
Those are just stories; things that happened. What you need to provide
is *evidence* that if the community changes, things will be better,
and unless you
From: Sudeep KarkadaNagesha
Currently the topology code computes cpu capacity and stores it in
the list along with hwid(which is MPIDR) as it parses the CPU nodes
in the device tree. This is required as it needs to be mapped to the
logical CPU later.
Since the CPU device nodes can be retrieved i
On 7/16/13 8:16 PM, Christian Ruppert wrote:> On Sat, Jul 13, 2013 at
02:36:43PM +0900, Shinya Kuribayashi wrote:
Basically, DW I2C core provides a good enough (and quite direct) way
to control tHIGH and tLOW timing specs, *HCNT and *LCNT registers.
But from my experience (with a slightly old v
From: Sudeep KarkadaNagesha
As more and more information is getting added into the cpu node, the number
of drivers needing to parse the device tree for CPU nodes are increasing.
Most of the time, the information needed from the cpu node is preferred
in the logical CPU order. Hence many drivers fi
On Wed, 17 Jul 2013, Pawel Moll wrote:
> On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote:
> > If this is really miscelaneous code that really doesn't fit
> > anywhere else, it should rather go into drivers/misc/ as a last resort.
>
> Interestingly enough drivers/misc was my first choice f
On Tue, Jul 16, 2013 at 04:23:08PM +0100, Arjan van de Ven wrote:
> On 7/16/2013 5:42 AM, Catalin Marinas wrote:
> > Morten's power scheduler tries to address the above and it will grow
> > into controlling a new model of power driver (and taking into account
> > Arjan's and others' comments regard
On Wed, Jul 17, 2013 at 09:01:02AM -0500, Felipe Contreras wrote:
> I know you think "being nice" is better, but do you actually have any
> evidence for this, or is it just wishful thinking? If you don't have
> hard evidence, then I'd say you have to admit it's simply your
> opinion, and I don't th
This patch removes all references to the old at91 clks implementation and
make use of the new at91 clk implem for at91rm9200 SoC.
All dt specific lookups are removed (handled in clk device tree binding).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |1 +
arch/arm/mach-
This patch removes all references to the old at91 clks implementation and
make use of the new at91 clk implem for at91sam9263 SoC.
All dt specific lookups are removed (handled in clk device tree binding).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9263.c | 593 +++
On Wed, Jul 17, 2013 at 07:43:01PM +0530, Raghavendra K T wrote:
> On 07/17/2013 06:55 PM, Gleb Natapov wrote:
> >On Wed, Jul 17, 2013 at 06:25:05PM +0530, Raghavendra K T wrote:
> >>On 07/17/2013 06:15 PM, Gleb Natapov wrote:
> >>>On Wed, Jul 17, 2013 at 03:35:37PM +0530, Raghavendra K T wrote:
>
On 07/17/2013 03:45 PM, Oleksandr Kozaruk wrote:
> On Mon, Jul 15, 2013 at 01:33:53PM +0200, Lars-Peter Clausen wrote:
>> On 07/15/2013 01:09 PM, Kozaruk, Oleksandr wrote:
>> [...]
>> >
>> >>> + ret = devm_request_threaded_irq(dev, irq, NULL,
>> >>> + twl6030_gpadc_irq_handler,
>> >>> + IRQF_ON
On Wed, Jul 17, 2013 at 03:36:36AM -0400, CAI Qian wrote:
> > On Tue, 2013-07-16 at 19:31 -0400, Ric Wheeler wrote:
> > > On 07/16/2013 07:12 PM, Sarah Sharp wrote:
> > > > On Tue, Jul 16, 2013 at 06:54:59PM -0400, Steven Rostedt wrote:
> > > >> On Tue, 2013-07-16 at 15:43 -0700, Sarah Sharp wrote:
This patch removes all references to the old at91 clks implementation and
make use of the new at91 clk implem for at91sam9g45 SoC.
All dt specific lookups are removed (handled in clk device tree binding).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9g45.c | 702 +++
On 07/17, Masami Hiramatsu wrote:
>
> At a glance, you're trying to change which operation will be
> failed. Currently, user can not remove an event while someone
> opens files which related to the event. And this approach
> changes that the someone can remove the event even if the
> files are open
On Wed, Jul 17, 2013 at 07:40:43AM -0700, Sarah Sharp wrote:
> Go look at Dreamwidth, the open source Livejournal fork. It has a good
> code of conduct, so developers are civil to each other. They encourage
> all patch submissions, and take the time to work with people who don't
> understand thei
On Wed, Jul 17, 2013 at 02:53:22PM +0200, Jan Kara wrote:
> On Tue 16-07-13 16:25:33, Dave Jones wrote:
> > I've seen this happen a few times this week..
> Thanks for report! Was this when fuzzing or just normal desktop load?
> What is inode with inode number 12 on your filesystem sdb1? What
This patch removes all references to the old at91 clks for at91sam9x5 SoCs.
These SoCs only supports dt boards: we can remove register_clocks
(all clocks are defined in dt).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9x5.c | 291 ---
1 file
This patch removes all references to the old at91 clks implementation and
make use of the new at91 clk implem for at91sam9rl SoC.
All dt specific lookups are removed (handled in clk device tree binding).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9rl.c | 500 +
On 07/17/2013 04:33 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 17-07-2013 15:12, Oleksandr Kozaruk wrote:
>
>> GPADC is the general purpose ADC present on twl6030.
>> The dt data is interrupt used to trigger end of ADC
>> conversion.
>
>> Signed-off-by: Oleksandr Kozaruk
>> ---
>> arch/arm/bo
This patch removes all references to the old at91 clks for at91sam9n12 SoC.
This SoC only supports dt boards: we can remove register_clocks
(all clocks are defined in dt).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9n12.c | 194 --
1 file ch
This patch removes all references to the old at91 clks for sama5d3 SoCs.
These SoCs only supports dt boards: we can remove register_clocks
(all clocks are defined in dt).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig |1 +
arch/arm/mach-at91/sama5d3.c | 342 ---
On Wed, 17 Jul 2013 18:31:19 +0530 Viresh Kumar viresh.ku...@linaro.org
wrote,
> On 17 July 2013 17:01, Rafael J. Wysocki wrote:
> > First off, I'm not sure how many applications actually use it and I
> > think, if any, they should be able cope with the attribute not
> > being present.
> >
> > Of
Move at91 clk init from early_init to timer_init for all at91rm9200 non dt
boards.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/board-1arm.c | 12 ++--
arch/arm/mach-at91/board-carmeva.c| 13 -
arch/arm/mach-at91/board-cpuat91.c| 12 ++--
This patch removes all references to the old at91 clks implementation and
make use of the new at91 clk implem for at91sam9261 SoC.
All dt specific lookups are removed (handled in clk device tree binding).
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9261.c | 570 +++
On 07/17, Masami Hiramatsu wrote:
>
> (2013/07/16 3:16), Oleg Nesterov wrote:
> > On 07/09, Masami Hiramatsu wrote:
> >>
> >> To avoid this, when opening events/*/*/enable, we have to ensure
> >> the dentry of the file is not unlinked yet, under event_mutex
> >> is locked.
> >
> > Probably this can
On Wed, Jul 17, 2013 at 03:06:20PM +0100, sudeep.karkadanage...@arm.com wrote:
> From: Sudeep KarkadaNagesha
>
> Now that the cpu device registration initialises the of_node(if available)
> appropriately for all the cpus, parsing here is redundant.
>
> This patch removes all DT parsing and uses
On 07/17/2013 09:06 AM, sudeep.karkadanage...@arm.com wrote:
> From: Sudeep KarkadaNagesha
>
> Currently different drivers requiring to access cpu device node are
> parsing the device tree themselves. Since the ordering in the DT need
> not match the logical cpu ordering, the parsing logic needs
On Wed, 17 Jul 2013 10:22:58 +0400
Konstantin Khlebnikov wrote:
> This patch fixes regression in power consumtion of sandy bridge gpu, which
> exists since v3.6 Sometimes after resuming from s2ram gpu starts thinking that
> it's extremely busy. After that it never reaches rc6 state.
>
> Bug exis
This patch changes the cpufreq-cpu0 driver to consider if
a cpu needs cooling (with cpufreq). In case the cooling is needed,
it can be flagged at the cpu0 device tree node, with the boolean
property 'needs-cooling'.
In case this boolean is present, the driver will
load a cpufreq cooling device in
In order to be able to build thermal policies
based on generic sensors, like I2C device, that
can be places in different points on different boards,
there is a need to have a way to feed board dependent
data into the thermal framework.
This patch introduces a thermal data parser for device
tree. T
This patch adds to lm75 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the lm75 DT node. Otherwise, the driver behavior
This patch adds to tmp102 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the tmp102 DT node. Otherwise, the driver beha
201 - 300 of 982 matches
Mail list logo
