Mezzanine Low Speed connector bus
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4 v1] Mezzanine Low Speed connector bus
Quoted 23 lines · Linus Walleij
Quoted 22 lines · Frank Rowand
Quoted 4 lines · Frank Rowand
Quoted 3 lines · Linus Walleij
I have been a bit hesitant to reiterate the series, but this is anyways a v1 of the 96Boards Mezzanine Low Speed connector driver framework.
< snip >
Quoted 4 lines
I will read through the rest of the series and revisit my previous conclusions, but most likely not for a few days.
-Frank
< snip >
My apologies for continuing to not getting to this task. It has been in the top grouping of my todo list but has been pushed aside by a rather busy schedule of conferences and company internal work. It remains up at the top of my todo list, but most likely will still be shunted aside for three more weeks of other pressing work.
Quoted 6 lines
Quoted 1 line
I will get to it, I definitely have not forgotten it.
It's OK, I might get to rebasing the series even.
We discussed it in a session with Linaro in Vancouver recently (some month ago). What we took away from it
It would be helpful for me to look at that. What was the title of the session, or a pointer to the resource page for it?
-Frank
Quoted 19 lines
is that there are many precedents of populating devices ad hoc, what really makes this one special is that it takes something device tree and ad hoc populates something on top of it, not defined in the device tree itself.
On a related note, Heikki Krogerus is making a software FWnode population series. I ran into this when converting board files to use more abstract descriptions. Check it out:
https://marc.info/?l=linux-kernel&m=154177331200561&w=2The idea with the series is to expand FWnode so that it doesn't only populate Linux devices from device tree or ACPI but also by software, where needed, further expanding the fwnode abstraction. I will probably look into using that.
Yours,
Linus Walleij