From: patchwork-bot+linux-arm-msm@kernel.org
To: Andrey Konovalov <andrey.konovalov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 0/3] media: qcom: camss: V4L2_CID_PIXEL_RATE/LINK_FREQ fixes
Date: Wed, 26 May 2021 19:03:24 +0000 [thread overview]
Message-ID: <162205580443.26840.6078755259949544437.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210303174250.11405-1-andrey.konovalov@linaro.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Wed, 3 Mar 2021 20:42:47 +0300 you wrote:
> The first patch adds printing a warning in v4l2_get_link_freq() if
> V4L2_CID_LINK_FREQ isn't implemented (this is a mandatory control for
> CSI-2 transmitter drivers [1], but many sensor drivers don't have it
> currently).
>
> The second patch is the start of the work discussed in the "[RFC] Repurpose
> V4L2_CID_PIXEL_RATE for the sampling rate in the pixel array" thread [2].
> I'll send the similar patches for the rest of CSI receiver drivers which
> use V4L2_CID_PIXEL_RATE to calculate the link frequency as a separate
> patchset following this one: I don't have the hardware to test the changes
> to these drivers, so the second patchset will be build tested only.
>
> [...]
Here is the summary with links:
- [v3,1/3] v4l: common: v4l2_get_link_freq: add printing a warning
https://git.kernel.org/qcom/c/67012d97df93
- [v3,2/3] media: camss: use v4l2_get_link_freq() to calculate the relevant clocks
https://git.kernel.org/qcom/c/78c2cc28df4a
- [v3,3/3] media: qcom: camss: Fix overflows in clock rate calculations
https://git.kernel.org/qcom/c/2f90857781bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-26 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 17:42 [PATCH v3 0/3] media: qcom: camss: V4L2_CID_PIXEL_RATE/LINK_FREQ fixes Andrey Konovalov
2021-03-03 17:42 ` [PATCH v3 1/3] v4l: common: v4l2_get_link_freq: add printing a warning Andrey Konovalov
2021-03-03 17:42 ` [PATCH v3 2/3] media: camss: use v4l2_get_link_freq() to calculate the relevant clocks Andrey Konovalov
2021-03-03 17:42 ` [PATCH v3 3/3] media: qcom: camss: Fix overflows in clock rate calculations Andrey Konovalov
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162205580443.26840.6078755259949544437.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).