Hi,
Am 17.06.26 um 13:35 schrieb Keshavamurthy K [Firmware-NTL] via coreboot:
I would also appreciate some guidance on GPIO configuration for a new
board port. My understanding is that GPIOs must be adapted carefully
before any hardware testing. Is the recommended workflow still:
1. Boot the vendor firmware.
2. Use |util/inteltool| to dump GPIO/pad configuration.
3. Use |util/intelp2m| to generate the initial GPIO definitions.
yes.
4. Create the board-specific GPIO configuration and reference it
from the mainboard |.cb| files.
no.
You don't reference your GPIO config from the .cb file, but from the .c
source files. Look at other mainboards: gpio.h defines a configuration
object. Search for other files within that mainboard that *use* this
configuration object. This shows you how to apply GPIO config.
Are there any examples of recent Alder Lake or Raptor Lake mainboards
that demonstrate the preferred way of defining GPIO configuration in the
device tree (|.cb|) and corresponding |gpio.c|/|gpio.h| files?
yes. As I already suggested, `git grep soc/intel/alderlake`.
Best,
Florian
--
Florian Jung
Development
--
TUXEDO Computers GmbH
Alter Postweg 101 ~ D-86159 Augsburg
--
E-Mail: [email protected]
--
www.tuxedocomputers.com
--
Amtsgericht Augsburg: HRB 27755
USt-IdNr.: DE815420876
CEO: Herbert Feiler
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
