From: michal.simek@xilinx.com (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [Dev] [PATCH 0/5] RFC: Mezzanine handling for 96boards
Date: Fri, 22 Jun 2018 15:08:25 +0200 [thread overview]
Message-ID: <616e99d3-b43e-58ca-aa82-eaf41f618682@xilinx.com> (raw)
In-Reply-To: <CAMuUZTH8wXhoBSKwsCFBRBzAvvBBTUTnkmwKEpq=56=URo7kjQ@mail.gmail.com>
On 19.6.2018 17:32, Yang Zhang wrote:
> On 19 June 2018 at 16:30, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
>> On 19 June 2018 at 17:26, Yang Zhang <yang.zhang@96boards.org> wrote:
>>> Yes.
>>>
>>> https://github.com/96boards/documentation/blob/master/
>> mezzanine/files/mezzanine-design-guidelines.pdf
>>>
>>> Under Configuration data section
>>>
>>
>> OK, fair enough. Do any such mezzanines exist yet? Should we offer
>> more guidance on how exactly this discovery should be implemented?
>>
>>
> I can't be sure, could look into it - I know there were couple of from
> Arrow and ST were supporting this.
>
> Yes, more details guidance of "How to" is always welcome :-).
Unfortunately this is not saying i2c address and also how to handle
stacked solution.
I have told to Linus what Xilinx is using for FMC connector present on
the most of xilinx development boards.
These on board FMC eeproms contain information in FRU format.
Also there incomplete support fmc support in the kernel in drivers/fmc
which was added by Alessandro Rubini in 2013.
At least these eeprom could reuse FRU data format.
Thanks,
Michal
next prev parent reply other threads:[~2018-06-22 13:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 7:45 [PATCH 0/5] RFC: Mezzanine handling for 96boards Linus Walleij
2018-06-18 7:45 ` [PATCH 1/5] RFC: gpio: Add API to explicitly name a consumer Linus Walleij
2018-06-18 7:45 ` [PATCH 2/5] RFC: eeprom: at24: Allow passing gpiodesc from pdata Linus Walleij
2018-06-20 0:45 ` Andy Shevchenko
2018-06-18 7:45 ` [PATCH 3/5] RFC: spi: Make of_find_spi_device_by_node() available Linus Walleij
2018-06-18 7:45 ` [PATCH 4/5] RFC: bus: 96boards Low-Speed Connector Linus Walleij
2018-06-19 11:19 ` [Dev] " Daniel Thompson
2018-06-18 7:45 ` [PATCH 5/5] RFC: ARM64: dts: Add Low-Speed Connector to ZCU100 Linus Walleij
2018-06-19 14:55 ` Rob Herring
2018-06-22 13:22 ` Michal Simek
2018-06-18 12:21 ` [PATCH 0/5] RFC: Mezzanine handling for 96boards Arnd Bergmann
2018-06-18 13:22 ` Ard Biesheuvel
2018-06-18 14:15 ` Arnd Bergmann
2018-06-22 13:36 ` Michal Simek
[not found] ` <CAMuUZTG0q4f2T=+HjEijUCLb7KNXok9RJHOXOKNs2iap5p7m5Q@mail.gmail.com>
2018-06-19 15:25 ` [Dev] " Ard Biesheuvel
[not found] ` <CAMuUZTHOuzQm3y-yF6cad9y1UgsK+6R2w7vSzz7MkkYCdYd3hA@mail.gmail.com>
2018-06-19 15:30 ` Ard Biesheuvel
[not found] ` <CAMuUZTH8wXhoBSKwsCFBRBzAvvBBTUTnkmwKEpq=56=URo7kjQ@mail.gmail.com>
2018-06-22 13:08 ` Michal Simek [this message]
2018-06-26 9:10 ` Linus Walleij
2018-06-26 8:09 ` Linus Walleij
2018-06-26 8:19 ` Ard Biesheuvel
2018-06-26 8:36 ` Linus Walleij
2018-06-26 8:02 ` Linus Walleij
2018-06-26 8:08 ` Arnd Bergmann
2018-06-26 12:12 ` Mark Brown
2018-06-19 11:10 ` [Dev] " Daniel Thompson
2018-06-19 11:56 ` Mark Brown
2018-06-19 15:52 ` Rob Herring
2018-06-21 13:02 ` Frank Rowand
2018-06-26 9:03 ` Linus Walleij
2018-06-26 9:00 ` Linus Walleij
2018-06-27 15:23 ` [Dev] " Rob Herring
2018-06-28 6:10 ` Michal Simek
2018-06-21 12:58 ` Frank Rowand
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=616e99d3-b43e-58ca-aa82-eaf41f618682@xilinx.com \
--to=michal.simek@xilinx.com \
--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 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).