On Fri, Aug 7, 2009 at 2:55 AM, Tony Lindgren wrote:
> Well we need to mux all the pins that can potentially conflict only in the
> board-*.c files.
>
> For naming, I think we should use the default mode0 name in the mux register
> as the
> key, and then link package specific pin names to that ke
* Vladimir Pantelic [090807 12:24]:
> Tony Lindgren wrote:
>
>
>>> Here's an idea:
>>>
>>> 1) Replace index with enum search in pin table - this breaks the
>>> requirement that the enum list and table align - a good thing as
>>> misalingment has bitten me multiple times when adding pins to th
Tony Lindgren wrote:
Here's an idea:
1) Replace index with enum search in pin table - this breaks the
requirement that the enum list and table align - a good thing as
misalingment has bitten me multiple times when adding pins to the
current mux table. Also, pinmux setup is done infrequen
* Peter Barada [090806 19:31]:
> On Thu, 2009-08-06 at 11:09 -0400, Philip Balister wrote:
> > Kevin Hilman wrote:
> > > John Sarman writes:
> > >
> > >> On Wed, Aug 5, 2009 at 2:35 PM, Kevin
> > >> Hilman wrote:
> > >>> Steve Sakoman wrote:
> > On Wed, Aug 5, 2009 at 10:58 AM, Kevin
> > >
On Thu, 2009-08-06 at 11:09 -0400, Philip Balister wrote:
> Kevin Hilman wrote:
> > John Sarman writes:
> >
> >> On Wed, Aug 5, 2009 at 2:35 PM, Kevin Hilman
> >> wrote:
> >>> Steve Sakoman wrote:
> On Wed, Aug 5, 2009 at 10:58 AM, Kevin
> Hilman wrote:
> > Steve Sakoman wrote:
> >
On Thu, Aug 6, 2009 at 8:16 AM, Kevin Hilman wrote:
>> even for 1 package, how will you know whether OMAP3_MMC3_CLK is connected
>> to ball AB1 or AF10 as both is possible...
>
> doh! good point. I was thinking of functions that are only availble
> on a single ball.
This is the point I was (unsu
Vladimir Pantelic writes:
> Kevin Hilman wrote:
>
>>> AB1_35XXCBB_MMC3_CLK
>>> AF10_35XXCBB_MMC3_CLK
>>> R9_35XXCBC_MMC3_CLK
>>> AB2_35XXCBC_MMC3_CLK
>>> AC1_35XXCUS_MMC3_CLK
>>> We would then have to update mux.c making sure the position matches
>>> and
Kevin Hilman wrote:
John Sarman writes:
On Wed, Aug 5, 2009 at 2:35 PM, Kevin Hilman wrote:
Steve Sakoman wrote:
On Wed, Aug 5, 2009 at 10:58 AM, Kevin
Hilman wrote:
Steve Sakoman wrote:
And up to now in each case I shrug and say "no time to do that now,
I'll just leave kernel pinmuxing tu
Kevin Hilman wrote:
AB1_35XXCBB_MMC3_CLK
AF10_35XXCBB_MMC3_CLK
R9_35XXCBC_MMC3_CLK
AB2_35XXCBC_MMC3_CLK
AC1_35XXCUS_MMC3_CLK
We would then have to update mux.c making sure the position matches
and add the proper settings.
So this is obviously a mainten
John Sarman writes:
> On Wed, Aug 5, 2009 at 2:35 PM, Kevin Hilman
> wrote:
>> Steve Sakoman wrote:
>>>
>>> On Wed, Aug 5, 2009 at 10:58 AM, Kevin
>>> Hilman wrote:
Steve Sakoman wrote:
>
> And up to now in each case I shrug and say "no time to do that now,
> I'll just leav
* John Sarman [090806 05:11]:
> On Wed, Aug 5, 2009 at 2:35 PM, Kevin Hilman
> wrote:
> > Steve Sakoman wrote:
> >>
> >> On Wed, Aug 5, 2009 at 10:58 AM, Kevin
> >> Hilman wrote:
> >>>
> >>> Steve Sakoman wrote:
>
> And up to now in each case I shrug and say "no time to do that now,
> >
On Wednesday 05 August 2009 11:55, Philip Balister wrote:
> Kevin Hilman wrote:
> > Steve Sakoman wrote:
> >> On Wed, Aug 5, 2009 at 10:58 AM, Kevin
> >>
> >> Hilman wrote:
> >>> Steve Sakoman wrote:
> And up to now in each case I shrug and say "no time to do that now,
> I'll just leave k
On Wed, Aug 5, 2009 at 2:35 PM, Kevin Hilman wrote:
> Steve Sakoman wrote:
>>
>> On Wed, Aug 5, 2009 at 10:58 AM, Kevin
>> Hilman wrote:
>>>
>>> Steve Sakoman wrote:
And up to now in each case I shrug and say "no time to do that now,
I'll just leave kernel pinmuxing turned off and do
Kevin Hilman wrote:
Steve Sakoman wrote:
On Wed, Aug 5, 2009 at 10:58 AM, Kevin
Hilman wrote:
Steve Sakoman wrote:
And up to now in each case I shrug and say "no time to do that now,
I'll just leave kernel pinmuxing turned off and do it in u-boot"
I agree there are lots of shortcomings in the
Hi,
There are a couple of other things relating to pix mux settings,
specific to the Overo, that is currently in u-boot, that should be
moved to the kernel, e.g. bluetooth subsystem of the wi2wi chipset,
used on the Overo Air/Fire modules.
Best regards,
Elvis
On Aug 5, 2009, at 8:25 PM
Steve Sakoman wrote:
On Wed, Aug 5, 2009 at 10:58 AM, Kevin
Hilman wrote:
Steve Sakoman wrote:
And up to now in each case I shrug and say "no time to do that now,
I'll just leave kernel pinmuxing turned off and do it in u-boot"
I agree there are lots of shortcomings in the current mux code and
On Wed, Aug 5, 2009 at 10:58 AM, Kevin
Hilman wrote:
> Steve Sakoman wrote:
>> And up to now in each case I shrug and say "no time to do that now,
>> I'll just leave kernel pinmuxing turned off and do it in u-boot"
>
> I agree there are lots of shortcomings in the current mux code and we've
> been
Steve Sakoman wrote:
On Wed, Aug 5, 2009 at 9:35 AM, John Sarman wrote:
On Wed, Aug 5, 2009 at 12:25 PM, Kevin Hilman
wrote:
Might I suggest a kernel patch for this rather than fixing u-boot so that
all the midnight oil you've burnt does not have to be duplicated by others.
Well I dont know h
Steve Sakoman wrote:
> On Wed, Aug 5, 2009 at 9:35 AM, John Sarman wrote:
> > On Wed, Aug 5, 2009 at 12:25 PM, Kevin Hilman
> > wrote:
> >> Might I suggest a kernel patch for this rather than fixing u-boot so that
> >> all the midnight oil you've burnt does not have to be duplicated by others.
> >
On Wed, Aug 5, 2009 at 9:35 AM, John Sarman wrote:
> On Wed, Aug 5, 2009 at 12:25 PM, Kevin Hilman
> wrote:
>> Might I suggest a kernel patch for this rather than fixing u-boot so that
>> all the midnight oil you've burnt does not have to be duplicated by others.
> Well I dont know how to answer t
On Wed, Aug 5, 2009 at 12:25 PM, Kevin
Hilman wrote:
> John Sarman writes:
>
>> -- Forwarded message --
>> From: John Sarman
>> Date: Wed, Aug 5, 2009 at 12:01 PM
>> Subject: Re: MMC3 Overo
>> To: Grazvydas Ignotas
>>
>>
>> O
John Sarman writes:
> -- Forwarded message --
> From: John Sarman
> Date: Wed, Aug 5, 2009 at 12:01 PM
> Subject: Re: MMC3 Overo
> To: Grazvydas Ignotas
>
>
> On Wed, Aug 5, 2009 at 4:32 AM, Grazvydas Ignotas wrote:
>>>
>>> MUX_V
-- Forwarded message --
From: John Sarman
Date: Wed, Aug 5, 2009 at 12:01 PM
Subject: Re: MMC3 Overo
To: Grazvydas Ignotas
On Wed, Aug 5, 2009 at 4:32 AM, Grazvydas Ignotas wrote:
>>
>> MUX_VAL(CP(ETK_CLK_ES2), (IDIS | PTU | EN | M2)) /*MMC3_CLK*/\
>
>
> MUX_VAL(CP(ETK_CLK_ES2), (IDIS | PTU | EN | M2)) /*MMC3_CLK*/\
You must have input enable on CLK line for MMC3 or it won't work for
some reason (MMC 1 and 2 doesn't need that). Without this part of the
host controller hardware doesn't get the clock I guess, or something
like that. You
On Sun, Aug 2, 2009 at 9:20 PM, Paul Walmsley wrote:
> Hello John,
>
> you are using the PM branch, correct?
>
> On Thu, 30 Jul 2009, John Sarman wrote:
>
>> On Thu, Jul 30, 2009 at 11:49 AM, John Sarman wrote:
>> > I am trying to use mmc3 on the Overo Gumstix board with no luck. I
>> > have patch
On Mon, 3 Aug 2009, John Sarman wrote:
> On Sun, Aug 2, 2009 at 9:20 PM, Paul Walmsley wrote:
> > From: Paul Walmsley
> > Date: Mon, 3 Aug 2009 04:18:45 +0300
> > Subject: [PATCH] OMAP3 hwmod: fix MMC3 IRQ
> >
> > The MMC3 IRQ is incorrect in mach-omap2/omap_hwmod_34xx.h, which causes
> > MMC3 i
Hi,
On Aug 3, 2009, at 2:56 PM, John Sarman wrote:
On Mon, Aug 3, 2009 at 6:37 AM, Elvis Dowson
wrote:
MMC3 connects to one of the 70 pin bottom connectors.
Is this for some custom board? I am using the standard Overo Earth +
palo43 combo. Just want to know if I need to apply the mmc3 p
On Mon, Aug 3, 2009 at 6:37 AM, Elvis Dowson wrote:
> Hi John,
> What does MMC3 on the Overo connect to?
MMC3 connects to one of the 70 pin bottom connectors. The datasheet
states that MMC3 has no PBIAS circuit so you have to interface it with
1.8V logic. I used a TXS0108 from TI
Paul,
On Sun, Aug 2, 2009 at 9:20 PM, Paul Walmsley wrote:
> Hello John,
>
> you are using the PM branch, correct?
Unfortunately I am not using the pm patch, because I am stuck at
2.6.30-rc8. This is because it is the last place I have usb host
working. I backported the necessary changes and pm
Hello John,
you are using the PM branch, correct?
On Thu, 30 Jul 2009, John Sarman wrote:
> On Thu, Jul 30, 2009 at 11:49 AM, John Sarman wrote:
> > I am trying to use mmc3 on the Overo Gumstix board with no luck. I
> > have patched the kernel with the latest changes and have yet to see a
> > c
On Thu, Jul 30, 2009 at 11:49 AM, John Sarman wrote:
> I am trying to use mmc3 on the Overo Gumstix board with no luck. I
> have patched the kernel with the latest changes and have yet to see a
> clk pulse, both before and after the patches.
After adding some debugging printks, I have determined t
I am trying to use mmc3 on the Overo Gumstix board with no luck. I
have patched the kernel with the latest changes and have yet to see a
clk pulse, both before and after the patches.
So far I have reconfigured the pins with uboot to GPIO and tested each
pin to verify that the signals are connected
32 matches
Mail list logo
