From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Addressing Complex Dependencies - Tuesday 9:30am - Coronado/Devargas
Date: Mon, 31 Oct 2016 11:35:53 -0700 [thread overview]
Message-ID: <CAB=NE6Wo-mWdJF8k9yGcsORatpNtiiug+jXdGP60xhd0F+jydg@mail.gmail.com> (raw)
[ Note: Plumbers attendees are welcomed to participate in KS tech topics ]
The tech topic thread of addressing complex dependencies was pretty
broad, I've gone over most of the thread and have tried to condense
most ideas discussed into categories. There were four related work
items I had originally noted but Andrzej Hajda also had mentioned his
own work, below they are all together:
* Functional dependencies (now merged on Greg's tree)
* Resource tracking / allocation framework
* Media controller feature graph
* Linker tables
* Async probe
Other topics brought up:
* Probe ordering
* Generic drivers
And lastly these related subjects were also mentioned which have a
direct impact to dependency relationships:
* Device hierarchy (just not a tree but a graph)
* Handling cycles on the graph
* Graph Cycle solution proposals
There was some overlap in interest between a bit of Audio workshop
folks and this session so we've made arrangements to address only the
shared topics of interest together with the Audio folks at the Audio
workshop first at Sweeney Ballroom CDE, and then move on to address
the rest of the topics in the room assigned for addressing complex
dependencies, Coronado/Devargas.
The shared topics then we will address first at 9:30am are:
* Generic drivers
* Device hierarchy (just not a tree but a graph)
* Handling cycles on the graph
* Graph Cycle solution proposals
After this is covered we can move on to Coronado/Devargas to adress
the rest of the remaining topics:
* Functional dependencies (now merged on Greg's tree)
* Resource tracking / allocation framework
* Media controller feature graph
* Linker tables
* Async probe
Luis
next reply other threads:[~2016-10-31 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 18:35 Luis R. Rodriguez [this message]
2016-10-31 19:32 ` James Bottomley
2016-10-31 22:00 ` Luis R. Rodriguez
2016-11-01 17:56 ` Grant Likely
2016-11-02 3:48 ` Rafael J. Wysocki
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='CAB=NE6Wo-mWdJF8k9yGcsORatpNtiiug+jXdGP60xhd0F+jydg@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.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