Skip to content
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

Timing requirements for a chain of mcontrol load address triggers #1011

Open
en-sc opened this issue Apr 24, 2024 · 2 comments
Open

Timing requirements for a chain of mcontrol load address triggers #1011

en-sc opened this issue Apr 24, 2024 · 2 comments

Comments

@en-sc
Copy link
Contributor

en-sc commented Apr 24, 2024

[5.7.11. Match Control (mcontrol, at 0x7a1)] states:

A chain of triggers that don’t all have the same timing value will never fire. That means to implement
the suggestions in Table 11, both timings should be supported on load address triggers.

Is this correct? Seems like it's enough to support timing == before (0) since [Table 11. Suggested Trigger Timings] recommends timing == before for Load Address triggers.

@rtwfroody
Copy link
Collaborator

To implement the suggested timings, load address triggers need:

  1. timing=before, to implement a simple load address before
  2. timing=after, to implement load address + data after

Which means that load address triggers need both before and after timing support. Does that make sense?

@en-sc
Copy link
Contributor Author

en-sc commented Apr 26, 2024

Oh, I see, I have misunderstood.
So That means to implement the suggestions in Table 11... implies all suggestions from the table.
Maybe something like:

That means to implement the suggestions in Table 11, both timings should be supported on a load address trigger if it can be chained with a load data trigger.

would be more clear?

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

No branches or pull requests

2 participants