/lib/libc.so) to see the eviction
cycles, and find out if frequently used code is
rather spread across many pages (bad) or coallesced
(good).
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
include/trace/events/filemap.h | 79
mm/filemap.c
Chao Xie chao@marvell.com writes:
Hi Chao Xie,
First of all, could you please send patches from rtc-pxa to me also, as I'm
maintaining that driver ?
Second point, the original design of the driver relies on the special case of
writing zeroes to WOM and DOM, as mentionned in PXA27x
Chao Xie chao@marvell.com writes:
The original pxa_rtc_open/pxa_rtc_release will be called
when the /dev/rtc0 is opened or closed.
In fact, these two functions will register/unregister the irqs.
User application will use /dev/rtc0 to read the rtc time or set
the alarm. The rtc should
/lib/libc.so) to see the eviction
cycles, and find out if frequently used code is
rather spread across many pages (bad) or coallesced
(good).
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
include/trace/events/filemap.h | 79
mm/filemap.c
Andrew Morton a...@linux-foundation.org writes:
+TP_STRUCT__entry(
+__field(struct page *, page)
+__field(unsigned long, i_no)
May as well call this i_ino - there's little benefit in using a
different identifier.
Agreed for patch V2.
+
Dave Chinner da...@fromorbit.com writes:
We actually have an informal convention for formating filesystem
trace events, and that is to use the device number
+ ),
+
+ TP_printk(page=%p pfn=%lu blk=%d:%d inode+ofs=%lu+%lu,
... and to prefix messages like:
TP_printk(dev
Hugh Dickins hu...@google.com writes:
On Thu, 8 Nov 2012, Robert Jarzmik wrote:
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -467,6 +471,7 @@ int add_to_page_cache_locked(struct page *page, struct
address_space *mapping,
} else {
page-mapping = NULL
Dave Chinner da...@fromorbit.com writes:
We actually have an informal convention for formating filesystem
trace events, and that is to use the device number
+ ),
+
+ TP_printk(page=%p pfn=%lu blk=%d:%d inode+ofs=%lu+%lu,
... and to prefix messages like:
TP_printk(dev
/lib/libc.so) to see the eviction
cycles, and find out if frequently used code is
rather spread across many pages (bad) or coallesced
(good).
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1:
- included Andrew's comments
- included Dave's comment
- fixed according to Hugh's
/lib/libc.so) to see the eviction
cycles, and find out if frequently used code is
rather spread across many pages (bad) or coallesced
(good).
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1:
- included Andrew's comments
- included Dave's comment
- fixed according to Hugh's
description.
But anyway :
Acked-by: Robert Jarzmik robert.jarz...@free.fr
--
Robert
--
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 read the FAQ
771d13b0094421b98310171d8794f2a793ec5d4d Mon Sep 17 00:00:00 2001
From: Robert Jarzmik robert.jarz...@free.fr
Date: Mon, 9 Apr 2012 13:19:08 +0200
Subject: [PATCH] mtd: docg3 fix missing bitreverse lib
Fix missing dependency which can cause a build error such
as: ERROR: byte_rev_table [drivers/mtd/devices/docg3.ko]
undefined
Guennadi Liakhovetski g.liakhovet...@gmx.de writes:
(adding Robert to CC)
I don't think any data is freed by pxa_free_dma(), it only disables DMA on
a certain channel. Theoretically there could be a different problem:
pxa_free_dma() deactivates DMA, whereas pxa_dma_start_channels()
Wei Yongjun weiyj...@gmail.com writes:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Use free_bch() instead of kfree() to free init_bch()
allocated data.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
Acked-by: Robert Jarzmik robert.jarz...@free.fr
--
To unsubscribe from
Dave Jones da...@redhat.com writes:
On Thu, Mar 20, 2014 at 01:43:44PM +1030, Rusty Russell wrote:
drivers/mtd/devices/docg3.c:
__ATTR(f##id##_dps0_protection_key, S_IWUGO, NULL, dps0_insert_key), \
__ATTR(f##id##_dps1_protection_key, S_IWUGO, NULL, dps1_insert_key), \
Chao Xie chao@marvell.com writes:
This patch have something wrong.
1.The pxa_sync_time API is not needed. The RTC sync can be done
by user space applications, so in kernel this API is not needed.
2.The pxa_rtc_open can not be deleted. This change has been
declined during review at the
(except in comments).
Signed-off-by: Michael Opdenacker michael.opdenac...@free-electrons.com
This clean up looks good to me.
Acked-by: Kees Cook keesc...@chromium.org
Yes, a consequence of the beheading in the commit mtd: doc: remove support for
DoC 2000/2001/2001+, excellent.
Acked-by: Robert
Add device-tree support to max1586.
The driver can still be used with the legacy platform data, or the new
device-tree way.
This work is heavily inspired by the device-tree support of its cousin
max8660 driver.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
drivers/regulator/max1586.c
Add max1586 regulator device-tree bindings documentation.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
.../bindings/regulator/max1586-regulator.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator
Mark Brown broo...@kernel.org writes:
On Sat, Jun 14, 2014 at 04:54:24PM +0200, Robert Jarzmik wrote:
+matched = of_regulator_match(dev, np, rmatch, ARRAY_SIZE(rmatch));
+of_node_put(np);
+if (matched = 0)
+return matched;
Why is this treating zero as an error? We
is not signaled by the tasklet
Cheers.
--
Robert
(1)
commit 4741ba6 (pxa_camera_dmaengine, backup/pxa_camera_dmaengine)
Author: Robert Jarzmik robert.jarz...@free.fr
Date: Sat Aug 24 21:13:38 2013 +0200
WIP: pxa_camera dmaengine conversion
Only slightly tested, without much success
Julia Lawall julia.law...@lip6.fr writes:
From: Julia Lawall julia.law...@lip6.fr
Replace ARRAY_AND_SIZE(e) in function argument position to avoid hiding the
arity of the called function.
Acked-by: Robert Jarzmik robert.jarz...@free.fr
As a side I'm curious why this change didn't touch also
Mark Brown broo...@kernel.org writes:
On Tue, Jun 17, 2014 at 09:16:52PM +0200, Robert Jarzmik wrote:
Mark Brown broo...@kernel.org writes:
On Sat, Jun 14, 2014 at 04:54:24PM +0200, Robert Jarzmik wrote:
+ matched = of_regulator_match(dev, np, rmatch, ARRAY_SIZE(rmatch));
+ of_node_put
Select CLKSRC_OF for PXA architectures, as the clocksource
driver can be also initialized from device-tree.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: Russell King li...@arm.linux.org.uk
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b
Move time.c from arch/arm/mach-pxa/time.c to
drivers/clocksource/pxa_timer.c.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/mach-pxa/Makefile | 2 +-
drivers/clocksource/Makefile| 1 +
arch/arm/mach-pxa/time.c
Add device-tree support to PXA platforms.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
drivers/clocksource/pxa_timer.c | 131 ++--
1 file changed, 98 insertions(+), 33 deletions(-)
diff --git a/drivers/clocksource/pxa_timer.c b/drivers/clocksource
Daniel Lezcano daniel.lezc...@linaro.org writes:
On 07/14/2014 06:52 PM, Robert Jarzmik wrote:
As clocksource pxa_timer was moved to clocksource framework, the
pxa_timer initialization needs to be a bit amended, to pass the
necessary informations to clocksource, ie :
- the timer interrupt
Robert Jarzmik robert.jarz...@free.fr writes:
Move time.c from arch/arm/mach-pxa/time.c to
drivers/clocksource/pxa_timer.c.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Ping ?
Cheers.
--
Robert
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Daniel Lezcano daniel.lezc...@linaro.org writes:
Good question.
Maybe not, I followed the same rationale as in orion-timer, which is :
- as this timer is the only possible timer for PXA boards, and because
without
it the kernel boot will stall (scheduling will be blocked), it's better
Move time.c from arch/arm/mach-pxa/time.c to
drivers/clocksource/pxa_timer.c.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/mach-pxa/Makefile | 2 +-
drivers/clocksource/Makefile| 1 +
arch/arm/mach-pxa/time.c
As clocksource pxa_timer was moved to clocksource framework, the
pxa_timer initialization needs to be a bit amended, to pass the
necessary informations to clocksource, ie :
- the timer interrupt (mach specific)
- the timer registers base (ditto)
- the timer clockrate
Signed-off-by: Robert
Select CLKSRC_OF for PXA architectures.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 87b63fd..472dea1 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -644,6 +644,7
Add device-tree support to PXA platforms.
The driver still needs to maintain backward non device-tree
compatibility as well, which implies :
- a non device-tree init function
- a static registers base address in the driver
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1
Move time.c from arch/arm/mach-pxa/time.c to
drivers/clocksource/pxa_timer.c.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/mach-pxa/Makefile | 2 +-
drivers/clocksource/Makefile| 1 +
arch/arm/mach-pxa/time.c
the current settings.
diff --git a/include/clocksource/pxa.h b/include/clocksource/pxa.h
new file mode 100644
index 000..1efbe5a
--- /dev/null
+++ b/include/clocksource/pxa.h
@@ -0,0 +1,18 @@
+/*
+ * PXA clocksource, clockevents, and OST interrupt handlers.
+ *
+ * Copyright (C) 2014 Robert Jarzmik
Select CLKSRC_OF for PXA architectures.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 87b63fd..472dea1 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -644,6 +644,7
Add device-tree support to PXA platforms.
The driver still needs to maintain backward non device-tree
compatibility as well, which implies :
- a non device-tree init function
- a static registers base address in the driver
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1
Daniel Lezcano daniel.lezc...@linaro.org writes:
-#include mach/regs-ost.h
#include mach/irqs.h
+#include mach/hardware.h
Now as the driver is in 'drivers', do not reference the headers files in
mach. Moving the driver to the drivers directory implies some cleanup with the
headers
Robert Jarzmik robert.jarz...@free.fr writes:
Daniel Lezcano daniel.lezc...@linaro.org writes:
-#include mach/regs-ost.h
#include mach/irqs.h
+#include mach/hardware.h
Now as the driver is in 'drivers', do not reference the headers files in
mach. Moving the driver to the drivers
pxa_timer_nodt_init(),
which is. The function is only called at init time, so it is safe
to also annotate it this way.
Signed-off-by: Arnd Bergmann a...@arndb.de
Indeed.
Acked-by: Robert Jarzmik robert.jarz...@free.fr
Cheers.
--
Robert
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
Yes please Arnd, I'm still out for 1.5 week, so it would be great if you take
that through your tree with my ack. Thanks.
Robert
PS: I know, top-posting is madness, but I'm really limited by technology right
now.
- Mail d'origine -
De: Arnd Bergmann a...@arndb.de
À: Robert Jarzmik
Add device-tree support to max1586.
The driver can still be used with the legacy platform data, or the new
device-tree way.
This work is heavily inspired by the device-tree support of its cousin
max8660 driver.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1: added the comment
Add max1586 regulator device-tree bindings documentation.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
.../bindings/regulator/max1586-regulator.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator
Add max1586 regulator device-tree bindings documentation.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
.../bindings/regulator/max1586-regulator.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator
Add device-tree support to max1586.
The driver can still be used with the legacy platform data, or the new
device-tree way.
This work is heavily inspired by the device-tree support of its cousin
max8660 driver.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since V1: added the comment
Joe Perches j...@perches.com writes:
Use the more common pr_warn.
Other miscellanea:
o Coalesce formats
o Realign arguments
Signed-off-by: Joe Perches j...@perches.com
Applied to pxa/cleanup branch, thanks.
--
Robert
--
To unsubscribe from this list: send the line unsubscribe
Pavel Machek pa...@ucw.cz writes:
Thanks for the info.
I added
+Mainline has support for Mitac Mio A701, but that having only 64MiB
+RAM, QTopia is the software to use there.
Thanks Pavel, that looks good.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line
Paul Bolle pebo...@tiscali.nl writes:
Robert,
Your commit 03ec7fe70c5c (arm: pxa: add pxa27x device-tree support) is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Ah yes, you're perfectly right,
As IRQ0, the legacy timer interrupt should not be used as an interrupt
number, shift the interrupts by a fixed number.
As we had in a special case a shift of 16 when ISA bus was used on a
PXA, use that value as the first interrupt number, regardless of ISA or
not.
Signed-off-by: Robert Jarzmik
Daniel Lezcano daniel.lezc...@linaro.org writes:
On 07/21/2014 08:15 PM, Robert Jarzmik wrote:
Daniel Lezcano daniel.lezc...@linaro.org writes:
On 07/14/2014 06:52 PM, Robert Jarzmik wrote:
As clocksource pxa_timer was moved to clocksource framework, the
pxa_timer initialization needs
Dmitry Eremin-Solenikov dbarysh...@gmail.com writes:
2014-11-09 0:01 GMT+03:00 Robert Jarzmik robert.jarz...@free.fr:
clock enable_cnt prepare_cntrate
accuracy phase
. The remaining steps are
:
- pxa3xx
- once PXA is fully converted to device tree, if that happens,
clk-pxa2* and clk-pxa3* should only hold the core clocks which cannot
be described in devicetree.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Tested-by: Dmitry Eremin-Solenikov dbarysh
,
which cannot acquire the OSTIMER0 clock.
To solve this issue, the clocks initialization is moved to pxa_timer(),
so that clocks are initialized before clocksource for non device-tree.
For device-tree, the standard arm time_init() will take care of the
ordering.
Signed-off-by: Robert Jarzmik
Add 2 clocks which were erronously forgotten by the clock framework
port, namely :
- sa1100-rtc
- irda for pxa2xx-ir:UARTCLK
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
drivers/clk/pxa/clk-pxa27x.c | 29 +
1 file changed, 29 insertions(+)
diff --git
The pxa25x gpio11 clock output was previously selected on its pin by the
clock enabling, toggling the pin function.
As we transition to common clock framework, the pin function is moved to
board file for the 2 users, ie. lubbock and eseries.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
).
This is targeted at 3.20 window.
Cheers.
--
Robert
Robert Jarzmik (4):
arm: pxa: change clocks init sequence
arm: pxa: Transition pxa25x and pxa27x to clk framework
arm: pxa: move gpio11 clock to board files
clk: pxa: add missing pxa27x clocks for Irda and sa1100-rtc
arch/arm/Kconfig
). Machine files should be amended to take
that into account.
This is the last step of clock framework transition for pxa25x and
pxa27x, leaving only pxa3xx for further work.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/Kconfig | 1 +
arch/arm/mach-pxa/Makefile | 9
.
And if you want to give a review, even better.
Cheers.
--
Robert
Robert Jarzmik (3):
clk: add pxa25x clock drivers
arm: pxa: Transition pxa25x to clk framework
ARM: pxa: move gpio11 clock to board files
arch/arm/Kconfig | 1 +
arch/arm/mach-pxa/Makefile | 9 +-
arch/arm
files should be amended to take
that into account.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/Kconfig| 1 +
arch/arm/mach-pxa/Makefile | 9 +--
arch/arm/mach-pxa/generic.c | 2 +
arch/arm/mach-pxa/generic.h | 1 +
arch/arm/mach-pxa/pxa25x.c | 182
. The remaining steps are
:
- pxa3xx
- once PXA is fully converted to device tree, if that happens,
clk-pxa2* and clk-pxa3* should only hold the core clocks which cannot
be described in devicetree.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
drivers/clk/pxa/Makefile | 1 +
drivers
The pxa25x gpio11 clock output was previously selected on its pin by the
clock enabling, toggling the pin function.
As we transition to common clock framework, the pin function is moved to
board file for the 2 users, ie. lubbock and eseries.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Jarzmik robert.jarz
As the interrupt handling was transferred to the cottula driver, make
the switch in lubbock platform code.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/mach-pxa/include/mach/lubbock.h | 7 +-
arch/arm/mach-pxa/lubbock.c | 112 +--
2
Dmitry Eremin-Solenikov dbarysh...@gmail.com writes:
Hello,
Tested in qemu (pxa25x target).
Excellent.
0) Had to revert 23c4a3a5212701ad34bd30591fa33d7bacef9c5f to get kernel
to build for pxa25x + pxa27x.
Yes, good move.
1) I got the following backtrace early in the boot:
Division by
7f43d2f9c9d415b8bc1ed7e2f3e422de349d6957 Mon Sep 17 00:00:00 2001
From: Robert Jarzmik robert.jarz...@free.fr
Date: Sat, 8 Nov 2014 18:20:18 +0100
Subject: [PATCH] fixup! clk: add pxa25x clock drivers
---
drivers/clk/pxa/clk-pxa25x.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Dmitry Eremin-Solenikov dbarysh...@gmail.com writes:
2014-11-08 20:26 GMT+03:00 Robert Jarzmik robert.jarz...@free.fr:
Dmitry Eremin-Solenikov dbarysh...@gmail.com writes:
Hello,
Tested in qemu (pxa25x target).
2) sa1100-rtc could not find a clock and thus failed to be probed.
4) Got
Dmitry Eremin-Solenikov dbarysh...@gmail.com writes:
2014-11-09 0:01 GMT+03:00 Robert Jarzmik robert.jarz...@free.fr:
Tested-by: Dmitry Eremin-Solenikov dbarysh...@gmail.com
OK, that's really great, thanks for your testing effort.
I'll digest the clk_summary output next week to cross-check
. The remaining steps are
:
- pxa3xx
- once PXA is fully converted to device tree, if that happens,
clk-pxa2* and clk-pxa3* should only hold the core clocks which cannot
be described in devicetree.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Tested-by: Dmitry Eremin-Solenikov dbarysh
Pavel Machek pa...@ucw.cz writes:
On Thu 2014-11-13 20:18:04, Aaro Koskinen wrote:
Hi,
On Thu, Nov 13, 2014 at 09:45:36AM -0800, Tony Lindgren wrote:
* Pavel Machek pa...@ucw.cz [141113 08:23]:
OTOH ofono seems pretty reasonable. So I played a bit, and result
is python/pygtk gui
Nicolas Pitre nicolas.pi...@linaro.org writes:
Let ktime_divns() use do_div() inline whenever the divisor is constant
and small enough. This will make things like ktime_to_us() and
ktime_to_ms() much faster.
Hi Nicolas,
I suppose the small enough is linked to the !(div 32) in your patch.
Haojian Zhuang haojian.zhu...@gmail.com writes:
I think that it's a kind of irq muxing, just like lots of PMIC (power
management IC).
We should move the lubbock board irqs to a mfd driver, and register them as
threaded irqs.
I will have a look.
I didn't consider mfd for motherboard gates,
Robert Jarzmik robert.jarz...@free.fr writes:
Arnd Bergmann a...@arndb.de writes:
On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
+
+ platform_set_drvdata(pdev, cot);
+ cot-gpio0 = gpiod_get(pdev-dev, lubbock_irq, 0);
+ if (IS_ERR(cot-gpio0
Arnd Bergmann a...@arndb.de writes:
On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
+
+ platform_set_drvdata(pdev, cot);
+ cot-gpio0 = gpiod_get(pdev-dev, lubbock_irq, 0);
+ if (IS_ERR(cot-gpio0)) {
+ dev_err(pdev-dev, Couldn't request GPIO : ret
Arnd Bergmann a...@arndb.de writes:
Will that look correct ?
I'd still prefer the platform data, but this seems good enough and I
see no serious problems with it.
OK, so I'll try with the 2 resources. If I'm bitten afterwards and am forced to
have a platform data, you'll tell me I had warned
that pxa_gpio_probe() was called before, so that lubbock
handler becomes the true IRQ chained handler of GPIO0, demuxing the
lubbock IO board interrupts.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
For Thomas: as a side note, I'm not very happy with this patch. What
makes me unhappy
Thomas Gleixner t...@linutronix.de writes:
So what is the relationship between installing that chained handler
and that gpio-pxa probe stuff?
The relation is in gpio-pxa probe, look at the extract of pxa_gpio_probe() :
pxa_gpio_probe()
irq = gpio_to_irq(0);
Remove the useless CPU_PXA27x non existing kconfig option.
The true options is PXA27x, which is already selected.
Reported-by: Paul Bolle pebo...@tiscali.nl
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/mach-pxa/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch
Mika Westerberg mika.westerb...@linux.intel.com writes:
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be transferred. If there are more messages in the queue, it is
possible that
Robert Jarzmik robert.jarz...@free.fr writes:
Remove the useless CPU_PXA27x non existing kconfig option.
The true options is PXA27x, which is already selected.
Reported-by: Paul Bolle pebo...@tiscali.nl
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Queued to pxa/for-next.
--
Robert
Robert Jarzmik robert.jarz...@free.fr writes:
As IRQ0, the legacy timer interrupt should not be used as an interrupt
number, shift the interrupts by a fixed number.
As we had in a special case a shift of 16 when ISA bus was used on a
PXA, use that value as the first interrupt number
Mika Westerberg mika.westerb...@linux.intel.com writes:
On Thu, Dec 04, 2014 at 10:01:06PM +0100, Robert Jarzmik wrote:
So with your change, we have :
drv_data-cur_chip = NULL;
spi_finalize_current_message(drv_data-master);
In that case, if spi_finalize_current_message() queues
Andy Lutomirski l...@amacapital.net writes:
I don't really care about the number of instructions.
Right, a couple of test/jz/jnz is negligible in the exception path, that's what
I also think.
But there are still all the nasty cases:
- Context switch during exception processing (both in the
Hi Andy,
Andy Lutomirski l...@amacapital.net writes:
On Dec 6, 2014 2:31 AM, Robert Jarzmik robert.jarz...@intel.com wrote:
We would have a LBR resource variable to track who owns the LBR :
- nobody : LBR_UNCLAIMED
- the exception handler : LBR_EXCEPTION_DEBUG_USAGE
Which exception handler
, demuxing the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Jarzmik
Robert Jarzmik robert.jarz...@free.fr writes:
@@ -66,18 +67,20 @@ static inline void __iomem *irq_base(int i)
void pxa_mask_irq(struct irq_data *d)
{
void __iomem *base = irq_data_get_irq_chip_data(d);
+ irq_hw_number_t irq = irqd_to_hwirq(d);
uint32_t icmr = __raw_readl
Stephen Boyd sb...@codeaurora.org writes:
On 01/31/15 14:37, Robert Jarzmik wrote:
As pxa27x_clocks_init() is called from early boot stage, it has to be
reachable from pxa architecture code, as are pxa25x_clocks_init() and
pxa2xx_clock_init().
Remove the static declaration, which
Sergei Shtylyov sergei.shtyl...@cogentembedded.com writes:
+clocksources {
+#address-cells = 1;
+#size-cells = 1;
+ranges;
+
+pxa-timer@40a0 {
Just timer@40a0, please.
Hi Sergei,
I forgot that in the v2, sorry. I'll put it in
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 36
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Each pxa variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
...@kernel.org
Acked-by: Robert Jarzmik robert.jarz...@free.fr
--
Robert
--
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 read the FAQ at http
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
arch/arm/boot/dts/pxa27x.dtsi | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
pxa27x variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa27x description.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
---
Since v2
Sergei Shtylyov sergei.shtyl...@cogentembedded.com writes:
Hello.
On 2/7/2015 3:39 PM, Robert Jarzmik wrote:
+stuart: uart@4070 {
+clocks = pxa2xx_clks CLK_STUART;
+};
+
The ePAPR standard tells to call such nodes serial, not uart.
Good
When booting via DT, the default PXA devices must not have been probed
before, otherwise the augmented information from the device tree is
ignored.
This is the twin commit of commit 82ce44d104dc (ARM: pxa3xx: skip
default device initialization when booting via DT).
Signed-off-by: Robert Jarzmik
1 - 100 of 2627 matches
Mail list logo
