Skip to content

Conversation

@mateusz-holenko
Copy link
Contributor

This adds LiteX GPIO driver and enables it in litex_vexriscv board.

@zephyrbot
Copy link

zephyrbot commented Aug 6, 2019

All checks are passing now.

Review history of this comment for details about previous failed status.
Note that some checks might have not completed yet.

galak
galak previously requested changes Aug 6, 2019
Copy link
Contributor

@galak galak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor change to DTS binding.

@galak
Copy link
Contributor

galak commented Aug 7, 2019

You'll need the fix in:

#18089

Also, instead of nrgpios we need to make ngpios (sorry for the churn on that).

@galak
Copy link
Contributor

galak commented Aug 7, 2019

You'll need the fix in:

#18089

Also, instead of nrgpios we need to make ngpios (sorry for the churn on that).

Re-based and fixed up the yaml to be ngpios

@mateusz-holenko
Copy link
Contributor Author

You'll need the fix in:
#18089
Also, instead of nrgpios we need to make ngpios (sorry for the churn on that).

Re-based and fixed up the yaml to be ngpios

Thanks.

@mateusz-holenko
Copy link
Contributor Author

I fixed the base addresses of gpio ports in the DTS.

@mateusz-holenko
Copy link
Contributor Author

@galak Is there anything else I should do to have this PR merged?

@kgugala kgugala force-pushed the litex_gpio branch 2 times, most recently from 05e2fce to 758db80 Compare September 11, 2019 16:32
@mateusz-holenko
Copy link
Contributor Author

@galak The code is rebased on top of the 2.0.0 release and all requested changes are applied. Can we merge it?

@mateusz-holenko
Copy link
Contributor Author

Rebased to resolve conflicts after merging #18649.

@zephyrbot
Copy link

zephyrbot commented Sep 23, 2019

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.

@mateusz-holenko
Copy link
Contributor Author

@galak Is there something blocking this PR from being merged?

@galak
Copy link
Contributor

galak commented Oct 1, 2019

@galak Is there something blocking this PR from being merged?

We should migrate it to the new GPIO apis in the 'topic-gpio' branch. See issue #18530

@mateusz-holenko
Copy link
Contributor Author

@mnkp You are right - I had pushed a wrong branch. Sorry for the confussion.

It's fixed now - the current version is using the new GPIO API and the PR is now targetting topic-gpio branch.

Copy link
Member

@mnkp mnkp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like this PR is missing updates of the soc .dts file.

@PiotrZierhoffer
Copy link
Contributor

@mnkp you mention lack of changes to the soc dts. I believe the relevant changes are in riscv32-litex-vexriscv.dtsi. Am I missing something?

@mnkp
Copy link
Member

mnkp commented Nov 5, 2019

@mnkp you mention lack of changes to the soc dts. I believe the relevant changes are in riscv32-litex-vexriscv.dtsi. Am I missing something?

Yes, they are. Sorry, I somehow overlooked the file.

@PiotrZierhoffer
Copy link
Contributor

@mnkp the requested changes are implemented, tested and pushed.

@galak
Copy link
Contributor

galak commented Nov 13, 2019

Can you rebase this on topic-gpio thanks.

@mateusz-holenko mateusz-holenko force-pushed the litex_gpio branch 2 times, most recently from ea64d74 to c0350aa Compare November 14, 2019 08:00
@mateusz-holenko
Copy link
Contributor Author

@galak It's rebased

@carlescufi
Copy link
Member

@galak can you take another look?

@carlescufi
Copy link
Member

@galak @pabigot can we merge this?

@pabigot pabigot changed the title Add LiteX GPIO driver [TOPIC-GPIO] Add LiteX GPIO driver Nov 25, 2019
Copy link
Contributor

@pabigot pabigot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have this board and haven't inspected this closely, and a quick search didn't locate any documentation (was curious about only having 4 GPIO signals supported).

Assuming it passes both tests the only thing that I'd recommend doing is below. I won't insist on it since the issue's likely to be fixed before the topic branch merges.

Copy link
Contributor

@galak galak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor dts binding update needed.

This commits adds GPIO driver for LiteX SoC builder.

Due to the fact that GPIO in LiteX is unidirectional and can be
configured with different pins amount per port, additional entries
were added to the dts file.

Signed-off-by: Robert Winkler <[email protected]>
Signed-off-by: Mateusz Holenko <[email protected]>
Signed-off-by: Piotr Zierhoffer <[email protected]>
Enable LiteX GPIO driver in litex_vexriscv board.

Signed-off-by: Robert Winkler <[email protected]>
Signed-off-by: Mateusz Holenko <[email protected]>
Signed-off-by: Piotr Zierhoffer <[email protected]>
@galak galak merged commit 8f41c2f into zephyrproject-rtos:topic-gpio Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants