Mec common gpio driver #99761
Mec common gpio driver #99761
Conversation
zephyrbot
added
area: GPIO
area: Interrupt Controller
platform: Microchip MEC
zephyrbot
requested review from
VenkatKotakonda,
dcpleung,
henrikbrixandersen,
nashif and
ycsin
|
Why is compliance check failing related to python script import ordering? |
|
Running check_compliance.py locally produces: and Do these tests require a specific Python version? |
scottwcpg
force-pushed
the
mec_common_gpio_driver
branch
from
3db36e2 to
7cfefa3
Compare
|
Had to install and configure a clean zephyr development environment using Python 3.10 not 3.11. |
|
@nashif @fabiobaltieri Does anyone know why check_compliance.py is failing? |
scottwcpg
force-pushed
the
mec_common_gpio_driver
branch
from
7cfefa3 to
c63c3bb
Compare
|
CI is running DeviceTree linter but local invocation of check_compliance.py is skipping the DeviceTree linter. Adding logging does not show why. Node.js npx and npm versions 10.9.3 are installed. |
|
Zephyr environment missing JS dts-linter module. Running npx command to link a single file triggered npx to request download of [email protected]. Local check_compliance.py now runs DeviceTree linter. |
Microchip MEC parts have a similar GPIO peripheral block. We create a unified driver for all parts. NOTE: MEC GPIO interrupt detection sets active status when changed from interrupt detect disabled to any enabled mode. Driver ISR and interrupt configuration implementation includes work-arounds for this issue. Signed-off-by: Scott Worley <[email protected]>
We added Microchip MEC15xx, MEC172x, MEC174x, and MEC175x evalutaion boards to the GPIO driver gpio_basic_api, gpio_api_1pin, and gpio_get_direction tests. Signed-off-by: Scott Worley <[email protected]>
scottwcpg
force-pushed
the
mec_common_gpio_driver
branch
from
c63c3bb to
050cb7a
Compare
|
2 participants
We are replacing the multiple GPIO drivers for Microchip MEC family with a single driver. The hardware is nearly identical in across MEC15xx and MEC172x/4x/5x SoCs.