This patch series adds support for DRM FIMD DT for Exynos4 DT Machines,
specifically for Exynos4412 SoC.
changes since v10:
- addressed comments from Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com>
changes since v9:
- dropped the patch "ARM: dts: Add lcd pinctrl node entries for EXYNOS4412 SoC"
as the gpios in the newly added nodes "lcd_en" and "lcd_sync" in this patch
were already PULLed high by existing "lcd_clk" node.
- addressed comments from Sylwester Nawrocki <sylvester.nawrocki(a)gmail.com>
and Thomas Abraham <thomas.abraham(a)linaro.org>
changes since v8:
- addressed comments to add missing documentation for clock and clock-names
properties as pointed out by Sachin Kamat <sachin.kamat(a)linaro.org>
changes since v7:
- rebased to kgene's "for-next"
- Migrated to Common Clock Framework
- removed the patch "ARM: dts: Add FIMD AUXDATA node entry for exynos4 DT",
as migration to Common Clock Framework will NOT need this.
- addressed the comments raised by Sachin Kamat <sachin.kamat(a)linaro.org>
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 kgene's "for-next"
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h…
Vikas Sajjan (3):
ARM: dts: Add FIMD node to exynos4
ARM: dts: Add FIMD node and display timing node to
exynos4412-origen.dts
ARM: dts: Add FIMD DT binding Documentation
.../devicetree/bindings/video/samsung-fimd.txt | 65 ++++++++++++++++++++
arch/arm/boot/dts/exynos4.dtsi | 12 ++++
arch/arm/boot/dts/exynos4412-origen.dts | 21 +++++++
3 files changed, 98 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/samsung-fimd.txt
--
1.7.9.5
The patch series adds a much-missed support for debugfs to dma-buf framework.
Based on the feedback received on v1 of this patch series, support is also
added to allow exporters to provide name-strings that will prove useful
while debugging.
Some more magic can be added for more advanced debugging, but we'll leave that
for the time being.
Best regards,
~Sumit.
---
changes since v2: (based on review comments from Laurent Pinchart)
- reordered functions to avoid forward declaration
- added __exitcall for dma_buf_deinit()
changes since v1:
- added patch to replace dma_buf_export() with dma_buf_export_named(), per
suggestion from Daniel Vetter.
- fixes on init and warnings as reported and corrected by Dave Airlie.
- added locking while walking attachment list - reported by Daniel Vetter.
Sumit Semwal (2):
dma-buf: replace dma_buf_export() with dma_buf_export_named()
dma-buf: Add debugfs support
Documentation/dma-buf-sharing.txt | 13 ++-
drivers/base/dma-buf.c | 170 ++++++++++++++++++++++++++++++++++++-
include/linux/dma-buf.h | 16 +++-
3 files changed, 190 insertions(+), 9 deletions(-)
--
1.7.10.4
=== Highlights ===
* Implemented file backed volatile ranges ontop of Minchan's anonymous
volatile ranges patch, sent out to lkml for comments.
* Had some discussions with Minchan on the issues regarding the various
potential interfaces and how they might mix.
* Had some discussions with community folks on how to expose sched_clock
timestamps to userland for perf, and how I think its a bad idea.
* Tglx pulled in the first half of my 3.10 patch queue
* Reviewed Serban's binder patches a few times before he sent them to
lkml/arve
* Worked with Viresh to resolve a quirk with merge_config.sh, sent the
patch upstream.
* Reviewed blueprints and sent out Android Upstreaming status email.
* Got pinged by some stranger, Zach Pfeffub(or something like that) on
tips for upstreaming a hardware driver from AOSP
* Did an interview.
* Got a chromebook & started to play around with it a bit.
=== Plans ===
* Continue focus on volatile range work in prep for lsf-mm
* Still need to work on earlysuspend blog post
* Double around on timekeeping lock hold-time patch queue
* Likely more discussion on perf/sched_clock() interfaces
=== Issues ===
* Oh man. This cold just doesn't go away! This week was a foggy blur
(how is it already friday!?).
sched_domains_numa_distance is written as sched_domains_nume_distance inside one
of the comments. Fix it.
Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org>
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 286066e..2e0de12 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6251,7 +6251,7 @@ static void sched_init_numa(void)
* 'level' contains the number of unique distances, excluding the
* identity distance node_distance(i,i).
*
- * The sched_domains_nume_distance[] array includes the actual distance
+ * The sched_domains_numa_distance[] array includes the actual distance
* numbers.
*/
--
1.7.12.rc2.18.g61b472e
Hello,
With the latest linaro-kernel release (ll_20130321.0), LPAE seems to be
broken on Versatile Express (and possible other targets too) as it hangs
very early in the boot process when enabled. KVM builds depend on LPAE, so
it would be good to see this fixed on next release.
Attached you can find said fix.
Regards.
Hi all,
Here are a few updates from the Android dev tree. Thanks to Arve Hjønnevåg
for the code, and John Stultz for actually preparing commits for
submission.
Unless there are objections, I'll push these updates to linux-pstore.git.
Thanks!
Anton