[PATCH] drm/exynos: remove unnecessary runtime pm interfaces

Exyno drm driver has no real hardware device, and runtime pm operation should be done by sub drivers. Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_drv.c | 29 - 1 file changed, 29 deletions(-) diff --git a/drivers/gpu/

[PATCH] drm/exynos: dsi: remove unnecessary pm interfaces

Exynos drm driver is a single driver so pm operation for kms drivers should be done by connector->dpms at top level driver. If kms driver has its own pm interfaces, single driver model would be broken so this patch removes unnecessary pm interfaces from dsi driver. Signed-off-by: Inki Dae Signed

[PATCH 4/5] drm/exynos: fix comment to exynos_drm_device_subdrv_prove call

subdrv_probe callback of virtual display driver will be called by exynos_drm_device_subdrv_probe() to create crtc and encoder/connector for virtual display driver. So it fixes comments to exynos_drm_device_subdrv probe call. Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/d

[PATCH 1/5] drm/exynos: modify goto labels to meaningful names

Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos_drm_drv.c | 55 +++ 1 file changed, 27 insertions(+), 28 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c index 2d27ba2..b3ba043 100644 --- a/driver

[PATCH 5/5] drm/exynos: separate dpi from fimd

From: Andrzej Hajda The patch separates dpi related routines from fimd. Changelog v2: - Rename ctx->dpi to ctx->display Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos_drm_dpi.c | 40 +-- drivers/gpu/drm/exynos/exynos_drm_drv.h | 15 ++--

[PATCH 2/5] drm/exynos: add component framework support

This patch adds component framework support to resolve the probe order issue. Until now, exynos drm had used codes specific to exynos drm to resolve that issue so with this patch, the specific codes are removed. Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos_dp_core.c | 45 +++--

[PATCH 3/5] drm/exynos: dpi: fix hotplug fail issue

When connector is created, if connector->polled is DRM_CONNECTOR_POLL_CONNECT then drm_kms_helper_hotplug_event function isn't called at drm_helper_hpd_irq_event because the function will be called only in case of DRM_CONNECTOR_POLL_HPD. So this patch sets always DRM_CONNECTOR_POLL_HPD flag to con

[PATCH 0/5] drm/exynos: more cleanup with component framework

This patch series cleans up exynos drm framework and kms sub drivers using the component framework[1]. And also this separates super device support from previous cleanup patch series[2] for more discussion. So the patch series for super node support will be posted later. [1] http://lists.freedesk

Re: [RFC PATCH 05/14] ARM: dts: samsung-fimd: add I80 specific properties

Hi Laurent Thank you for the comment. On 04/17/2014 06:26 AM, Laurent Pinchart wrote: Hi YoungJun, Thank you for the patch. On Tuesday 15 April 2014 14:47:33 YoungJun Cho wrote: In case of using CPU interface panel, the relevant registers should be set. So this patch adds relevant dt binding

Re: [PATCH v2 1/3] ARM: EXYNOS: Map PMU address through DT

Hi Vikas, As you comment, I found the history of this patch in mailing list. It seems like that this patch stop the review. Besides, Pankaj posted same patch to support PMU as following: - https://lkml.org/lkml/2014/4/2/48 Do you have a plan to resend or not? because I need this patch to remove

Re: [PATCHv3 1/5] drm: exynos: hdmi: remove usage of struct s5p_hdmi_platform_data

Hi Tomasz, On 04/17/2014 12:12 AM, Tomasz Stanislawski wrote: This patch continues shift of DRM EXYNOS to DT-only configuration. The usage of the old structure for HDMI's platform data is removed. Signed-off-by: Tomasz Stanislawski --- drivers/gpu/drm/exynos/exynos_hdmi.c | 30

Re: [PATCH 01/27] ARM: EXYNOS: Add Exynos3250 SoC ID

Hi Tomasz, On 04/17/2014 12:53 AM, Tomasz Figa wrote: > Hi Chanwoo, > > On 14.04.2014 07:13, Chanwoo Choi wrote: >> On 04/11/2014 05:39 PM, Tomasz Figa wrote: >>> On 11.04.2014 08:32, Chanwoo Choi wrote: On 04/11/2014 10:46 AM, Olof Johansson wrote: > On Thu, Apr 10, 2014 at 06:37:12PM +

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

Hi Doug, On 16 April 2014 15:25, Doug Anderson wrote: > Simon, > > On Wed, Apr 16, 2014 at 1:50 PM, Simon Glass wrote: >>> +#define MAX_CTRL_READ_TRIES5 >>> +#define MAX_FET_ENABLE_TRIES 1000 >> >> Gosh that is a lot of tries - should we maybe give up sooner? > > That's actually a squash o

[PATCH v3 5/5] regulator: tps65090: Make FETs more reliable by adding retries

An issue was discovered with tps65090 where sometimes the FETs wouldn't actually turn on when requested (they would report overcurrent). The most problematic FET was the one used for the LCD backlight on the Samsung ARM Chromebook (FET1). Problems were especially prevalent when the device was plu

[PATCH v3 3/5] mfd: tps65090: Stop caching most registers

Nearly all of the registers in tps65090 combine control bits and status bits. Turn off caching of all registers except the select few that can be cached. In order to avoid adding more duplicate #defines, we also move some register offset definitions to the mfd driver (and resolve inconsistent nam

[PATCH v3 4/5] regulator: tps65090: Allow setting the overcurrent wait time

The tps65090 regulator allows you to specify how long you want it to wait before detecting an overcurrent condition. Allow specifying that through the device tree (or through platform data). Signed-off-by: Doug Anderson Signed-off-by: Simon Glass Signed-off-by: Michael Spang Signed-off-by: Sea

[PATCH v3 2/5] charger: tps65090: Allow charger module to be used when no irq

On the ARM Chromebook tps65090 has two masters: the AP (the main processor running linux) and the EC (the embedded controller). The AP is allowed to mess with FETs but the EC is in charge of charge control. The tps65090 interupt line is routed to both the AP and the EC, which can cause quite a he

[PATCH v3 0/5] Fixes for tps65090 for Samsung ARM Chromebook

These five patches bring tps65090 up to speed with what's currently in the Chromium OS kernel 3.8 tree and running on the Samsung ARM Chromebook. Changes were tested atop the current linux tree (v3.15-rc1). FET retries were tested on a machine with a known flaky tps65090. Since display isn't wor

[PATCH v3 1/5] mfd: tps65090: Don't tell child devices we have an IRQ if we don't

If we weren't given an interrupt we shouldn't tell child devices (like the tps65090 charger) that they have an interrupt. This is needed so that we can support polling mode in the tps65090 charger driver. See also (charger: tps65090: Allow charger module to be used when no irq). Signed-off-by: D

Re: [PATCH v2 4/5] regulator: tps65090: Allow setting the overcurrent wait time

Randy, On Wed, Apr 16, 2014 at 1:33 PM, Randy Dunlap wrote: > On 04/16/2014 11:25 AM, Doug Anderson wrote: >> diff --git a/drivers/regulator/tps65090-regulator.c >> b/drivers/regulator/tps65090-regulator.c >> index 2e92ef6..ca13a1a 100644 >> --- a/drivers/regulator/tps65090-regulator.c >> +++ b/

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

Mark, On Wed, Apr 16, 2014 at 2:54 PM, Mark Brown wrote: > On Wed, Apr 16, 2014 at 02:34:47PM -0700, Doug Anderson wrote: >> On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote: > >> > Please don't send new patches as replies in the middle of threads, it >> > makes it confusing trying to work out

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

On Wed, Apr 16, 2014 at 02:34:47PM -0700, Doug Anderson wrote: > On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote: > > Please don't send new patches as replies in the middle of threads, it > > makes it confusing trying to work out which versions of things should be > > applied. > I'm a little c

Re: [RFC PATCH v2 09/14] ARM: dts: s6e3fa0: add DT bindings

Hi YoungJun, Thank you for the patch. On Wednesday 16 April 2014 13:38:57 YoungJun Cho wrote: > This patch adds DT bindings for s6e3fa0 panel. > The bindings describes panel resources, display timings, delays > and physical size. > > Changelog v2: > - Adds unit address (commented by Sachin Kamat

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

Mark, On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote: > On Wed, Apr 16, 2014 at 11:25:24AM -0700, Doug Anderson wrote: >> An issue was discovered with tps65090 where sometimes the FETs >> wouldn't actually turn on when requested (they would report >> overcurrent). The most problematic FET was

Re: [RFC PATCH 05/14] ARM: dts: samsung-fimd: add I80 specific properties

Hi YoungJun, Thank you for the patch. On Tuesday 15 April 2014 14:47:33 YoungJun Cho wrote: > In case of using CPU interface panel, the relevant registers should be set. > So this patch adds relevant dt bindings. > > Signed-off-by: YoungJun Cho > Signed-off-by: Inki Dae > Signed-off-by: Kyungm

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

Simon, On Wed, Apr 16, 2014 at 1:50 PM, Simon Glass wrote: >> +#define MAX_CTRL_READ_TRIES5 >> +#define MAX_FET_ENABLE_TRIES 1000 > > Gosh that is a lot of tries - should we maybe give up sooner? That's actually a squash of a recent patch. See

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On Wednesday 16 April 2014 21:50:01 Mark Brown wrote: > On Wed, Apr 16, 2014 at 08:14:27PM +0200, Arnd Bergmann wrote: > > > This patch does a partial revert of 313367e7bfa by allowing these > > drivers on all samsung platforms except EXYNOS, so we can proceed > > with the multiplatform patches. >

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On Wed, Apr 16, 2014 at 08:14:27PM +0200, Arnd Bergmann wrote: > This patch does a partial revert of 313367e7bfa by allowing these > drivers on all samsung platforms except EXYNOS, so we can proceed > with the multiplatform patches. > If support for these drivers is actually needed on EXYNOS mach

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

On Wed, Apr 16, 2014 at 11:25:24AM -0700, Doug Anderson wrote: > An issue was discovered with tps65090 where sometimes the FETs > wouldn't actually turn on when requested (they would report > overcurrent). The most problematic FET was the one used for the LCD Please don't send new patches as repl

Re: [PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

Hi Doug, (take 2) On 16 April 2014 12:25, Doug Anderson wrote: > An issue was discovered with tps65090 where sometimes the FETs > wouldn't actually turn on when requested (they would report > overcurrent). The most problematic FET was the one used for the LCD > backlight on the Samsung ARM Chrom

Re: [PATCH v2 4/5] regulator: tps65090: Allow setting the overcurrent wait time

On 04/16/2014 11:25 AM, Doug Anderson wrote: > diff --git a/drivers/regulator/tps65090-regulator.c > b/drivers/regulator/tps65090-regulator.c > index 2e92ef6..ca13a1a 100644 > --- a/drivers/regulator/tps65090-regulator.c > +++ b/drivers/regulator/tps65090-regulator.c > @@ -28,15 +28,57 @@ > +/**

Re: [PATCH 1/3] mfd: tps65090: Allow charger module to be used when no irq

> >> >> On the ARM Chromebook tps65090 has two masters: the AP (the main > >> >> processor running linux) and the EC (the embedded controller). The AP > >> >> is allowed to mess with FETs but the EC is in charge of charge control. > >> >> > >> >> The tps65090 interupt line is routed to both the A

[PATCH v2 1/5] mfd: tps65090: Don't tell child devices we have an IRQ if we don't

If we weren't given an interrupt we shouldn't tell child devices (like the tps65090 charger) that they have an interrupt. This is needed so that we can support polling mode in the tps65090 charger driver. See also (charger: tps65090: Allow charger module to be used when no irq). Signed-off-by: D

[PATCH v2 5/5] regulator: tps65090: Make FETs more reliable by adding retries

An issue was discovered with tps65090 where sometimes the FETs wouldn't actually turn on when requested (they would report overcurrent). The most problematic FET was the one used for the LCD backlight on the Samsung ARM Chromebook (FET1). Problems were especially prevalent when the device was plu

[PATCH v2 4/5] regulator: tps65090: Allow setting the overcurrent wait time

The tps65090 regulator allows you to specify how long you want it to wait before detecting an overcurrent condition. Allow specifying that through the device tree (or through platform data). Signed-off-by: Doug Anderson Signed-off-by: Simon Glass Signed-off-by: Michael Spang Signed-off-by: Sea

Re: [PATCH 2/3] mfd: tps65090: Stop caching registers

Mark, On Wed, Apr 16, 2014 at 3:13 AM, Mark Brown wrote: > On Wed, Apr 16, 2014 at 10:59:22AM +0100, Lee Jones wrote: > >> > NOTE: the IRQnMASK and CG_CTRLn registers are the exception and could >> > be cached. If we find that we spend a lot of time reading those we >> > can turn on cache for ju

Re: [PATCH 3/3] regulator: tps65090: Make FETs more reliable

Mark, On Tue, Apr 15, 2014 at 3:52 PM, Mark Brown wrote: > On Tue, Apr 15, 2014 at 01:14:36PM -0700, Doug Anderson wrote: > >> Mitigate the problem by: >> * Allow setting the overcurrent wait time so devices with this problem >> can set it to the max. >> * Add retry logic on enables of FETs. >

[PATCH v2 3/5] mfd: tps65090: Stop caching most registers

Nearly all of the registers in tps65090 combine control bits and status bits. Turn off caching of all registers except the select few that can be cached. In order to avoid adding more duplicate #defines, we also move some register offset definitions to the mfd driver (and resolve inconsistent nam

[PATCH v2 0/5] Fixes for tps65090 for Samsung ARM Chromebook

These five patches bring tps65090 up to speed with what's currently in the Chromium OS kernel 3.8 tree and running on the Samsung ARM Chromebook. Changes were tested atop the current linux tree (v3.15-rc1). FET retries were tested on a machine with a known flaky tps65090. Since display isn't wor

[PATCH v2 2/5] charger: tps65090: Allow charger module to be used when no irq

On the ARM Chromebook tps65090 has two masters: the AP (the main processor running linux) and the EC (the embedded controller). The AP is allowed to mess with FETs but the EC is in charge of charge control. The tps65090 interupt line is routed to both the AP and the EC, which can cause quite a he

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On Wednesday 16 April 2014 16:58:43 Tomasz Figa wrote: > On 16.04.2014 16:55, Thomas Abraham wrote: > > On Wed, Apr 16, 2014 at 8:18 PM, Tomasz Figa wrote: > >> On 16.04.2014 16:31, Arnd Bergmann wrote: > >>> sparsemem is still not supported in multiplatform, but after I looked > >>> at it in mor

Re: [PATCH 1/3] mfd: tps65090: Allow charger module to be used when no irq

Lee, On Wed, Apr 16, 2014 at 9:26 AM, Lee Jones wrote: >> >> On the ARM Chromebook tps65090 has two masters: the AP (the main >> >> processor running linux) and the EC (the embedded controller). The AP >> >> is allowed to mess with FETs but the EC is in charge of charge control. >> >> >> >> The

Re: [PATCH Resend] ARM: EXYNOS: Map SYSRAM address through DT

Hi, Am Mittwoch, 16. April 2014, 16:35:36 schrieb Arnd Bergmann: > On Wednesday 16 April 2014 17:20:51 Sachin Kamat wrote: > > Instead of hardcoding the SYSRAM details for each SoC, > > pass this information through device tree (DT) and make > > the code SoC agnostic. > > > > Signed-off-by: Sachi

Re: [PATCH v2 2/6] PCI: tegra: use new OF interrupt mapping when possible

On Wed, Apr 16, 2014 at 10:20:45AM +0200, Lucas Stach wrote: > Am Dienstag, den 15.04.2014, 12:30 -0600 schrieb Bjorn Helgaas: > > On Tue, Apr 15, 2014 at 12:07:34PM +0200, Lucas Stach wrote: > > > Hi Bjorn, > > > > > > Am Freitag, den 04.04.2014, 10:55 -0600 schrieb Bjorn Helgaas: > > > > On Wed,

Re: [PATCH 1/3] mfd: tps65090: Allow charger module to be used when no irq

> >> On the ARM Chromebook tps65090 has two masters: the AP (the main > >> processor running linux) and the EC (the embedded controller). The AP > >> is allowed to mess with FETs but the EC is in charge of charge control. > >> > >> The tps65090 interupt line is routed to both the AP and the EC, wh

Re: [PATCH 01/27] ARM: EXYNOS: Add Exynos3250 SoC ID

Hi Chanwoo, On 14.04.2014 07:13, Chanwoo Choi wrote: On 04/11/2014 05:39 PM, Tomasz Figa wrote: On 11.04.2014 08:32, Chanwoo Choi wrote: On 04/11/2014 10:46 AM, Olof Johansson wrote: On Thu, Apr 10, 2014 at 06:37:12PM +0900, Chanwoo Choi wrote: diff --git a/arch/arm/plat-samsung/include/plat

Re: [PATCH 1/3] mfd: tps65090: Allow charger module to be used when no irq

Lee On Wed, Apr 16, 2014 at 2:52 AM, Lee Jones wrote: >> On the ARM Chromebook tps65090 has two masters: the AP (the main >> processor running linux) and the EC (the embedded controller). The AP >> is allowed to mess with FETs but the EC is in charge of charge control. >> >> The tps65090 interup

Re: [PATCH 4/5] exynos4-is: Remove requirement for "simple-bus" compatible

On Tue, Apr 15, 2014 at 12:34 PM, Sylwester Nawrocki wrote: > This patch makes the driver instantiating its child devices itself, > rather than relying on an OS to instantiate devices as children > of "simple-bus". This removes an incorrect usage of "simple-bus" > compatible. Good, but why can't

Re: [PATCH Resend] ARM: EXYNOS: Map SYSRAM address through DT

On Wed, Apr 16, 2014 at 6:50 AM, Sachin Kamat wrote: > Instead of hardcoding the SYSRAM details for each SoC, > pass this information through device tree (DT) and make > the code SoC agnostic. > > Signed-off-by: Sachin Kamat > --- > Rebased on latest linux-next. > --- > .../devicetree/bindings/a

[PATCHv3 4/5] drm: exynos: add compatibles for HDMI and Mixer chips and exynos4210 SoC

This patch add proper compatibles for Mixer and HDMI chip available on exynos4210 SoCs. Signed-off-by: Tomasz Stanislawski --- drivers/gpu/drm/exynos/exynos_hdmi.c |7 +++ drivers/gpu/drm/exynos/exynos_mixer.c |3 +++ 2 files changed, 10 insertions(+) diff --git a/drivers/gpu/drm/e

[PATCHv3 5/5] drm: exynos: hdmi: add support for pixel clock limitation

Adds support for limitation of maximal pixel clock of HDMI signal. This feature is needed on boards that contains lines or bridges with frequency limitations. Signed-off-by: Tomasz Stanislawski --- .../devicetree/bindings/video/exynos_hdmi.txt |4 drivers/gpu/drm/exynos/exynos_hdmi

[PATCHv3 3/5] drm: exynos: mixer: fix using usleep() in atomic context

This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to reset correctly. Signed-off-by: Tomasz Stanislawski ---

[PATCHv3 1/5] drm: exynos: hdmi: remove usage of struct s5p_hdmi_platform_data

This patch continues shift of DRM EXYNOS to DT-only configuration. The usage of the old structure for HDMI's platform data is removed. Signed-off-by: Tomasz Stanislawski --- drivers/gpu/drm/exynos/exynos_hdmi.c | 30 -- 1 file changed, 8 insertions(+), 22 deletions(

[PATCHv3 0/5] drm: exynos: update/fixes to HDMI driver

Hi everyone, This patchset adds 5 fixes/updates to EXYNOS DRM driver for HDMI subsystem. All comments are welcome. Regards, Tomasz Stanislawski Changelog: v3: * remove usage of s5p_hdmi_platform_data * return MODE_CLOCK_HIGH instead of MODE_CLOCK_BAD v2: * fix check with gpio_is_valid() * use

[PATCHv3 2/5] drm: exynos: hdmi: simplify extracting hpd-gpio from DT

This patch eliminates redundant checks while retrieving HPD gpio from DT during HDMI's probe(). Signed-off-by: Tomasz Stanislawski --- drivers/gpu/drm/exynos/exynos_hdmi.c |7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c b/driver

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

Hi Thomas, On 16.04.2014 16:55, Thomas Abraham wrote: On Wed, Apr 16, 2014 at 8:18 PM, Tomasz Figa wrote: On 16.04.2014 16:31, Arnd Bergmann wrote: On Wednesday 16 April 2014 15:51:29 Tomasz Figa wrote: On 15.04.2014 11:28, Sachin Kamat wrote: From: Arnd Bergmann This makes it possible

Re: [PATCH Resend] ARM: EXYNOS: Map SYSRAM address through DT

On Wednesday 16 April 2014 17:20:51 Sachin Kamat wrote: > Instead of hardcoding the SYSRAM details for each SoC, > pass this information through device tree (DT) and make > the code SoC agnostic. > > Signed-off-by: Sachin Kamat > --- > Rebased on latest linux-next. Thanks for sending this again.

Re: [PATCHv2 6/8] ARM: EXYNOS: Enter a15 lowpower mode for Exynos3250 based on Cortex-a7

Hi Chanwoo, On 15.04.2014 03:59, Chanwoo Choi wrote: This patch decide proper lowpower mode of either a15 or a9 according to own ID from Main ID register. Signed-off-by: Chanwoo Choi Acked-by: Kyungmin Park --- arch/arm/mach-exynos/hotplug.c | 16 +++- 1 file changed, 11 insert

Re: [PATCH 1/2] v4l: Add resolution change event.

Hi Laurent and Hans, Thank you for the review. On Wed, Apr 16, 2014 at 7:46 PM, Hans Verkuil wrote: > On 04/16/2014 04:09 PM, Laurent Pinchart wrote: >> Hi Arun, >> >> Thank you for the patch. >> On Wednesday 16 April 2014 18:29:21 Arun Kumar K wrote: >>> From: Pawel Osciak >>> >>> This event i

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On Wed, Apr 16, 2014 at 8:18 PM, Tomasz Figa wrote: > On 16.04.2014 16:31, Arnd Bergmann wrote: >> >> On Wednesday 16 April 2014 15:51:29 Tomasz Figa wrote: >>> >>> On 15.04.2014 11:28, Sachin Kamat wrote: From: Arnd Bergmann This makes it possible to enable the exynos platfor

Re: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver

Hi, On Wed, Apr 16, 2014 at 7:14 PM, Tomasz Figa wrote: > Hi Vivek, > > > On 15.04.2014 08:09, Vivek Gautam wrote: >> >> Hi Tomasz, >> >> >> On Thu, Apr 10, 2014 at 5:09 PM, Vivek Gautam >> wrote: >>> >>> On Wed, Apr 9, 2014 at 7:03 PM, Tomasz Figa wrote: On 09.04.2014 13:49, Vivek G

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On 16.04.2014 16:31, Arnd Bergmann wrote: On Wednesday 16 April 2014 15:51:29 Tomasz Figa wrote: On 15.04.2014 11:28, Sachin Kamat wrote: From: Arnd Bergmann This makes it possible to enable the exynos platform as part of a multiplatform kernel, in addition to keeping the single-platform Exyn

Re: [PATCH V4 5/5] usb-phy: samsung-usb3: Remove older phy-samsung-usb3 driver

Hi Richard, On Wed, Apr 16, 2014 at 7:03 PM, Richard Genoud wrote: > Hi Vivek, > > 2014-04-09 13:34 GMT+02:00 Vivek Gautam : >> Hi Tomasz, >> ' >> >> On Wed, Apr 9, 2014 at 4:43 PM, Tomasz Figa wrote: >>> Hi Vivek, >>> >> Thanks for reviewing the patch series. >> >>> >>> On 08.04.2014 16:36, Vi

Re: [PATCHv2 6/8] ARM: EXYNOS: Enter a15 lowpower mode for Exynos3250 based on Cortex-a7

Hi Tomasz, On Wed, Apr 16, 2014 at 11:35 PM, Tomasz Figa wrote: > Hi Chanwoo, > > > On 15.04.2014 03:59, Chanwoo Choi wrote: >> >> This patch decide proper lowpower mode of either a15 or a9 according to >> own ID >> from Main ID register. >> >> Signed-off-by: Chanwoo Choi >> Acked-by: Kyungmin P

[PATCH 2/7] drm/panel: add pre_enable routine to drm panel

Most of the panels need an init sequence as mentioned below: -- poweron LCD unit/LCD_EN -- start video data -- poweron LED unit/BL_EN With existing callbacks for drm panel, we cannot accomodate such panels, since only one callback, i.e "panel_enable" is supported. This patc

[PATCH 5/7] drm/exynos: dp: modify driver to support drm_panel

This patch attaches the dp connector to exynos_dp_panel, and adds calls to drm_panel functions to control panel power sequence. Signed-off-by: Ajay Kumar --- drivers/gpu/drm/exynos/Kconfig | 1 + drivers/gpu/drm/exynos/exynos_dp_core.c | 19 +++ drivers/gpu/drm/exynos/e

[PATCH 4/7] drm/exynos: add exynos_dp_panel driver registration to drm driver

Register exynos_dp_panel before the list of exynos crtcs and connectors are probed. This is needed because exynos_dp_panel should be registered to the drm_panel list via panel-exynos-dp probe, i.e much before exynos_dp_bind calls of_drm_find_panel(). Signed-off-by: Ajay Kumar --- drivers/gpu/dr

[PATCH 7/7] drm/bridge: ptn3460: add drm_panel controls

attach ptn3460 connector to drm_panel and support drm_panel routines, if a valid drm_panel object is passed to ptn3460_init. Signed-off-by: Ajay Kumar --- drivers/gpu/drm/bridge/Kconfig | 1 + drivers/gpu/drm/bridge/ptn3460.c| 17 - drivers/gpu/drm/exynos/exynos

[PATCH 0/7] drm: exynos: few patches to enhance bridge chip support

This series is based on exynos-drm-next-todo branch of Inki Dae's tree at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git This set of drm patches are needed to support bridge chips and eDP/LVDS panels with exynos_dp. For testing, I have used exynos5250-snow board along with a

[PATCH 6/7] drm/bridge: ptn3460: enable polling based detection

From: Rahul Sharma Add DRM_CONNECTOR_POLL_HPD to the set of connector flags while registering drm_connector for ptn3460. Signed-off-by: Rahul Sharma Signed-off-by: Ajay Kumar --- drivers/gpu/drm/bridge/ptn3460.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/bridge/ptn346

[PATCH 3/7] drm/panel: Add driver for exynos_dp based panels

This patch adds a simple driver to handle all the LCD and LED powerup/down routines needed to support eDP/eDP-LVDS panels supported on exynos boards. Most of the eDP/LVDS panels need this sequence for powerup: -- LCD unit powerup/LCD_EN -- video data on -- LED unit powerup/

[PATCH 1/7] drm/exynos: dp: support hotplug detection via GPIO

From: Andrew Bresticker Certain bridge chips use a GPIO to indicate the cable status instead of the I_DP_HPD pin. This adds an optional device-tree property, "samsung,hpd-gpio", to the exynos-dp controller which indicates that the specified GPIO should be used for hotplug detection. The GPIO is

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

On Wednesday 16 April 2014 15:51:29 Tomasz Figa wrote: > On 15.04.2014 11:28, Sachin Kamat wrote: > > From: Arnd Bergmann > > > > This makes it possible to enable the exynos platform as part of a > > multiplatform kernel, in addition to keeping the single-platform > > Exynos support. > > sparsemem

Re: [PATCHv2 5/8] ARM: EXYNOS: Support secondary CPU boot of Exynos3250

Hi Chanwoo, On 15.04.2014 03:59, Chanwoo Choi wrote: This patch fix the offset of CPU boot address and don't operate smc call of SMC_CMD_CPU1BOOT command for Exynos3250. Signed-off-by: Chanwoo Choi Acked-by: Kyungmin Park --- arch/arm/mach-exynos/firmware.c | 7 +-- 1 file changed, 5 i

Re: [PATCH 1/2] v4l: Add resolution change event.

On 04/16/2014 04:09 PM, Laurent Pinchart wrote: > Hi Arun, > > Thank you for the patch. > On Wednesday 16 April 2014 18:29:21 Arun Kumar K wrote: >> From: Pawel Osciak >> >> This event indicates that the decoder has reached a point in the stream, >> at which the resolution changes. The userspace

Re: [PATCH RFC 3/4] xhci: Tune PHY for the DWC3-Exynos host controller

Hi, On Tue, Apr 15, 2014 at 06:24:11PM +0530, Vivek Gautam wrote: > I had seen your patches in the mailing list, but i don't see any > updated version of these patches. > Are you planning to work on this above mentioned patch-series any time soon ? I'm sorry, I forgot this completely. I have not

Re: [PATCH 1/2] v4l: Add resolution change event.

Hi Arun, Thank you for the patch. On Wednesday 16 April 2014 18:29:21 Arun Kumar K wrote: > From: Pawel Osciak > > This event indicates that the decoder has reached a point in the stream, > at which the resolution changes. The userspace is expected to provide a new > set of CAPTURE buffers for t

Re: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support

Hi Sachin, On 15.04.2014 11:28, Sachin Kamat wrote: From: Arnd Bergmann This makes it possible to enable the exynos platform as part of a multiplatform kernel, in addition to keeping the single-platform Exynos support. sparsemem is currently not supported in multiplatform. Is this still true

Re: [PATCH v2 0/6] Further cleanup and enable multiplat build

Hi Sachin, On 15.04.2014 11:28, Sachin Kamat wrote: This series is based on latest linux-next and depends on the following patch: ARM: EXYNOS: Consolidate Kconfig entries http://article.gmane.org/gmane.linux.kernel.samsung-soc/28642 Changes since v2: Replaced patch 2, "ARM: EXYNOS: Staticize ex

Re: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver

Hi Vivek, On 15.04.2014 08:09, Vivek Gautam wrote: Hi Tomasz, On Thu, Apr 10, 2014 at 5:09 PM, Vivek Gautam wrote: On Wed, Apr 9, 2014 at 7:03 PM, Tomasz Figa wrote: On 09.04.2014 13:49, Vivek Gautam wrote: Hi, On Wed, Apr 9, 2014 at 4:36 PM, Tomasz Figa wrote: Hi Vivek, Please see

Re: [PATCH V4 5/5] usb-phy: samsung-usb3: Remove older phy-samsung-usb3 driver

Hi Vivek, 2014-04-09 13:34 GMT+02:00 Vivek Gautam : > Hi Tomasz, > ' > > On Wed, Apr 9, 2014 at 4:43 PM, Tomasz Figa wrote: >> Hi Vivek, >> > Thanks for reviewing the patch series. > >> >> On 08.04.2014 16:36, Vivek Gautam wrote: >>> >>> Removing this older USB 3.0 DRD controller PHY driver, sinc

Re: [PATCH] arm: dts: exynos4: add missing pinctrls for I2C controllers

Hi Tomasz, On 16.04.2014 14:40, Tomasz Stanislawski wrote: This patch adds missing pinctrls for I2C controllers 2-7. Signed-off-by: Tomasz Stanislawski --- arch/arm/boot/dts/exynos4.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arc

[PATCH 1/2] v4l: Add resolution change event.

From: Pawel Osciak This event indicates that the decoder has reached a point in the stream, at which the resolution changes. The userspace is expected to provide a new set of CAPTURE buffers for the new format before decoding can continue. Signed-off-by: Pawel Osciak Signed-off-by: Arun Kumar K

[PATCH 2/2] [media] s5p-mfc: Add support for resolution change event

From: Pawel Osciak When a resolution change point is reached, queue an event to signal the userspace that a new set of buffers is required before decoding can continue. Signed-off-by: Pawel Osciak Signed-off-by: Arun Kumar K --- drivers/media/platform/s5p-mfc/s5p_mfc.c |6 ++ driv

[PATCH] arm: dts: exynos4: add missing pinctrls for I2C controllers

This patch adds missing pinctrls for I2C controllers 2-7. Signed-off-by: Tomasz Stanislawski --- arch/arm/boot/dts/exynos4.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi index 0401f4d..288aa81 100644 --- a/

Re: [PATCH Resend] ARM: EXYNOS: Map SYSRAM address through DT

Hi, On 04/16/2014 08:50 PM, Sachin Kamat wrote: > Instead of hardcoding the SYSRAM details for each SoC, > pass this information through device tree (DT) and make > the code SoC agnostic. > > Signed-off-by: Sachin Kamat > --- > Rebased on latest linux-next. > --- > .../devicetree/bindings/arm/s

Re: [PATCH v2 2/3] ARM: EXYNOS: Add initial support of PMU for Exynos5260

Hi Vikas, On 16.04.2014 07:34, Vikas Sajjan wrote: Hi Tomasz, On Wed, Apr 16, 2014 at 12:04 AM, Tomasz Figa wrote: Hi Vikas, On 17.03.2014 14:09, Vikas Sajjan wrote: Adds PMU support of PMU for Exynos5260. Suspend-to-RAM can be built on top this. Signed-off-by: Pankaj Dubey Signed-off-b

Re: [PATCH Resend 3/3] ARM: EXYNOS: Map SYSRAM address through DT

Hi Chanwoo, On 16 April 2014 16:36, Chanwoo Choi wrote: > Hi Sachin, > > I want to use this patch to remove static SYSRAM memory mapping for > Exynos3250. > But this patch has conflict on 3.15-rc1 base. > Do you have a plan to resend this patch? Rebased and resent (CC'd you). Please let me have

[PATCH Resend] ARM: EXYNOS: Map SYSRAM address through DT

Instead of hardcoding the SYSRAM details for each SoC, pass this information through device tree (DT) and make the code SoC agnostic. Signed-off-by: Sachin Kamat --- Rebased on latest linux-next. --- .../devicetree/bindings/arm/samsung-boards.txt | 11 +++ arch/arm/boot/dts/exynos4210-univ

Re: [PATCHv3 2/2] iio: devicetree: Add DT binding documentation for Exynos3250 ADC

Hi Chanwoo, On 16.04.2014 12:11, Chanwoo Choi wrote: This patch add DT binding documentation for Exynos3250 ADC IP. Exynos3250 has special clock ('sclk_tsadc') for ADC which provide clock to internal ADC. Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala Cc: R

Re: [PATCH Resend 3/3] ARM: EXYNOS: Map SYSRAM address through DT

Hi Sachin, I want to use this patch to remove static SYSRAM memory mapping for Exynos3250. But this patch has conflict on 3.15-rc1 base. Do you have a plan to resend this patch? Thanks, Chanwoo Choi On 03/19/2014 07:25 PM, Sachin Kamat wrote: > Instead of hardcoding the SYSRAM details for each S

Re: [PATCHv3 1/2] iio: adc: exynos_adc: Control special clock of ADC to support Exynos3250 ADC

Hi Chanwoo, On 16.04.2014 12:11, Chanwoo Choi wrote: This patch control special clock for ADC in Exynos series's FSYS block. If special clock of ADC is registerd on clock list of common clk framework, Exynos ADC drvier have to control this clock. Exynos3250/Exynos4/Exynos5 has 'adc' clock as fo

Re: [PATCHv2] pinctrl: exynos: Add driver data for Exynos3250

Hi Linus Walleij, I sent this patch with minor modification. Any comment of this patch? Best Regards, Chanwoo Choi On 04/14/2014 10:45 AM, Chanwoo Choi wrote: > From: Tomasz Figa > > This patch adds driver data (bank list and EINT layout) for Exynos3250 > to pinctrl-exynos driver. Exynos3250 i

Re: [PATCH 2/3] mfd: tps65090: Stop caching registers

On Wed, Apr 16, 2014 at 10:59:22AM +0100, Lee Jones wrote: > > NOTE: the IRQnMASK and CG_CTRLn registers are the exception and could > > be cached. If we find that we spend a lot of time reading those we > > can turn on cache for just those registers. > > -static bool is_volatile_reg(struct devi

[PATCHv3 2/2] iio: devicetree: Add DT binding documentation for Exynos3250 ADC

This patch add DT binding documentation for Exynos3250 ADC IP. Exynos3250 has special clock ('sclk_tsadc') for ADC which provide clock to internal ADC. Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala Cc: Randy Dunlap Cc: Kukjin Kim Cc: Naveen Krishna Chatradh

[PATCHv3 0/2] iio: adc: exynos_adc: Support Exynos3250 ADC

This patchset support Exynos3250 ADC (Analog Digital Converter) because Exynos3250 has additional special clock for ADC IP. Changes from v2: - Check return value of clock function to deal with error exception - Fix minor coding style to improve readability Changes from v1: - Add new "samsung,exyn

[PATCHv3 1/2] iio: adc: exynos_adc: Control special clock of ADC to support Exynos3250 ADC

This patch control special clock for ADC in Exynos series's FSYS block. If special clock of ADC is registerd on clock list of common clk framework, Exynos ADC drvier have to control this clock. Exynos3250/Exynos4/Exynos5 has 'adc' clock as following: - 'adc' clock: bus clock for ADC Exynos3250 ha

Re: [PATCH 2/3] mfd: tps65090: Stop caching registers

> Nearly all of the registers in tps65090 combine control bits and > status bits. Turn off caching of registers so that we can read status > bits reliably. > > NOTE: the IRQnMASK and CG_CTRLn registers are the exception and could > be cached. If we find that we spend a lot of time reading those

Re: [PATCH 1/3] mfd: tps65090: Allow charger module to be used when no irq

> On the ARM Chromebook tps65090 has two masters: the AP (the main > processor running linux) and the EC (the embedded controller). The AP > is allowed to mess with FETs but the EC is in charge of charge control. > > The tps65090 interupt line is routed to both the AP and the EC, which > can caus

Re: [PATCH 1/3] clocksource: exynos_mct: Fix stall after CPU hotplugging

On Wed, 16 Apr 2014, Krzysztof Kozlowski wrote: > On wto, 2014-04-15 at 18:20 +0200, Thomas Gleixner wrote: > > Here is a complete solution to the problem. We really want the drivers > > to be fast and clean and not work around such issues. > > > > I'm quite happy that I kept the 'force' argument

  1   2   >