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

drivers: media: pisp_be: Remove extras field from pisp_be_config #6140

Draft
wants to merge 1 commit into
base: rpi-6.6.y
Choose a base branch
from

Conversation

naushir
Copy link
Contributor

@naushir naushir commented May 1, 2024

Remove the various extras fields from struct pisp_be_config. These fields are not used by the driver nor the hardware, so do not belong in this structure.

Also put the tiles array at the top of struct pisp_be_tiles_config to ensure any size change to struct pisp_be_config does not move the tiles struct out of alignment.

This is a userland breaking change, and libpisp must be updated accordingly.

@naushir
Copy link
Contributor Author

naushir commented May 1, 2024

This will break userland, so best to merge this in together with the (soon to be) upstream changes.

@naushir
Copy link
Contributor Author

naushir commented May 1, 2024

@davidplowman and @njhollinghurst we won't merge this yet, but just a heads-up.

@naushir
Copy link
Contributor Author

naushir commented May 1, 2024

@jmondi this is something we should put into the next revision of your upstream driver.

@njhollinghurst
Copy link
Contributor

I'm definitely a bit nervous about the driver/UAPI change....

But while we're at it why don't we remove the I/O addresses (buffer configs) as well, and start from GLOBAL_BAYER_ENABLE? The driver will never touch those address fields (instead it uses dma_addr_t addrs[]). I think the "test HAL" does use them for index numbers for TDN/Stitch buffer cycling, but I'm sure we could come up with a different and no worse hack.

@naushir
Copy link
Contributor Author

naushir commented May 1, 2024

But while we're at it why don't we remove the I/O addresses (buffer configs) as well, and start from GLOBAL_BAYER_ENABLE? The driver will never touch those address fields (instead it uses dma_addr_t addrs[]). I think the "test HAL" does use them for index numbers for TDN/Stitch buffer cycling, but I'm sure we could come up with a different and no worse hack.

Done!

@jmondi
Copy link
Contributor

jmondi commented May 2, 2024

@jmondi this is something we should put into the next revision of your upstream driver.

I'll take this in and take the occasion to send a new version.

If mainline does not provide any additional feedback/comments on the driver, I'll send a pull request and that's it, the series has been there for quite some time. We're late already for the 6.10 merge window, but as soon as v6.10-rc1 is out, I'll make sure the driver is collected

Remove the various extras fields from struct pisp_be_config. These
fields are not used by the driver nor the hardware, so do not belong
in this structure.

Also put the tiles array at the top of struct pisp_be_tiles_config to
ensure any size change to struct pisp_be_config does not move the
tiles struct out of alignment.

This is a userland breaking change, and libpisp must be updated
accordingly.

Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
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.

None yet

3 participants