From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 7/7] ARM: mvebu: Add Armada 385 Access Point Development Board support
Date: Wed, 7 Jan 2015 15:34:20 +0100 [thread overview]
Message-ID: <20150107143420.GA30268@lunn.ch> (raw)
In-Reply-To: <20150107095936.GG7853@lukather>
> > > > > + i2c0: i2c at 11000 {
> > > > > + pinctrl-names = "default";
> > > > > + pinctrl-0 = <&i2c0_pins>;
> > > > > + status = "okay";
> > > > > + clock-frequency = <100000>;
> > > > > + };
> > > > > +
> > > > > + i2c1: i2c at 11100 {
> > > > > + status = "okay";
> > > > > + clock-frequency = <100000>;
> > > > > + };
> > > >
> > > > Is there anything on these two i2c busses?
> > >
> > > One goes to some pin of the mPCIe slot, the other is connected to the
> > > EEPROM.
> >
> > So could you add the EEPROM, and a comment about the mPCIe slot?
>
> I can't really add the EEPROM: it actually goes to two DIP sockets,
> one of them holding that EEPROM, the other one being empty.
>
> The default EEPROM also contains the board ID, that will be used by
> the bootloader. Erasing this will result in a board that can't be
> booted, so I'm not really sure exposing it to the user is a good idea.
O.K, please add a comment. People like me tend to run i2c-detect to
see if there is anything interesting on the bus. A warning you can
brick the board could save somebody an interesting time.
Andrew
next prev parent reply other threads:[~2015-01-07 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 15:28 [PATCH v2 0/7] ARM: mvebu: Add Armada 385 AP support Maxime Ripard
2015-01-06 15:28 ` [PATCH v2 1/7] ARM: mvebu: Rename DEBUG_LL to indicate UART index Maxime Ripard
2015-01-06 21:07 ` Gregory CLEMENT
2015-01-06 15:28 ` [PATCH v2 2/7] ARM: mvebu: Add UART1 as DEBUG_LL possible target Maxime Ripard
2015-01-06 21:08 ` Gregory CLEMENT
2015-01-06 15:28 ` [PATCH v2 3/7] ARM: mvebu: a38x: Fix node names Maxime Ripard
2015-01-06 21:10 ` Gregory CLEMENT
2015-01-06 15:28 ` [PATCH v2 4/7] pinctrl: mvebu: a38x: Add UART1 muxing options Maxime Ripard
2015-01-06 15:28 ` [PATCH v2 5/7] ARM: mvebu: A38x: Remove redundant pinctrl informations Maxime Ripard
2015-01-06 21:11 ` Gregory CLEMENT
2015-01-06 15:28 ` [PATCH v2 6/7] ARM: mvebu: Add a number of pinctrl functions Maxime Ripard
2015-01-06 21:25 ` Gregory CLEMENT
2015-01-06 15:28 ` [PATCH v2 7/7] ARM: mvebu: Add Armada 385 Access Point Development Board support Maxime Ripard
2015-01-06 15:57 ` Andrew Lunn
2015-01-06 17:31 ` Maxime Ripard
2015-01-06 18:07 ` Andrew Lunn
2015-01-07 9:59 ` Maxime Ripard
2015-01-07 14:34 ` Andrew Lunn [this message]
2015-01-07 16:26 ` Gregory CLEMENT
2015-01-08 15:21 ` Nadav Haklai
2015-01-06 21:47 ` Gregory CLEMENT
2015-01-07 9:27 ` Maxime Ripard
2015-01-07 15:25 ` Gregory CLEMENT
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=20150107143420.GA30268@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.