On Thu, Jul 23, 2015 at 04:35:46PM -0700, Rodrigo Vivi wrote:
> If we got to the point where we are trying to stop sink CRC
> the main output of this function was already gotten properly,
> so don't return the error and let userspace use the crc data.
>
> Let's replace the errnos returns with some log messages.
So, up to this commit, there's no way to know that an error has ocurred
and the next CRC calculation can go wrong.
I know that in a follow up patch this is fixed by trying to stop the
calculation at the beginning too, but just pointing out that this one
specifically has this problem.
Not sure if this is a problem though, since the patches are submitted
together. If not, then
Reviewed-by: Rafael Antognolli <rafael.antognolli@xxxxxxxxx>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 70a4a37..44f8a32 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4021,12 +4021,12 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
>
> stop:
> if (drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK, &buf) < 0) {
> - ret = -EIO;
> + DRM_DEBUG_KMS("Sink CRC couldn't be stopped properly\n");
> goto out;
> }
> if (drm_dp_dpcd_writeb(&intel_dp->aux, DP_TEST_SINK,
> buf & ~DP_TEST_SINK_START) < 0) {
> - ret = -EIO;
> + DRM_DEBUG_KMS("Sink CRC couldn't be stopped properly\n");
> goto out;
> }
> out:
> --
> 2.1.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Rafael
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
