From: Tony Lindgren <tony@atomide.com>
To: Philip Balister <philip@balister.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap: Fix cmdline muxing (Re: New pinmux)
Date: Fri, 8 Jan 2010 11:35:08 -0800 [thread overview]
Message-ID: <20100108193508.GA2879@atomide.com> (raw)
In-Reply-To: <4B478081.4060809@balister.org>
* Philip Balister <philip@balister.org> [100108 10:57]:
> On 01/08/2010 01:00 PM, Tony Lindgren wrote:
> >* Philip Balister<philip@balister.org> [100108 07:35]:
> >>I am trying to work out how to use the new pinmux code on my
> >>Overo+Summit system. I have a recent git running with the new pinmux
> >>code built. I am trying to configure the mcspi1_clk pin on the
> >>expansion connector as gpio_171 with the following:
> >>
> >>root@overo:~# dmesg |grep mux
> >>
> >>Kernel command line: console=ttyS2,115200n8 vram=12M
> >>omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y
> >>omapdss.def_display=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3
> >>rootwait omap_mux=mcspi1_clk.gpio_171=0x0
> >>
> >>And this is what happens :(
> >>
> >>mux: Could not set signal mcspi1_clk
> >>
> >>mux: Setting signal i2c3_scl.i2c3_scl 0x0118 -> 0x0100
> >>
> >>Any suggestions?
> >
> >Sounds like the cmdline options got broken by some changes
> >I did to limit everything to happen as __init..
> >
> >Can you please try the following patch?
>
> The patch solved the problem, thanks! Great work guys, this will
> really help people working with boards with expansion connectors
> like the Beagle and Overo.
Good to hear :)
> Tony, do you need a signoff from me for this? Not to sure what the
> procedure is.
Maybe reply with your Tested-by? See Documentation/SubmittingPatches
for Reported-by/Tested-by etc.
Regards,
Tony
next prev parent reply other threads:[~2010-01-08 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 15:30 New pinmux Philip Balister
2010-01-08 18:00 ` [PATCH] omap: Fix cmdline muxing (Re: New pinmux) Tony Lindgren
2010-01-08 18:59 ` Philip Balister
2010-01-08 19:35 ` Tony Lindgren [this message]
2010-01-08 22:38 ` Philip Balister
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100108193508.GA2879@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=philip@balister.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox