MBus DT binding: A new hope
Get series with b4
b4 am [email protected]Versions newest first
- v5 Latest0 of 12 patches 0 repliesNew
Patches in v5 No applies recorded yet
None of the 12 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCH v5 00/12] MBus DT binding: A new hope
Quoted 4 lines · Ezequiel Garcia
In the current proposal we have now required a 'controller' property to specify the MBus controller MMIO registers. To us this looks more appropriate, since the MBus registers are effectively located within the internal register region, behind the so-called internal-regs window.
Interesting, seems reasonable to me.
Quoted 7 lines
Personally, I can't see any disadvantage, and the binding looks much cleaner now. But of course I can be wrong, and I'm open to discussion.
There's another pending issue. Arnd Bergmann has required to add a property to specify the available space within the CPU address space for decoding windows. This property would allow to support fully dynamic mbus window allocation.
I wonder if this range is implied - eg it is address space not covered by the memory node or any mbus ranges? Is there a situation where that is not sufficient?
Quoted 7 lines
For now, this property is intentionally missing, and I expect that it can be added in the future, together with the full-dynamic MBus implementation.
@Arnd, @Jason: Given the v4 patchset didn't receive any comments but wasn't accepted either, I'd like to know which other pending issues I'm forgetting to address.
I took a quick look and it seems to match what was discussed..
Regards,
Jason