Thanks for adding me Shelly!
Hey Paul,
I work on Arbitrage. Currently it is an internal tool because it uses non-public data (such as schematics). We do not currently have plans to open source it because it has limited usefulness without these data sources.
To give a bit more detail into how it works, Arbitrage uses a combination of digital datasheet information, schematic information, and hueristics to generate the gpio.c files based on what it thinks a pin is being used for.
This tool is still relatively new so it's not being used for all boards yet, but hopefully more gpio.c files will be generated by Arbitrage in the future.
Hope this is helpful! Rachel
On Mon, Oct 30, 2023, 3:27 PM Shelley Chen shchen@google.com wrote:
+Rachel Nancollas rachelsn@google.com
On Fri, Oct 27, 2023, 10:52 PM Paul Menzel pmenzel@molgen.mpg.de wrote:
Dear coreboot folks,
Today, in commit 952a4473ec23 (mb/google/brox: Add Arbitrage generated gpio.c file) [1], I first read consciously about the tool Arbitrage:
mb/google/brox: Add Arbitrage generated gpio.c file
Checking in gpio.c generated by arbitrage. Used this command line to generate: arb export-coreboot-gpio --refdes=U1 brox:proto1_20231017
Commit dbc904b26768 (mb/google/brya/var/ghost: Add auto-generated GPIO config from Arbitrage) [2], I found, where the tool is mentioned the first time, includes a description:
Arbitrage is an internal tool at Google to work with schematics programatically. In particular, it features an "export-coreboot-gpio" command, which, does it's best to try and make a gpio.c from the schematics to avoid human errors when translating to C code.
It’d be great, if you could share more details, and if there are plans to make it public. Also, is that tool used to create `gpio.c` for all boards?
Kind regards,
Paul
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org