On Wed, Mar 6, 2013 at 12:18 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Add Samsung Exynos5250 SoC specific data to enable pinctrl support for
all platforms based on Exynos5250.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Reviewed-by: Tomasz Figa t.f...@samsung.com
On Wed, Mar 6, 2013 at 12:36 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Wed, Mar 6, 2013 at 12:42 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Wed, Mar 6, 2013 at 12:49 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Wed, Mar 6, 2013 at 1:04 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Wed, Mar 6, 2013 at 12:55 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Wed, Mar 6, 2013 at 1:36 PM, Thomas Abraham
thomas.abra...@linaro.org 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
On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha
shaik.am...@samsung.com 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
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 merged
Hi Rahul,
On Thu, Mar 7, 2013 at 2:58 PM, Rahul Sharma r.sh.o...@gmail.com wrote:
On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha
shaik.am...@samsung.com wrote:
s3c_set_clksrc() updates the clock source as per u-boot settings.
This patch adds the functionality to overwrite u-boot settings,
On Thu, Mar 7, 2013 at 12:37 PM, Stéphane Marchesin
stephane.marche...@gmail.com wrote:
On Wed, Mar 6, 2013 at 8:43 PM, Inki Dae inki@samsung.com wrote:
2013/3/7 김승우 sw0312@samsung.com:
On 2013년 03월 04일 23:05, Rahul Sharma wrote:
Thanks Sean,
On Wed, Feb 27, 2013 at 9:47 PM, Sean
On Thu, Mar 7, 2013 at 3:12 PM, Shaik Ameer Basha
shaik.sams...@gmail.com wrote:
Hi Rahul,
On Thu, Mar 7, 2013 at 2:58 PM, Rahul Sharma r.sh.o...@gmail.com wrote:
On Thu, Mar 7, 2013 at 11:01 AM, Shaik Ameer Basha
shaik.am...@samsung.com wrote:
s3c_set_clksrc() updates the clock source as
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
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 lonsn2...@gmail.com
Cc: sta...@vger.kernel.org # 3.7
tags, and any other in case someone
Linus Walleij wrote:
On Wed, Mar 6, 2013 at 12:18 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Add Samsung Exynos5250 SoC specific data to enable pinctrl support for
all platforms based on Exynos5250.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Reviewed-by:
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
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
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_STATUS
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
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 IS_ERR(),
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 linus.wall...@linaro.org
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 diand...@chromium.org
mailto:diand...@chromium.org wrote:
Linus,
+dw_mmc folks and Stephen Warren : for context here, we are discussing
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 reuse
On Thu, Mar 7, 2013 at 5:13 PM, Doug Anderson diand...@chromium.org 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,
Linus,
On Thu, Mar 7, 2013 at 6:04 PM, Linus Walleij linus.wall...@linaro.org wrote:
On Thu, Mar 7, 2013 at 5:13 PM, Doug Anderson diand...@chromium.org 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
On Thu, Mar 7, 2013 at 12:09 PM, Kukjin Kim kgene@samsung.com 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
26 matches
Mail list logo
