Re: [PATCH v2 1/3] pinctrl: exynos: add exynos5250 SoC specific data

On Thu, Mar 7, 2013 at 12:09 PM, Kukjin Kim wrote: > [Me] >> So shall I merge these three patches to the pinctrl tree or not? >> > Hi Linus, this series is already in Samsung tree with your ack. OK good, thanks! Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe li

Re: State of pinctrl and exynos5250?

Linus, On Thu, Mar 7, 2013 at 6:04 PM, Linus Walleij wrote: > On Thu, Mar 7, 2013 at 5:13 PM, Doug Anderson wrote: > >> ...I think the most important issue at hand is the device tree >> bindings for pinmux on this device. It sounds like you are in >> agreement that the best thing is to have a p

Re: State of pinctrl and exynos5250?

On Thu, Mar 7, 2013 at 5:13 PM, Doug Anderson wrote: > ...I think the most important issue at hand is the device tree > bindings for pinmux on this device. It sounds like you are in > agreement that the best thing is to have a pinmux specified per-slot. I don't know, Stephen's point to have one

Re: [PATCH 00/23] RFC: exynos multiplatform support

On Thursday 07 of March 2013 08:22:03 Thierry Reding wrote: > On Thu, Mar 07, 2013 at 03:02:46AM +, Arnd Bergmann wrote: > > On Wednesday 06 March 2013, Thierry Reding wrote: > > > > Option 2 would probably come down to having a trivial MFD driver > > > > exposing a regmap. You can probably reu

Re: State of pinctrl and exynos5250?

On 03/07/2013 09:27 AM, Doug Anderson wrote: > +the proper address for Will. Sorry... > > > On Thu, Mar 7, 2013 at 8:13 AM, Doug Anderson > wrote: > > Linus, > > +dw_mmc folks and Stephen Warren : for context here, we are discussing > device tree bind

Re: State of pinctrl and exynos5250?

Linus, +dw_mmc folks and Stephen Warren : for context here, we are discussing device tree bindings for pinmux for dw_mmc. The issue at hand is whether they belong under the slot node or under the top-level device node. On Wed, Mar 6, 2013 at 11:57 PM, Linus Walleij wrote: > I don't quite under

Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440

On Thu, Mar 07, 2013 at 04:28:00PM +0100, Sylwester Nawrocki wrote: > On 03/07/2013 05:13 AM, Amit Daniel Kachhap wrote: > > + dvfs_info->cpu_clk = devm_clk_get(dvfs_info->dev, "armclk"); > > + if (IS_ERR_OR_NULL(dvfs_info->cpu_clk)) { > > devm_clk_get() return value needs to be checked with I

Re: [PATCH] ARM: SAMSUNG: Set clock parent if provided

On 03/07/2013 06:31 AM, Shaik Ameer Basha wrote: > s3c_set_clksrc() updates the clock source as per u-boot settings. > This patch adds the functionality to overwrite u-boot settings, > if user provides the clock parent field. In case of wrong source > provided by the user, it will retain the u-boot

Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440

On 03/07/2013 05:13 AM, Amit Daniel Kachhap wrote: > +/* Register definations */ s/definations/definitions > +#define XMU_DVFS_CTRL0x0060 > +#define XMU_PMU_P0_7 0x0064 > +#define XMU_C0_3_PSTATE 0x0090 > +#define XMU_P_LIMIT 0x00A0 > +#define XMU_P_S

Re: [PATCH] ARM: EXYNOS: change HAVE_SAMSUNG_KEYPAD to KEYBOARD_SAMSUNG

On Thu, 2013-03-07 at 10:02 +0900, Kukjin Kim wrote: > BTW, just to use only 8~12 digits of commit ID, "Commit 6b5ab4f4" is > enough instead of full commit ID. I used to do that but now I actually prefer to use 40 hex character strings. Sure, they're ugly, but so are strings of 10, or 12 hex char

Re: [PATCH] ARM: EXYNOS: remove EXYNOS_DEV_SYSMMU entirely

On Thu, 2013-03-07 at 10:12 +0900, Kukjin Kim wrote: > Actually, to update iommu for exynos is on-going. And as I know, it > will be done this time for v3.10 by KyongHo Cho, so it would be better > to handle this cleanup with that at the same time. You mean I should try to recheck the status of EX

RE: [PATCH v2 1/3] pinctrl: exynos: add exynos5250 SoC specific data

Linus Walleij wrote: > > On Wed, Mar 6, 2013 at 12:18 PM, Thomas Abraham > wrote: > > > Add Samsung Exynos5250 SoC specific data to enable pinctrl support for > > all platforms based on Exynos5250. > > > > Signed-off-by: Thomas Abraham > > Reviewed-by: Tomasz Figa > > Acked-by: Linus Walleij

RE: [PATCH] ARM: S5PV210: Fix PL330 DMA controller clkdev entries

Sylwester Nawrocki wrote: > > On 03/04/2013 02:00 PM, Kukjin Kim wrote: > > Looks good to me, applied into -fixes. > > > > Sylwester, why did you want to re-send this patch? > > Only to add > > Tested-by: Lonsn > Cc: sta...@vger.kernel.org # 3.7 > > tags, and any other in case someone else tes

RE: [PATCH] mmc: dwmmc: let device core setup the default pin configuration

Hi Thomas, On Wednesday, March 06, 2013, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the pin configuration code based on the deprecated Samsung specific > gpio bindings is removed. 'setup_bus' callback is still useful in dw_mci_drv_data? Considering

Re: [PATCH] ARM: SAMSUNG: Set clock parent if provided

On Thu, Mar 7, 2013 at 3:12 PM, Shaik Ameer Basha wrote: > Hi Rahul, > > On Thu, Mar 7, 2013 at 2:58 PM, Rahul Sharma wrote: >> On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha >> wrote: >>> s3c_set_clksrc() updates the clock source as per u-boot settings. >>> This patch adds the functionality

Re: [PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

On Thu, Mar 7, 2013 at 12:37 PM, Stéphane Marchesin wrote: > On Wed, Mar 6, 2013 at 8:43 PM, Inki Dae wrote: >> 2013/3/7 김승우 : >>> >>> >>> On 2013년 03월 04일 23:05, Rahul Sharma wrote: Thanks Sean, On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: > On Wed, Feb 27, 2013 at 8:22

Re: [PATCH] ARM: SAMSUNG: Set clock parent if provided

Hi Rahul, On Thu, Mar 7, 2013 at 2:58 PM, Rahul Sharma wrote: > On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha > wrote: >> s3c_set_clksrc() updates the clock source as per u-boot settings. >> This patch adds the functionality to overwrite u-boot settings, >> if user provides the clock parent

Re: [PATCH] ARM: S3C24XX: drop "select MACH_N35"

On Thu, Mar 07, 2013 at 10:14:19AM +0900, Kukjin Kim wrote: > Russell King - ARM Linux wrote: > > And deleting entries from it is pointless if they've ever been in the > > kernel. > > OK, I see and agree. The issue is that the database system "locks" an entry into the file as soon as support is m

Re: [PATCH] ARM: SAMSUNG: Set clock parent if provided

On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha wrote: > s3c_set_clksrc() updates the clock source as per u-boot settings. > This patch adds the functionality to overwrite u-boot settings, > if user provides the clock parent field. In case of wrong source > provided by the user, it will retain

RE: [PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

> -Original Message- > From: 김승우 [mailto:sw0312@samsung.com] > Sent: Thursday, March 07, 2013 4:04 PM > To: Rahul Sharma > Cc: Inki Dae; linux-samsung-soc@vger.kernel.org; Sean Paul; sunil joshi; > dri-de...@lists.freedesktop.org; Rahul Sharma; sw0312@samsung.com > Subject: Re: [P

Re: [PATCH 0/2] ARM: dts: Add default pin states for client nodes on Exynos4/5 platforms

On Wed, Mar 6, 2013 at 1:36 PM, Thomas Abraham wrote: > This patch series populates the default pin states in client nodes > of Exynos4 and Exynos5 platforms. Exynos4/5 platforms are migrating > to use pinctrl framework and having the default pin states listed > in the client nodes allows the dev

Re: [PATCH] ASoC: samsung: let device core setup the default pin configuration

On Wed, Mar 6, 2013 at 12:55 PM, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the pin configuration code based on the deprecated Samsung specific > gpio bindings in i2s driver is removed. > > Signed-off-by: Thomas Abraham Acked-by: Linus Walleij

Re: [PATCH] mmc: dwmmc: let device core setup the default pin configuration

On Wed, Mar 6, 2013 at 1:04 PM, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the pin configuration code based on the deprecated Samsung specific > gpio bindings is removed. > > Signed-off-by: Thomas Abraham Acked-by: Linus Walleij Yours, Linus Wa

Re: [PATCH] input: samsung-keypad: let device core setup the default pin configuration

On Wed, Mar 6, 2013 at 12:49 PM, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the pin configuration code based on the deprecated Samsung specific > gpio bindings is removed. > > Signed-off-by: Thomas Abraham Acked-by: Linus Walleij Yours, Linus W

Re: [PATCH] spi: s3c64xx: let device core setup the default pin configuration

On Wed, Mar 6, 2013 at 12:42 PM, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the pin configuration code based on the deprecated Samsung specific > gpio bindings is removed. > > Signed-off-by: Thomas Abraham Acked-by: Linus Walleij Yours, Linus W

Re: [PATCH] mmc: sdhci-s3c: let device core setup the default pin configuration

On Wed, Mar 6, 2013 at 12:36 PM, Thomas Abraham wrote: > With device core now able to setup the default pin configuration, > the call to devm_pinctrl_get_select_default can be removed. And > the pin configuration code based on the deprecated Samsung specific > gpio bindings is also removed. > > S

Re: [PATCH v2 1/3] pinctrl: exynos: add exynos5250 SoC specific data

On Wed, Mar 6, 2013 at 12:18 PM, Thomas Abraham wrote: > Add Samsung Exynos5250 SoC specific data to enable pinctrl support for > all platforms based on Exynos5250. > > Signed-off-by: Thomas Abraham > Reviewed-by: Tomasz Figa > Acked-by: Linus Walleij So shall I merge these three patches to t