This is to let you know that the migration of lists.linaro.org has been
successfully completed.
As per the email I sent on Wednesday, it may take some time for the new
address of the server to be seen by your computer. You can check this by
trying to connect to the web site:
http://lists.linaro.org/
If you are able to connect and you do not get an error, this means you are
connecting to the new server and you can send email to the lists.
If you experience any problems after the weekend and you find that you
still cannot connect to the server, please reply to this email to let us
know.
Regards
Philip
IT Services Manager
Linaro
== Ulf Hansson ==
=== Highlights ===
General:
* Last week spent at Linaro Connect Hong Kong. A great week!
Storage:
* Reviewing patches on mmc-list.
* Discussing sent patchset to enable runtime pm support for mmc/sd block device.
* Rework parts of the HS200 and SDR104 support in the mmc protocol
layer. First part for tuning sequence done, patch will be pushed to
mmc-list shortly.
Clk:
* Preparing patchset for upstreaming patches that will add support for
abx500 clocks.
* Preparing patchset to update different driver's clk support used by ux500.
* Resent patches for clk_set_parent fixup and for disable unprepared
clocks at late init.
* Diving into discussion around doing DVFS through the clock API.
Reviewing related patches.
=== Plans ===
Storage:
* Speed up work around the mmc power management blueprint so we can
finalize this work as soon as possible.
* Push patches for mmci host driver, to support UHS cards/HS200, CMD23.
* Push patches for mmci host driver to extend the power management
support. Context save/restore are for example missing.
* Push patches for mmci host driver to add support for new STE 8540 variant.
Clk:
* Optimizations and bug fixes for ux500 clk implementations.
* Send RFC/PATCH for DVFS clock type used by ux500.
* Follow up on previously sent patchset.
=== Issues ===
* None.
On Fri, Mar 15, 2013 at 11:54 AM, Chao Xie <xiechao.mail(a)gmail.com> wrote:
> hi
> It may be a old topic.
> Now the cpufreq governors will sample for system work load. The
> schduler knows about the current workload of each cores. So why not
> make use of it? The sampling need take some time, so when the cpufreq
> increase the frequency , the system has been busy for a period of
> time. Making use of the schduler information can reduce time spending
> at sampling.
Hi Chao,
I am working for Linaro Power Management Working Group and we know
about this problem or solution. We have a dedicated blueprint towards this
goal:
https://blueprints.launchpad.net/linaro-big-little-system/+spec/sched-coope…
--
viresh
Replaces the "platform_get_resource() for IORESOURCE_IRQ" with
platform_get_resource_byname().
Both in exynos4 and exynos5, FIMD IP has 3 interrupts in the order: "fifo",
"vsync", and "lcd_sys".
But The FIMD driver expects the "vsync" interrupt to be mentioned as the
1st parameter in the FIMD DT node. So to meet this expectation of the
driver, the FIMD DT node was forced to be made by keeping "vsync" as the
1st paramter.
For example in exynos4, the FIMD DT node has interrupt numbers
mentioned as <11, 1> <11, 0> <11, 2> keeping "vsync" as the 1st paramter.
This patch fixes the above mentioned "hack" of re-ordering of the
FIMD interrupt numbers by getting interrupt resource of FIMD by using
platform_get_resource_byname().
Signed-off-by: Vikas Sajjan <vikas.sajjan(a)linaro.org>
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
index 1ea173a..cd79d38 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
@@ -945,7 +945,7 @@ static int fimd_probe(struct platform_device *pdev)
return -ENXIO;
}
- res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
+ res = platform_get_resource_byname(pdev, IORESOURCE_IRQ, "vsync");
if (!res) {
dev_err(dev, "irq request failed.\n");
return -ENXIO;
--
1.7.9.5
This patch series adds support for DRM FIMD DT for Exynos4 DT Machines,
specifically for Exynos4412 SoC.
changes since v6:
- addressed comments and added interrupt-names = "fifo", "vsync", "lcd_sys"
in exynos4.dtsi and re-ordered the interrupt numbering to match the order in
interrupt combiner IP as suggested by Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com>.
changes since v5:
- renamed the fimd binding documentation file name as "samsung-fimd.txt",
since it not only talks about exynos display controller but also about
previous samsung display controllers.
- rephrased an abmigious statement about the interrupt combiner in the
fimd binding documentation as pointed out by
Sachin Kamat <sachin.kamat(a)linaro.org>
changes since v4:
- moved the fimd binding documentation to Documentation/devicetree/bindings/video/
as suggested by Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com>
- added more fimd compatiblity strings in fimd documentation as
discussed at https://patchwork.kernel.org/patch/2144861/ with
Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com> and
Tomasz Figa <tomasz.figa(a)gmail.com>
- modified compatible string for exynos4 fimd as "exynos4210-fimd"
exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible
value should be named after first specific SoC model in which this
particular IP version was included as discussed at
https://patchwork.kernel.org/patch/2144861/
- documented more about the interrupt combiner and their order as
suggested by Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com>
changes since v3:
- rebased on
http://git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git;a=shortlo…
changes since v2:
- added alias to 'fimd@11c00000' node
(reported by: Rahul Sharma <r.sh.open(a)gmail.com>)
- removed 'lcd0_data' node as there was already a similar node lcd_data24
(reported by: Jingoo Han <jg1.han(a)samsung.com>
- replaced spaces with tabs in display-timing node
changes since v1:
- added new patch to add FIMD DT binding Documentation
- removed patch enabling SAMSUNG_DEV_BACKLIGHT and SAMSUNG_DEV_PMW
for mach-exynos4 DT
- added 'status' property to fimd DT node
Is based on branch "for-next-next"
http://git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git;a=shortlo…
Sachin Kamat (1):
ARM: dts: Add lcd pinctrl node entries for EXYNOS4412 SoC
Vikas Sajjan (4):
ARM: dts: Add FIMD node to exynos4
ARM: dts: Add FIMD node and display timing node to
exynos4412-origen.dts
ARM: dts: Add FIMD AUXDATA node entry for exynos4 DT
ARM: dts: Add FIMD DT binding Documentation
.../devicetree/bindings/video/samsung-fimd.txt | 58 ++++++++++++++++++++
arch/arm/boot/dts/exynos4.dtsi | 8 +++
arch/arm/boot/dts/exynos4412-origen.dts | 22 ++++++++
arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 14 +++++
arch/arm/mach-exynos/mach-exynos4-dt.c | 2 +
5 files changed, 104 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/samsung-fimd.txt
--
1.7.9.5
Hello
You are receiving this email because you are subscribed to one or more
mailing lists provided by the lists.linaro.org server.
IT Services are announcing planned maintenance for this server scheduled
for *Friday 15th March 2013, starting at 2pm GMT*. The purpose of the work
is to move the service to another server. There will be some disruption
during this maintenance.
In order to ensure that you do not accidentally try to use the service
while it is being moved, the current server will be shut down at 2pm.
A further email will be sent on Friday afternoon to confirm that the
migration of the service is completed. However, due to the way servers are
found, it may take a while before your computer is able to connect to the
relocated service.
After the old server has been shut down, email sent to any of the lists
will be queued, but it is possible that the sending server will still
trying to deliver the email to the old server rather than the new one when
it is started.
It is therefore *strongly* recommended that you do not send any email to an
@lists.linaro.org email address until you can connect to the new service,
which you will be able to test by trying to use a web browser to connect to
http://lists.linaro.org after you receive the email confirming that the
migration has been completed. Since the old service will be shut down, if
you are able to connect, you can be sure you have connected to the new
service.
If by Monday you are still unable to connect to the service or you are not
able to send email to an @lists.linaro.org email address, please send an
email to its(a)linaro.org.
Thank you.
Regards
Philip
IT Services Manager
Linaro
The only difference between schedule_delayed_work[_on]() and
queue_delayed_work[_on]() is the workqueue, work is scheduled on. We may need to
modify the delay for works queued with schedule_delayed_work[_on]() calls and
thus adding these helpers.
First users of these new helpers is cpufreq governors which need to modify the
delay for its works.
Cc: Tejun Heo <tj(a)kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org>
---
include/linux/workqueue.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/linux/workqueue.h b/include/linux/workqueue.h
index 2b58905..864c2b3 100644
--- a/include/linux/workqueue.h
+++ b/include/linux/workqueue.h
@@ -412,6 +412,7 @@ extern bool schedule_delayed_work_on(int cpu, struct delayed_work *work,
extern bool schedule_delayed_work(struct delayed_work *work,
unsigned long delay);
extern int schedule_on_each_cpu(work_func_t func);
+
extern int keventd_up(void);
int execute_in_process_context(work_func_t fn, struct execute_work *);
@@ -465,6 +466,11 @@ static inline long work_on_cpu(unsigned int cpu, long (*fn)(void *), void *arg)
long work_on_cpu(unsigned int cpu, long (*fn)(void *), void *arg);
#endif /* CONFIG_SMP */
+#define mod_scheduled_delayed_work_on(cpu, dwork, delay) \
+ mod_delayed_work_on(cpu, system_wq, dwork, delay)
+#define mod_scheduled_delayed_work(dwork, delay) \
+ mod_delayed_work(system_wq, dwork, delay)
+
#ifdef CONFIG_FREEZER
extern void freeze_workqueues_begin(void);
extern bool freeze_workqueues_busy(void);
--
1.7.12.rc2.18.g61b472e
When a cpu goes to a deep idle state where its local timer is shutdown,
it notifies the time framework to use the broadcast timer instead.
Unfortunately, the broadcast device could wake up any CPU, including an
idle one which is not concerned by the wake up at all.
This implies, in the worst case, an idle CPU will wake up to send an IPI
to another idle cpu.
This patch solves this by setting the irq affinity to the cpu concerned
by the nearest timer event, by this way, the CPU which is wake up is
guarantee to be the one concerned by the next event and we are safe with
unnecessary wakeup for another idle CPU.
As the irq affinity is not supported by all the archs, a flag is needed
to specify which clocksource can handle it.
Daniel Lezcano (3):
time : pass broadcast parameter
time : set broadcast irq affinity
ARM: nomadik: add dynamic irq flag to the timer
Viresh Kumar (1):
ARM: timer-sp: Set dynamic irq affinity
arch/arm/common/timer-sp.c | 3 ++-
drivers/clocksource/nomadik-mtu.c | 3 ++-
include/linux/clockchips.h | 1 +
kernel/time/tick-broadcast.c | 40 +++++++++++++++++++++++++++++--------
4 files changed, 37 insertions(+), 10 deletions(-)
--
1.7.9.5
Add display-timing node parsing to drm fimd and depends on
the display helper patchset at
http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html
changes since v12:
- Added dependency of "OF" for exynos drm fimd as suggested
by Inki Dae <inki.dae(a)samsung.com>
changes since v11:
- Oops, there was a build error, fixed that.
changes since v10:
- abandoned the pinctrl patch, as commented by Linus Walleij
<linus.walleij(a)linaro.org>
- added new patch to enable the OF_VIDEOMODE and FB_MODE_HELPERS for
EXYNOS DRM FIMD.
changes since v9:
- replaced IS_ERR_OR_NULL() with IS_ERR(), since IS_ERR_OR_NULL()
will be depreciated, as discussed at
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140543.h…http://www.mail-archive.com/linux-omap@vger.kernel.org/msg78030.html
changes since v8:
- replaced IS_ERR() with IS_ERR_OR_NULL(),
because devm_pinctrl_get_select_default can return NULL,
If CONFIG_PINCTRL is disabled.
- modified the error log, such that it shall NOT cross 80 column.
- added Acked-by.
changes since v7:
- addressed comments from Joonyoung Shim <jy0922.shim(a)samsung.com>
to remove a unnecessary variable.
changes since v6:
addressed comments from Inki Dae <inki.dae(a)samsung.com> to
separated out the pinctrl functionality and made a separate patch.
changes since v5:
- addressed comments from Inki Dae <inki.dae(a)samsung.com>,
to remove the allocation of 'fbmode' and replaced
'-1'in "of_get_fb_videomode(dev->of_node, fbmode, -1)" with
OF_USE_NATIVE_MODE.
changes since v4:
- addressed comments from Paul Menzel
<paulepanter(a)users.sourceforge.net>, to modify the commit message
changes since v3:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>, to modify
the return values and print messages.
changes since v2:
- moved 'devm_pinctrl_get_select_default' function call under
'if (pdev->dev.of_node)', this makes NON-DT code unchanged.
(reported by: Rahul Sharma <r.sh.open(a)gmail.com>)
changes since v1:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>
Vikas Sajjan (2):
video: drm: exynos: Add display-timing node parsing using video
helper function
drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm
fimd
drivers/gpu/drm/exynos/Kconfig | 4 +++-
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 24 ++++++++++++++++++++----
2 files changed, 23 insertions(+), 5 deletions(-)
--
1.7.9.5
Hi,
I'm developing a baremetal hypervisor for Cortex-A15 and I'm using
Arndale Board as a reference platform. ATM, I'm working on running
Linaro 13.02 as a guest.
I've noticed that `arch/arm/kernel/arch_timer.c` Linux prefers the
virtual IRQ timers (CNTV_):
static bool arch_timer_use_virtual = false;
as a timer source and I'm wondering if there's a reason for this. Is
it even possible for virtual timer to be available, while physical one
is not? I don't think so. So why would Linux want to default to
virtual one instead of physical one, especially in the situation when
it was started in SVC mode and HYP is not accessible to it?
>From Hypervisor point of view, it seems natural that guest does not
care about virtualization stuff, does not try to be smarter than
necessary and simply uses physical timer (PL1) all the time.
It's hypervisor's job to trap guest accesses to physical timer (CNTP_)
and route them to virtual timer (CNTV_) so virtual offset (CNTVOFF)
value can be easily switched (again, by hypervisor, not the guest)
when handling multiple guests, to correctly handle virtual time for
them. In opposite direction the hardware virtual timer irq is just
renumbered to appear to guest as a physical one.
While emulating the CNTVOFF and CNTV_ is entirely possible too and
required for completeness, it seems like additional work for no
apparent reason. So I wanted to clarify this. Maybe there is something
that I don't understand or I misread the intentions described in
reference manual.
--
Dawid Ciężarkiewicz
B-Labs. http://b-labs.com/
