-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a gpio pinmap #10644
Add a gpio pinmap #10644
Conversation
@fkjagodzinski, thank you for your changes. |
This is consistent with the rest of pinmap API. On the other hand, there's a bit of ROM taken to hold the entire gpio table (some chips are large - have lot of pins). @ARMmbed/mbed-os-hal Please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments, but the change looks good to me. @0xc0170 the extra ROM usage should only be for testing, so even for large devices this shouldn't be a problem.
targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_MCU_K64F/TARGET_FRDM/PeripheralNames.h
Show resolved
Hide resolved
{PTE11, GPIO_E, 1}, | ||
{PTE12, GPIO_E, 1}, | ||
// {PTE24, GPIO_E, 1}, // fixed pull-up (for I2C) | ||
// {PTE25, GPIO_E, 1}, // fixed pull-up (for I2C) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only applies to the pull up/down tests right? If so is there a way the GPIO tests could run all its normal testing on these pins except the pull up/down test?
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@fkjagodzinski Today is the day to complete this one :-) |
This was unnecessary since all the pins may be used independently.
I've updated the code as @c1728p9 suggested. This is ready for CI again. |
CI started |
Test run: FAILEDSummary: 2 of 11 test jobs failed Failed test jobs:
|
|
Two targets failed mbed-os/targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_KW24D/TARGET_FRDM/PinNames.h Line 103 in a4738fa
mbed-os/targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_KW41Z/TARGET_FRDM/PinNames.h Line 103 in a4738fa
I added a dedicated |
Ready to run CI tests again. |
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@maciejbocianski could you please review the additional changes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
How was it decided what pins go into the PinMap_GPIO array for each supported Freescale platform? |
I added pins based on the spec for each chip: My intention was to add every possible pin, so we could later comment out any unsupported ones if needed. |
Description
This is an alternative to #10459 -- instead of giving a list of pins to avoid, provide a list of pins that are suitable for all gpio tests.
This patch adds a
gpio_pinmap()
function that every target has to override to provide a set of pins for GPIO testing with the FPGA shield.Pull request type
Reviewers
@c1728p9 @maclobdell @0xc0170 @maciejbocianski
Release Notes
Add a weak
gpio_pinmap()
, that every target has to override, to provide a set of pins for GPIO testing.