Thanks Sean,
On Tue, Feb 26, 2013 at 11:33 PM, Sean Paul wrote:
> On Fri, Feb 22, 2013 at 8:32 AM, Rahul Sharma
> wrote:
>> Exynos5 is already using drm_display_mode for timings parameters. Exynos4
>> is also modifed to use the same. List of supported resolutions and
>> corresponding timings ar
Thanks Sean,
On Tue, Feb 26, 2013 at 10:55 PM, Sean Paul wrote:
> On Tue, Feb 26, 2013 at 7:16 AM, Rahul Sharma
> 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/
于 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:
>
> http://www.spinics.net/lists/linu
Wolfram,
On Mon, Feb 11, 2013 at 4:48 PM, Doug Anderson 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 functionality.
>
Hi,
On Fri, Feb 22, 2013 at 3:48 PM, Tushar Behera wrote:
> LDO3 and LDO8 are used for powering both device and host phy controllers.
> These regulators are not handled in USB host driver. Hence we get
> unexpected behaviour when the regulators are disabled elsewhere.
>
> It would be best to keep
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 the
It's not used anywhere else.
Signed-off-by: Heiko Stuebner
---
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
--- a/arch/arm/mach-s3c24xx/irq.c
+++ b/arc
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 any
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 inte
The check during the parent handling itself was wrong, as it should have
checked for parent_irq_data.
The interrupt controller structs always contain an irq_data array with 32
entries and the only possible error could be a parent_irq assignment of >31.
As this would point to outside the irq_data
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):
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 = "s
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
> > comp
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-fim
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 dma-pl33
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"
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 Fri, Feb 22, 2013 at 8:32 AM, Rahul Sharma wrote:
> Exynos5 is already using drm_display_mode for timings parameters. Exynos4
> is also modifed to use the same. List of supported resolutions and
> corresponding timings are removed which helps is enabling some extra
> resolutions. It also cleans
On Tue, Feb 26, 2013 at 7:16 AM, Rahul Sharma 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, drm_display_mode
> fields cane be dir
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;
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 i
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 https://patchwork.
On 26 February 2013 16:52, Russell King - ARM Linux
wrote:
> On Tue, Feb 26, 2013 at 04:46:01PM +0530, Inderpal Singh wrote:
>> On 26 February 2013 15:32, Russell King - ARM Linux
>> wrote:
>> > On Tue, Feb 26, 2013 at 03:26:53PM +0530, Inderpal Singh wrote:
>> >> Only cortex-a9 based samsung pla
On Tue, Feb 26, 2013 at 04:46:01PM +0530, Inderpal Singh wrote:
> On 26 February 2013 15:32, Russell King - ARM Linux
> 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
On 26 February 2013 15:32, Russell King - ARM Linux
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 soo complicated
Adds the FIMD AUXDATA entry for Exynos5
Signed-off-by: Leela Krishna Amudala
---
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
b/arch/arm/mach-exynos/include/m
This adds common FIMD device node for all Exynos5 SoCs.
Signed-off-by: Leela Krishna Amudala
---
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 3acf594..0ee4706 100644
--- a
Add display timing node to exynos5250-smdk5250.dts
Signed-off-by: Leela Krishna Amudala
---
arch/arm/boot/dts/exynos5250-smdk5250.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts
b/arch/arm/boot/dts/exynos5250-smdk5250.dts
index
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 nod
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 unsu
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
---
changes in v2:
- check processor midr instead of checking all soc ids as
sugges
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
> git://git.kernel.org/pub/scm/li
33 matches
Mail list logo
