Re: State of pinctrl and exynos5250?

2013-03-07 Thread Doug Anderson
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?

2013-03-07 Thread Linus Walleij
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: State of pinctrl and exynos5250?

2013-03-07 Thread Stephen Warren
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?

2013-03-07 Thread Doug Anderson
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: State of pinctrl and exynos5250?

2013-03-06 Thread Linus Walleij
On Wed, Mar 6, 2013 at 12:49 AM, Thomas Abraham wrote: > Yes, I am currently held up with supporting default pin states at slot > level. One option that could be considered is to list out the default > pin states for all slots in the parent node of the slots. So it would > be something like below

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Doug Anderson
Thomas, On Tue, Mar 5, 2013 at 4:01 PM, Thomas Abraham wrote: > So now I have: pinctrl_0 is SPI[46], pinctrl_1 is SPI[45], pinctrl_2 > is SPI[50] and pinctrl_3 is SPI[47]. I am yet to test this and > confirm. If you feel these are wrong, could you please let me know. Yes, that matches my finding

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Doug Anderson
Thomas, On Tue, Mar 5, 2013 at 3:49 PM, Thomas Abraham wrote: > Yes, I am currently held up with supporting default pin states at slot > level. One option that could be considered is to list out the default > pin states for all slots in the parent node of the slots. So it would > be something lik

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Thomas Abraham
On 6 March 2013 05:20, Doug Anderson wrote: > Thomas, > > On Mon, Mar 4, 2013 at 6:04 AM, Thomas Abraham > wrote: >> >> Ok. I will repost this patch again with pinctrl_1 and pinctrl_2 >> included. I had not included this in the earlier patch since I was not >> sure of the best pin grouping for th

RE: State of pinctrl and exynos5250?

2013-03-05 Thread Kukjin Kim
Doug Anderson wrote: > > Tomasz, > > Thanks for your response. > > > On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa wrote: > > > > The 4 patches above are already merged in Kgene's for-next-next (for > 3.10) > > branch. > > Excellent. I see them now. I haven't yet seen them show up in > linux-

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Doug Anderson
Thomas, On Mon, Mar 4, 2013 at 6:04 AM, Thomas Abraham wrote: > > Ok. I will repost this patch again with pinctrl_1 and pinctrl_2 > included. I had not included this in the earlier patch since I was not > sure of the best pin grouping for the camera and c2c interface. OK, thanks. >>> --> NOTE:

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Thomas Abraham
On 6 March 2013 04:59, Doug Anderson wrote: > Tomasz, > > Thanks for your response. > > > On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa wrote: >> >> The 4 patches above are already merged in Kgene's for-next-next (for 3.10) >> branch. > > Excellent. I see them now. I haven't yet seen them show up

Re: State of pinctrl and exynos5250?

2013-03-05 Thread Doug Anderson
Tomasz, Thanks for your response. On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa wrote: > > The 4 patches above are already merged in Kgene's for-next-next (for 3.10) > branch. Excellent. I see them now. I haven't yet seen them show up in linux-next (which is where I tend to look first), though

Re: State of pinctrl and exynos5250?

2013-03-04 Thread Thomas Abraham
Hi Doug, On 2 March 2013 17:18, Tomasz Figa wrote: > Hello Doug, > > On Friday 01 of March 2013 16:19:39 Doug Anderson wrote: >> Thomas and Tomasz, >> >> I'm trying to get my head wrapped around the state of pinctrl for >> exynos5250. I see various patches that have floated around at times >> bu

Re: State of pinctrl and exynos5250?

2013-03-02 Thread Tomasz Figa
Hello Doug, On Friday 01 of March 2013 16:19:39 Doug Anderson wrote: > Thomas and Tomasz, > > I'm trying to get my head wrapped around the state of pinctrl for > exynos5250. I see various patches that have floated around at times > but it doesn't look like anything has landed. It would be reall

State of pinctrl and exynos5250?

2013-03-01 Thread Doug Anderson
Thomas and Tomasz, I'm trying to get my head wrapped around the state of pinctrl for exynos5250. I see various patches that have floated around at times but it doesn't look like anything has landed. It would be really nice to get this resolved since I think it blocks getting eint support landed