-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Add Low speed connector support for 96Boards IE boards #19751
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 Low speed connector support for 96Boards IE boards #19751
Conversation
|
All checks are passing now. Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages. |
b48a0fc to
dacbb42
Compare
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.
Please update boards documentation so we can quickly reach connector specification.
Otherwise, change is good.
Little hick up is that we miss sample to test that. Maybe we can add boards to tests/drivers/gpio/gpio_basi_api once topic-gpio branch is merged.
|
@erwango Okay, will add the link to 96Boards IE spec.
Sure. I can add that later. |
boards/arm/96b_carbon/96b_lscon.dtsi
Outdated
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.
Please also add gpio-map-mask props, cf #19862
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.
Done
dacbb42 to
77973ac
Compare
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.
sorry for the nit change, but change platform to platforms
All 96Boards complying to the IE spec exposes either 40pin or 30pin standard low speed connectors for peripheral connectivity. These connectors are well defined and available in the IE spec. So, lets create a devicetree binding for the most commonly used 30pin header for the 3.3v IE 96Boards. This binding will be utilized by the 96Boards for exposing the GPIO pins as nexus node as per the devicetree spec. This will allow the shields and applications to use board independent GPIO mapping. Signed-off-by: Manivannan Sadhasivam <[email protected]>
Add support for 3.3v Low speed connector available on the Wistrio board inorder to access peripherals in a board independent way. Following peripherals are supported: 1. 7-GPIOs 2. I2C0 3. UART0 Signed-off-by: Manivannan Sadhasivam <[email protected]>
Add support for 3.3v Low speed connector available on the Carbon board inorder to access peripherals in a board independent way. Following peripherals are supported: 1. 8-GPIOs 2. I2C0 3. SPI0 4. UART0 5. UART1 Signed-off-by: Manivannan Sadhasivam <[email protected]>
All 96Boards complying to the IE spec exposes either 40pin or 30pin standard low speed connectors for peripheral connectivity. These connectors are well defined and available in the IE spec. So, lets create a devicetree binding for the 40pin header for the 1.8v IE 96Boards. This binding will be utilized by the 96Boards for exposing the GPIO pins as nexus node as per the devicetree spec. This will allow the shields and applications to use board independent GPIO mapping. Signed-off-by: Manivannan Sadhasivam <[email protected]>
Add support for 1.8v Low speed connector available on the Wistrio board inorder to access peripherals in a board independent way. Following peripherals are supported: 1. 12-GPIOs 2. SPI0 3. UART0 Signed-off-by: Manivannan Sadhasivam <[email protected]>
77973ac to
7e519b4
Compare
|
Any updates on this? |
dbkinder
left a comment
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.
+1 for doc changes, thanks.
All 96Boards complying to the IE spec exposes either 40pin or 30pin
standard low speed connectors for peripheral connectivity. These
connectors are well defined and available in the IE spec [1]. This PR
creates two different gpio bindings for these connectors:
These bindings will be utilized by the 96Boards for exposing the
GPIO pins as nexus node as per the devicetree spec. This will allow
the shields and applications to use board independent GPIO mapping.
While at it, 96Boards generic node labels for I2C, SPI and UART are also
added.
[1] https://linaro.co/ie-specification
Fixes: #15598
Signed-off-by: Manivannan Sadhasivam [email protected]