From: Florian Fainelli <florian@openwrt.org>
To: mbizon@freebox.fr
Cc: ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/2] bcm63xx: only set the proper GPIO overlay settings
Date: Mon, 31 Aug 2009 23:37:31 +0200 [thread overview]
Message-ID: <200908312337.36634.florian@openwrt.org> (raw)
In-Reply-To: <1251750389.10420.24.camel@sakura.staff.proxad.net>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Le lundi 31 août 2009 22:26:29, Maxime Bizon a écrit :
> On Mon, 2009-08-31 at 20:28 +0200, Florian Fainelli wrote:
> > This patch makes the GPIO pin multiplexing configuration
> > read the initial GPIO mode register value instead of
> > setting it initially to 0, then setting the correct
> > bits, this is safer.
>
> I disagree, now we get working or not working devices depending on the
> CFE version used, for which we don't have any public source code nor
> changelog.
I did not think this could break other boards, it is required on BCM6345
though.
>
> I cleared the register for that purpose.
>
> If a particular pin muxing config is needed for some board, we should
> add this to the board specific struct instead.
Then I will make it BCM6345 specific.
Thanks.
--
Best regards, Florian Fainelli
Email: florian@openwrt.org
Web: http://openwrt.org
IRC: [florian] on irc.freenode.net
-------------------------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2009-08-31 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 18:28 [PATCH 2/2] bcm63xx: only set the proper GPIO overlay settings Florian Fainelli
2009-08-31 20:26 ` Maxime Bizon
2009-08-31 21:37 ` Florian Fainelli [this message]
2009-10-11 22:53 ` Ralf Baechle
2009-10-12 16:12 ` Florian Fainelli
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=200908312337.36634.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).