Hi,
On 02/26/2013 07:38 AM, Chen Gang wrote:
于 2013年02月16日 19:39, Kyungmin Park 写道:
You can find it at recent patch from Arnd.
excuse me, could you please provide more information about it ?
I have checked 2 tags:
the next-20130225 tag in
Only cortex-a9 based samsung platforms have l2x0 cache controller. Hence check
the same before restoring the cache in resume.
This is needed for single kernel image.
Signed-off-by: Inderpal Singh inderpal.si...@linaro.org
---
changes in v2:
- check processor midr instead of checking all
On Tue, Feb 26, 2013 at 03:26:53PM +0530, Inderpal Singh wrote:
Only cortex-a9 based samsung platforms have l2x0 cache controller. Hence check
the same before restoring the cache in resume.
Why is this patch soo complicated? Can't you read the CPUs MIDR register
from assembly code?
--
To
This patch series adds support for FIMD DT for Exynos5 DT Machines
Adds display timing node for smdk5250 board.
This series is rebased on branch
http://git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git;a=shortlog;h=refs/heads/for-next
Leela Krishna Amudala (3):
ARM: dts: Add FIMD
Add display timing node to exynos5250-smdk5250.dts
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
---
arch/arm/boot/dts/exynos5250-smdk5250.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts
Adds the FIMD AUXDATA entry for Exynos5
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
---
arch/arm/mach-exynos/include/mach/map.h | 1 +
arch/arm/mach-exynos/mach-exynos5-dt.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/arm/mach-exynos/include/mach/map.h
This adds common FIMD device node for all Exynos5 SoCs.
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250.dtsi
index
On 26 February 2013 15:32, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, Feb 26, 2013 at 03:26:53PM +0530, Inderpal Singh wrote:
Only cortex-a9 based samsung platforms have l2x0 cache controller. Hence
check
the same before restoring the cache in resume.
Why is this patch
On Tue, Feb 26, 2013 at 04:46:01PM +0530, Inderpal Singh wrote:
On 26 February 2013 15:32, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, Feb 26, 2013 at 03:26:53PM +0530, Inderpal Singh wrote:
Only cortex-a9 based samsung platforms have l2x0 cache controller. Hence
check
Exynos hdmi driver is using drm_display_mode for setting timing values
for a supported resolution. Conversion to fb_videomode and then comparing
with the mixer/hdmi/phy limits is not required. Instead, drm_display_mode
fields cane be directly compared.
This patch is dependent on
Currently, mode_fixup code doesn't consider the limitations of mixer as it
is implemented inside the hdmi driver. Following fix, moves the mode_fixup
to common drm hdmi driver. To check the mode support, it calls both, mixer
and hdmi check_timing callbacks for a given resolution mode.
This patch
Now I checked HDMI failed at:
drivers/media/platform/s5p-tv/hdmi_drv.c: 912 line
adapter = i2c_get_adapter(pdata-hdmiphy_bus);
if (adapter == NULL) {
dev_err(dev, hdmiphy adapter request failed\n);
ret = -ENXIO;
goto fail_vdev;
On Tue, Feb 26, 2013 at 7:16 AM, Rahul Sharma rahul.sha...@samsung.com wrote:
Exynos hdmi driver is using drm_display_mode for setting timing values
for a supported resolution. Conversion to fb_videomode and then comparing
with the mixer/hdmi/phy limits is not required. Instead,
Hi Lonsn,
On 02/26/2013 01:59 PM, Lonsn wrote:
Now I checked HDMI failed at:
drivers/media/platform/s5p-tv/hdmi_drv.c: 912 line
adapter = i2c_get_adapter(pdata-hdmiphy_bus);
if (adapter == NULL) {
dev_err(dev, hdmiphy adapter request failed\n);
ret = -ENXIO;
On 02/26/2013 09:07 PM, Sylwester Nawrocki wrote:
Hi Lonsn,
On 02/26/2013 01:59 PM, Lonsn wrote:
Now I checked HDMI failed at:
drivers/media/platform/s5p-tv/hdmi_drv.c: 912 line
adapter = i2c_get_adapter(pdata-hdmiphy_bus);
if (adapter == NULL) {
dev_err(dev, hdmiphy adapter request failed\n);
On 02/22/2013 01:00 PM, Lonsn wrote:
Hi,
I have tested the kernel 3.8 with a SMDKV210 like board. But I failed
with dma-pl330 and HDMI driver.
For dma-pl330, kernel print:
dma-pl330 dma-pl330.0: PERIPH_ID 0x0, PCELL_ID 0x0 !
dma-pl330: probe of dma-pl330.0 failed with error -22
dma-pl330
On 02/26/2013 05:19 AM, Vikas Sajjan wrote:
ok thanks. Will modify the documentation as below.
compatible = samsung, exynos4-fimd; for Exynos4 SoCs
compatible = samsung, exynos5-fimd ; for Exynos5 SoCs
compatible = samsung, s3c64xx-fimd ; for S3C64XX SoCs
compatible = samsung, s3c24xx-fimd ;
On Tuesday 26 of February 2013 22:57:15 Sylwester Nawrocki wrote:
On 02/26/2013 05:19 AM, Vikas Sajjan wrote:
ok thanks. Will modify the documentation as below.
compatible = samsung, exynos4-fimd; for Exynos4 SoCs
compatible = samsung, exynos5-fimd ; for Exynos5 SoCs
compatible =
On 02/26/2013 11:11 PM, Tomasz Figa wrote:
We should stick to the rule that compatible value should be named after
first specific SoC model in which this particular IP version was included.
So this is what I would suggest:
compatible = samsung,s3c2443-fimd; // for S3C24XX SoCs
compatible =
Asorted fixes and enhancements for the recent redo of the s3c24xx
interrupt controllers.
The only real error that gets fixed is the handling of 0-hwirq as
parent_irq on s3c2412 in patch 2. No other of the s3c24xx platforms
uses the bit0 of the parent controller as parent_irq.
Heiko Stuebner (5):
Asorted fixes and enhancements for the recent redo of the s3c24xx
interrupt controllers.
The only real error that gets fixed is the handling of 0-hwirq as
parent_irq on s3c2412 in patch 2. No other of the s3c24xx platforms
uses the bit0 of the parent controller as parent_irq.
Heiko Stuebner (5):
The current parent_irq check checks for a value != 0. This does of course
not work when the parent irq sits in the bit 0 of the parent register.
This only affects the eint0 interrupt of the s3c2412.
To fix this behaviour, check for the presence of a parent_intc in the
structure. In an s3c24xx
The s3c24xx_init_irq function that was the base for all irq inits
is now only used to initialize the real s3c2410 irqs.
Therefore rename it and also move its declaration from plat/cpu.h
to common.h
The eint declaration is used by the vast majority of the SoCs and
gets therefore placed outside
It's not used anywhere else.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
arch/arm/mach-s3c24xx/irq.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-s3c24xx/irq.c b/arch/arm/mach-s3c24xx/irq.c
index ee47654..8bc2931 100644
---
This removes the dependency on static irq mappings for basic irq handling
and makes the s3c24xx entry-macro.S obsolete.
Also the interrupts of the second full interrupt controller on the s3c2416
are really handled now, which was forgotten when adding them.
The handling itself does the same as
Wolfram,
On Mon, Feb 11, 2013 at 4:48 PM, Doug Anderson diand...@chromium.org wrote:
This was suggested by Mark Brown in response to a patch for adding
this functionality only for the s3c2410 bus:
https://lkml.org/lkml/2012/11/20/681
I have also modified the i2c-pxa driver to use this new
于 2013年02月26日 17:50, Sylwester Nawrocki 写道:
No, the fix is not yet in linux-next. I has not been merged through the media
tree and it might take some time until it gets to Linus's tree now. You can
use
one of following patches to fix this build break:
Thanks Sean,
On Tue, Feb 26, 2013 at 10:55 PM, Sean Paul seanp...@chromium.org wrote:
On Tue, Feb 26, 2013 at 7:16 AM, Rahul Sharma rahul.sha...@samsung.com
wrote:
Exynos hdmi driver is using drm_display_mode for setting timing values
for a supported resolution. Conversion to fb_videomode
28 matches
Mail list logo
