mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Artem Chernyshev <artem.chernyshev@red-soft.ru>,
	Michael Ira Krufky <mkrufky@linuxtv.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media <linux-media@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH] [media] mxl111sf: Check return value in mxl111sf_config_mpeg_in
Date: Fri, 18 Aug 2023 16:32:44 +0200	[thread overview]
Message-ID: <1c00196c-e64e-119a-fd30-5e8f797c22ec@xs4all.nl> (raw)
In-Reply-To: <Y6XXF6gffL9aHTuw@localhost.localdomain>

On 23/12/2022 17:28, Artem Chernyshev wrote:
> Hi,
> On Fri, Dec 23, 2022 at 07:28:47AM -0500, Michael Ira Krufky wrote:
>> On Thu, Dec 22, 2022, 4:46 PM Artem Chernyshev <artem.chernyshev@red-soft.ru>
>> wrote:
>>
>>> Error check after mxl111sf_read_reg
>>>
>>> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>>>
>>> Fixes: 4c66c9205c07 ("[media] dvb-usb: add ATSC support for the Hauppauge
>>> WinTV-Aero-M")
>>> Signed-off-by: Artem Chernyshev <artem.chernyshev@red-soft.ru>
>>> ---
>>>  drivers/media/usb/dvb-usb-v2/mxl111sf-phy.c | 3 ++-
>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/media/usb/dvb-usb-v2/mxl111sf-phy.c
>>> b/drivers/media/usb/dvb-usb-v2/mxl111sf-phy.c
>>> index 40b26712ba4c..ad1888514bd0 100644
>>> --- a/drivers/media/usb/dvb-usb-v2/mxl111sf-phy.c
>>> +++ b/drivers/media/usb/dvb-usb-v2/mxl111sf-phy.c
>>> @@ -121,7 +121,8 @@ int mxl111sf_config_mpeg_in(struct mxl111sf_state
>>> *state,
>>>         mxl_fail(ret);
>>>
>>>         /* Configure MPEG Clock phase */
>>> -       mxl111sf_read_reg(state, V6_MPEG_IN_CLK_INV_REG, &mode);
>>> +       ret = mxl111sf_read_reg(state, V6_MPEG_IN_CLK_INV_REG, &mode);
>>> +       mxl_fail(ret);
>>>
>>>         if (clock_phase == TSIF_NORMAL)
>>>                 mode &= ~V6_INVERTED_CLK_PHASE;
>>> --
>>> 2.30.3
>>>
>>
>> Artem,
>>
>> Thank you for this.  If I recall correctly, the read from that particular
>> register often returns a failure despite the correct value being read into
>> memory. This needs to be tested before being merged, and if my memory is
>> correct about this we should add a comment about it. Unfortunately, I'm out
>> of town at the moment, I won't be able to test this for some time. Can we
>> hold off on this one for a bit? If you don't hear from me after a few
>> weeks, please feel free to ping me again. Thanks.
>>
>> Best,
>> Michael Krufky
>>
>>>
> 
> Thanks for reply. I'll be waiting for your decision

I'll drop this patch, I never saw a follow-up on this.

If this is really needed, then just resend.

Regards,

	Hans

> 
> Best regards,
> Artem


      reply	other threads:[~2023-08-18 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 21:46 Artem Chernyshev
     [not found] ` <CAOcJUby8i=vRu5-cSe6iBKrnLG8ucmatpiPT=VaMS9etwHH_uw@mail.gmail.com>
2022-12-23 16:28   ` Artem Chernyshev
2023-08-18 14:32     ` Hans Verkuil [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=1c00196c-e64e-119a-fd30-5e8f797c22ec@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=artem.chernyshev@red-soft.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=mchehab@kernel.org \
    --cc=mkrufky@linuxtv.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

all inboxes | Powered by JetHome®