Skip to content

Conversation

@luismarques
Copy link

No description provided.

Copy link

@rivos-eblot rivos-eblot left a comment

Choose a reason for hiding this comment

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

Seems mostly ok to me

@luismarques luismarques force-pushed the lc_ctrl_jtag branch 2 times, most recently from 62e6f92 to 33c4756 Compare November 9, 2025 15:58
@luismarques luismarques marked this pull request as ready for review November 9, 2025 16:09
Copy link

@AlexJones0 AlexJones0 left a comment

Choose a reason for hiding this comment

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

Thanks, this LGTM.

Copy link

@rivos-eblot rivos-eblot left a comment

Choose a reason for hiding this comment

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

LGTM, except the ABIS constant.

I think you need to update the documentation so that the LC / DMI interface is referenced for ot_earlgrey.md as it is for ot_darjeeling.md. You may also need to add a machine section to lc_ctrl_dmi.md in a similar manner done for example in of_flash.md:

## Machine specific options

### EarlGrey Machine
...

to document the new JTAG controller with an example for its chardev, see for example Remote bitbang protocol section in jtag-dm.md

* words on the TL-UL side, addressing [0 .. 2^7*4) bytes, and accessing the LC
* Ctrl registers at the appropriate (documented) offset.
*/
#define OT_EG_LC_CTRL_TAP_DMI_ABIS 7u

Choose a reason for hiding this comment

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

Is ABIS an ABITS typo (Address BITS) or is it referring to something else? (not enough coffee yet for me)

Copy link
Author

Choose a reason for hiding this comment

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

oops, that was a typo. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants