Re: [PATCH v3] clk: s3c2410: removed unneeded variable in s3c24xx_clkout_set_parent

On 30/11/15 11:08, Mutharaju, Prasanna (P.) wrote: > From: Prasanna Karthik > > Remove unneeded variable used to store return value. > > Signed-off-by: Prasanna Karthik Patch applied, thanks. -- To unsubscribe from this list: send the line

[GIT PULL] clk/samsung updates for v4.5

The following changes since commit 9f9499ae8e6415cefc4fe0a96ad0e27864353c89: Linux 4.4-rc5 (2015-12-13 17:42:58 -0800) are available in the git repository at: git://linuxtv.org/snawrocki/samsung.git tags/clk-samsung-4.5 for you to fetch changes up to

Re: [PATCH 1/2] clk: samsung: exynos5422: add missing parent GSCL block clocks

Krzysztof, On 09/12/15 14:36, Krzysztof Kozlowski wrote: > W dniu 09.12.2015 o 19:14, Sylwester Nawrocki pisze: >> > Adding Stephen and linux-clk at Cc. >> > >> > On 09/12/15 05:49, Krzysztof Kozlowski wrote: >>> >> On 08.12.2015 22:46, Marek Szyprowski wrote: > This patch adds clocks,

Re: [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source

On 16.12.2015 19:32, Sudeep Holla wrote: > > > On 15/12/15 23:32, Krzysztof Kozlowski wrote: >> On 16.12.2015 01:35, Sudeep Holla wrote: >>> >>> >>> On 21/10/15 11:10, Sudeep Holla wrote: Though the keyboard and other driver will continue to support the legacy "gpio-key,wakeup",

Re: [PATCH 16/19] ARM: dts: s5pv210: replace legacy *,wakeup property with wakeup-source

2015-10-21 19:10 GMT+09:00 Sudeep Holla : > Though the keyboard and other driver will continue to support the legacy > "gpio-key,wakeup", "linux,input-wakeup" boolean property to enable the > wakeup source, "wakeup-source" is the new standard binding. > > This patch replaces

Re: [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source

On 21.10.2015 19:10, Sudeep Holla wrote: > Though the keyboard and other driver will continue to support the legacy > "gpio-key,wakeup", "linux-keypad,wakeup" boolean property to enable the > wakeup source, "wakeup-source" is the new standard binding. > > This patch replaces all the legacy wakeup

Re: [PATCH v6 0/9] samsung: pmu: split up SoC specific PMU data

On 17.11.2015 15:05, Pankaj Dubey wrote: > In this series I am splitting up SoC specific PMU configuration data into > mach-exynos folder itself, before moving all of them under > drivers/soc/samsung/. Also instead of making all changes in single patch it > has been broken into SoC specific

Re: [PATCH v9 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410

On 16.11.2015 16:43, Pavel Fedin wrote: > This patch extends Exynos SROM controller driver with ability to configure > controller outputs and enables SMSC9115 Ethernet chip on SMDK5410 board, > which is connected via SROMc bank #3. > > With this patchset, support for the whole existing SMDK range

Re: [PATCH v3 5/7] drm/exynos: mixer: refactor layer setup

Hi Marek, On 12/16/2015 09:21 PM, Marek Szyprowski wrote: > Properly configure blending properties of given hardware layer based on > the selected pixel format. Currently only per-pixel-based alpha is possible > when respective pixel format has been selected. Configuration of global, > per-plane

Re: [RESEND PATCH v5 0/8] Add support for Exynos SROM Controller driver

On 12.12.2015 16:43, Pankaj Dubey wrote: > THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES > > Series v5 got merged in kgene/for-next but due to last moment change before > pull > these patches were not accepted during 4.3 merge window.After that > kgene/for-next > got

Re: [PATCH 1/2] clk: samsung: exynos5422: add missing parent GSCL block clocks

On 17.12.2015 02:23, Sylwester Nawrocki wrote: > Krzysztof, > > On 09/12/15 14:36, Krzysztof Kozlowski wrote: >> W dniu 09.12.2015 o 19:14, Sylwester Nawrocki pisze: Adding Stephen and linux-clk at Cc. On 09/12/15 05:49, Krzysztof Kozlowski wrote: >> On 08.12.2015 22:46, Marek

Re: [GIT PULL 0/9] ARM: EXYNOS: Pull request for v4.5

On 17.12.2015 10:43, Krzysztof Kozlowski wrote: > On 02.12.2015 10:39, Krzysztof Kozlowski wrote: >> Hi Kukjin, >> >> A lot of stuff for v4.5 with 3 dependencies split into >> separate tags. The need for dependency is explained both >> in merge-commit and in description of a tag which is using >>

Re: [GIT PULL 0/9] ARM: EXYNOS: Pull request for v4.5

On 02.12.2015 10:39, Krzysztof Kozlowski wrote: > Hi Kukjin, > > A lot of stuff for v4.5 with 3 dependencies split into > separate tags. The need for dependency is explained both > in merge-commit and in description of a tag which is using > the dependency. Hi everyone, It's been like two

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

+Cc: Boram Park, Hi Marek, On 12/16/2015 09:21 PM, Marek Szyprowski wrote: > This patch adds all infrastructure to make zpos plane property > configurable from userspace. > > Signed-off-by: Marek Szyprowski > --- > drivers/gpu/drm/exynos/exynos_drm_drv.h | 4 ++- >

Re: [PATCH] PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties

On 16-12-15, 16:41, Bartlomiej Zolnierkiewicz wrote: > Commit 01fb4d3c39d3 ("PM / OPP: Parse 'opp--' > bindings") broke support for parsing standard opp-microvolt and > opp-microamp properties. Fix it by setting 'name' string to > proper value for !dev_opp->prop_name cases. > > Cc: Viresh Kumar

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

On Wed, Dec 16, 2015 at 01:21:43PM +0100, Marek Szyprowski wrote: > This patch adds all infrastructure to make zpos plane property > configurable from userspace. > > Signed-off-by: Marek Szyprowski Imo zpos should be a generic atomic property with well-defined

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

On Wed, Dec 16, 2015 at 02:28:36PM +0100, Daniel Vetter wrote: > On Wed, Dec 16, 2015 at 01:21:43PM +0100, Marek Szyprowski wrote: > > This patch adds all infrastructure to make zpos plane property > > configurable from userspace. > > > > Signed-off-by: Marek Szyprowski

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

Hello, On 2015-12-16 14:28, Daniel Vetter wrote: On Wed, Dec 16, 2015 at 01:21:43PM +0100, Marek Szyprowski wrote: This patch adds all infrastructure to make zpos plane property configurable from userspace. Signed-off-by: Marek Szyprowski Imo zpos should be a

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

On Wed, Dec 16, 2015 at 02:54:04PM +0100, Marek Szyprowski wrote: > Hello, > > On 2015-12-16 14:28, Daniel Vetter wrote: > >On Wed, Dec 16, 2015 at 01:21:43PM +0100, Marek Szyprowski wrote: > >>This patch adds all infrastructure to make zpos plane property > >>configurable from userspace. > >> >

Re: [PATCH v3 2/7] drm/exynos: make zpos property configurable

Hello, On 2015-12-16 15:21, Daniel Vetter wrote: On Wed, Dec 16, 2015 at 02:54:04PM +0100, Marek Szyprowski wrote: On 2015-12-16 14:28, Daniel Vetter wrote: On Wed, Dec 16, 2015 at 01:21:43PM +0100, Marek Szyprowski wrote: This patch adds all infrastructure to make zpos plane property

[PATCH v3 7/7] media: s5p-mfc: add iommu support

This patch adds support for IOMMU to s5p-mfc device driver. MFC firmware is limited and it cannot use the default configuration. If IOMMU is available, the patch disables the default DMA address space configuration and creates a new address space of size limited to 256M and base address set to

[PATCH v3 0/7] Exynos: MFC driver: reserved memory cleanup and IOMMU support

Hello, This patchset finally perform cleanup of custom code in s5p-mfc codec driver. The first part is removal of custom, driver specific code for intializing and handling of reserved memory. Instead, a generic code for reserved memory regions is used. Then, once it is done, the proper setup of

[PATCH v3 6/7] media: s5p-mfc: replace custom reserved memory init code with generic one

This patch removes custom code for initialization and handling of reserved memory regions in s5p-mfc driver and replaces it with generic named reserved memory regions specified in device tree. s5p-mfc driver now handles two reserved memory regions: "left" and "right", defined by generic reserved

[PATCH v3 3/7] of: reserved_mem: add support for named reserved mem nodes

This patch allows device drivers to initialize more than one reserved memory region assigned to given device. When driver needs to use more than one reserved memory region, it should allocate child devices and initialize regions by index or name for each of its child devices. Signed-off-by: Marek

[PATCH v3 4/7] media: vb2-dma-contig: add helper for setting dma max seg size

Add a helper function for device drivers to set DMA's max_seg_size. Setting it to largest possible value lets DMA-mapping API always create contiguous mappings in DMA address space. This is essential for all devices, which use dma-contig videobuf2 memory allocator and shared buffers.

[PATCH v3 5/7] media: set proper max seg size for devices on Exynos SoCs

All multimedia devices found on Exynos SoCs support only contiguous buffers, so set DMA max segment size to DMA_BIT_MASK(32) to let memory allocator to correctly create contiguous memory mappings. Signed-off-by: Marek Szyprowski ---

[PATCH v3 1/7] ARM: Exynos: convert MFC device to generic reserved memory bindings

This patch replaces custom properties for definining reserved memory regions with generic reserved memory bindings. All custom code for handling MFC-specific reserved memory can be now removed from Exynos-DT generic board code. Signed-off-by: Marek Szyprowski ---

[PATCH v3 2/7] ARM: dts: exynos4412-odroid*: enable MFC device

Enable support for Multimedia Codec (MFC) device for all Exynos4412-based Odroid boards. Signed-off-by: Marek Szyprowski --- arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 24 1 file changed, 24 insertions(+) diff --git

[PATCH] PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties

Commit 01fb4d3c39d3 ("PM / OPP: Parse 'opp--' bindings") broke support for parsing standard opp-microvolt and opp-microamp properties. Fix it by setting 'name' string to proper value for !dev_opp->prop_name cases. Cc: Viresh Kumar Cc: Lee Jones

[PATCH v3 1/7] drm/exynos: rename zpos to index

This patch renames zpos entry to index, because in most places it is used as index for selecting hardware layer/window instead of configurable layer position. This will later enable to make the zpos property configurable. Signed-off-by: Marek Szyprowski ---

[PATCH v3 4/7] drm/exynos: mixer: remove all static blending setup

From: Tobias Jakobi Previously blending setup was static and most of it was done in mixer_win_reset(). Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_mixer.c | 23 --- 1 file changed, 23

[PATCH v3 6/7] drm/exynos: mixer: also allow ARGB1555 and ARGB4444

From: Tobias Jakobi Allow the remaining alpha formats now that blending is properly setup. Signed-off-by: Tobias Jakobi Signed-off-by: Marek Szyprowski --- drivers/gpu/drm/exynos/exynos_mixer.c | 6 ++

[PATCH v3 7/7] drm/exynos: mixer: unify a check for video-processor window

Always use macro instead of hard-coded '2' value in conditions related to video processor window. Additional checks are not needed, because video layer is registered only when video processor is available. Signed-off-by: Marek Szyprowski ---

[PATCH v3 5/7] drm/exynos: mixer: refactor layer setup

Properly configure blending properties of given hardware layer based on the selected pixel format. Currently only per-pixel-based alpha is possible when respective pixel format has been selected. Configuration of global, per-plane alpha value, color key and background color will be added later.

[PATCH v3 2/7] drm/exynos: make zpos property configurable

This patch adds all infrastructure to make zpos plane property configurable from userspace. Signed-off-by: Marek Szyprowski --- drivers/gpu/drm/exynos/exynos_drm_drv.h | 4 ++- drivers/gpu/drm/exynos/exynos_drm_plane.c | 51 --- 2 files

[PATCH v3 3/7] drm/exynos: mixer: set window priority based on zpos

'zpos' plane property is configurable, so adjust hardware layers priority based on the zpos value. 'zpos' value shifted by one can be used directly as hw priority value and stored to the registers, because mixer accepts priority values from 1 to 15 (0 means that layer is disabled). This patch

Re: [PATCH 2/3] Add support for monitoring gpio switches

On 11/12/15 09:08, Linus Walleij wrote: On Fri, Dec 4, 2015 at 6:31 PM, Martyn Welch wrote: Select Chromebooks have gpio attached to switches used to cause the firmware to enter alternative modes of operation and/or control other device characteristics (such as

Re: [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source

On 15/12/15 23:32, Krzysztof Kozlowski wrote: On 16.12.2015 01:35, Sudeep Holla wrote: On 21/10/15 11:10, Sudeep Holla wrote: Though the keyboard and other driver will continue to support the legacy "gpio-key,wakeup", "linux-keypad,wakeup" boolean property to enable the wakeup source,