media: i2c: imx415: Correct hmax_min values for 891Mbps/lane#6750
Merged
pelwell merged 2 commits intoraspberrypi:rpi-6.12.yfrom Apr 2, 2025
Merged
media: i2c: imx415: Correct hmax_min values for 891Mbps/lane#6750pelwell merged 2 commits intoraspberrypi:rpi-6.12.yfrom
pelwell merged 2 commits intoraspberrypi:rpi-6.12.yfrom
Conversation
I obviously backported V1 of the patchset sent to mainline, as code review there picked up these incorrect hmax_min values. https://lore.kernel.org/all/AS4PR08MB773533B9D04BE15F51548FEBF7182@AS4PR08MB7735.eurprd08.prod.outlook.com/ The upstream patches also fixed a return without pm_runtime_put and the fall-through from V4L2_CID_VBLANK to V4L2_CID_EXPOSURE not updating ctrl, so the wrong exposure would get set. Backport these fixes from mainline. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
Changing clock source also requires changing the link frequency. Add a single override that does both for Waveshare modules that are now using 37.125MHz clocks instead of 24MHz. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
popcornmix
added a commit
to raspberrypi/firmware
that referenced
this pull request
Apr 2, 2025
…se HATs See: raspberrypi/linux#6758 kernel: ads7846 touch overlay fixups See: raspberrypi/linux#6760 kernel: staging: bcm2835-camera: Initialise dev in v4l2_dev See: raspberrypi/linux#6754 kernel: media: i2c: imx415: Correct hmax_min values for 891Mbps/lane See: raspberrypi/linux#6750 kernel: PCI: pcie-brcmstb: fake MSIx support on internal MSI target See: raspberrypi/linux#6761 kernel: DRM fixes for cropping P030/SAND128 on Pi5 See: raspberrypi/linux#6741 kernel: Show process name in set_mempolicy() ignored message See: raspberrypi/linux#6762
popcornmix
added a commit
to raspberrypi/rpi-firmware
that referenced
this pull request
Apr 2, 2025
…se HATs See: raspberrypi/linux#6758 kernel: ads7846 touch overlay fixups See: raspberrypi/linux#6760 kernel: staging: bcm2835-camera: Initialise dev in v4l2_dev See: raspberrypi/linux#6754 kernel: media: i2c: imx415: Correct hmax_min values for 891Mbps/lane See: raspberrypi/linux#6750 kernel: PCI: pcie-brcmstb: fake MSIx support on internal MSI target See: raspberrypi/linux#6761 kernel: DRM fixes for cropping P030/SAND128 on Pi5 See: raspberrypi/linux#6741 kernel: Show process name in set_mempolicy() ignored message See: raspberrypi/linux#6762
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I obviously backported V1 of the patchset sent to mainline, as code review there picked up these incorrect hmax_min values. https://lore.kernel.org/all/AS4PR08MB773533B9D04BE15F51548FEBF7182@AS4PR08MB7735.eurprd08.prod.outlook.com/
The upstream patches also fixed a return without pm_runtime_put and the fall-through from V4L2_CID_VBLANK to V4L2_CID_EXPOSURE not updating ctrl, so the wrong exposure would get set.
Backport these fixes from mainline.