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

driver-architecture: bus infrastructure is itself a framework #243

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arnout
Copy link
Contributor

@arnout arnout commented May 6, 2024

This is explained much later in the training, but I think it's important to mention this early on already. Otherwise, things that are explained immediately afterwards don't make much sense (e.g. the fact that you have a struct device twice: once for the bus and once for the functional framewoek).

While using the bootlin materials for an internal training, there are a few improvements I made (at least, I consider them improvments myself). Since you probably don't agree with all of them, I'm making separate PRs for each. Feel free to close the PR if you disagree with the idea.

This is explained much later in the training, but I think it's important
to mention this early on already. Otherwise, things that are explained
immediately afterwards don't make much sense (e.g. the fact that you
have a struct device twice: once for the bus and once for the functional
framewoek).

Signed-off-by: Arnout Vandecappelle <[email protected]>
Copy link
Contributor

@miquelraynal miquelraynal left a comment

Choose a reason for hiding this comment

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

It is totally true we don't explain well the fact that we have in the end several struct devices for the same physical device, but:

  • it's not always the case (welcome in the kernel world)
  • it feels way too early here before we can talk about this

However I would suggest to add your modified figure when we talk about the device model being recursive? We could maybe even have a bit of text explaining the double struct device thing there. This way the learning curve is not too steep at the very beginning.

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.

2 participants