[Libre-soc-bugs] [Bug 846] Pinmux Pinspec Interconnect Auto-Generation

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Sat Oct 1 13:33:18 BST 2022


--- Comment #6 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Andrey Miroshnikov from comment #5)
> Here's the latest commit:
> https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/stage2.py;
> h=1669149e22bed1776e7aa7c9ace5772ca0a607f4;hb=HEAD

that's a file, not a commit diff.

  48         self.periph_ports = Array(temp)

that's extremely unlikely to need Array().  just = temp.

> "keys()" is a method you added to the Pinouts class (which PinSpec inherits)
> that internally calls .pins.keys().

to make it look like the standard python "dict" using Liskov Substitution
Principle, yes.

> ps.byspec <-- dict that has the signal names with IOType information
> Now that I have the information, I'll integrate it into the pinmux block by
> feeding PinSpec object directly!

excellent. getting there.

> There seems to be a strange recursive duplication.
> ps.items() gives the pin information (as ps is PinSpec and inherits Pinouts),
> but the same dict is returned by ps.gpio.pinouts.items()

good. one data structure is easily accessible from the other.

> Also added new sections to the pinmux doc (they may need to move around, but
> haven't focused on that yet), 4.1.1-4.1.4 covering the terminology and the
> PinSpec and Pinouts classes.


You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-soc-bugs mailing list