From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Brian Norris
<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Updated ePAPR specification?
Date: Thu, 26 Jun 2014 11:24:16 -0700 [thread overview]
Message-ID: <CAGVrzcZcLooRwP3yH=HxgaGNfVp6AbGdk9cqx7vvhsPgwv0BMA@mail.gmail.com> (raw)
Hi all,
During ELC 2014 in San Jose, we quickly talked about whether there is
a need for an updated ePAPR specification that would cover the new
bindings that Linux has been adopting.
I think Olof had some concerns about how a committee-driven approach
might make things more complex than they need to be.
Still, I feel like there is some room for standardizing some of the
new bindings Linux has been coming up with, in particular:
- clocks bindings
- DMA bindings
- (S)IOMMU bindings
and a bunch of updates to existing specification (e.g: new Ethernet
PHY types such as "xgmii").
If we were serious about doing this, how would you recommend we move
forward, should we aim at doing something similar to the virtio
specification and publish an update Device Tree binding specification
as part of an OASIS working group?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-06-26 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 18:24 Florian Fainelli [this message]
[not found] ` <CAGVrzcZcLooRwP3yH=HxgaGNfVp6AbGdk9cqx7vvhsPgwv0BMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-27 8:02 ` Updated ePAPR specification? Pawel Moll
2014-06-28 4:52 ` 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='CAGVrzcZcLooRwP3yH=HxgaGNfVp6AbGdk9cqx7vvhsPgwv0BMA@mail.gmail.com' \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).