Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp565941rwe; Wed, 31 Aug 2022 07:24:44 -0700 (PDT) X-Google-Smtp-Source: AA6agR5f2ZY7Y+xyRr53u6mLwQoqV8p5vDul2g3eKNzMtNqvB4ZY3g3CVhNkKTU8YzOlVZFU8jAN X-Received: by 2002:a17:902:d509:b0:16f:1e1:2067 with SMTP id b9-20020a170902d50900b0016f01e12067mr25588443plg.140.1661955883762; Wed, 31 Aug 2022 07:24:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661955883; cv=none; d=google.com; s=arc-20160816; b=IpRpOM/Ago++B5G3AUGjZeBYz41tvyCW6IcT/jqbo/0p2rd+euJkPMHn+VbecjamQO PErQ6rUd0tWr04PEUGGEcdpaStDniftnXz/K1h6Z3JGAIJlUbmIjDPmDWzXyLWWl5Gbo mbOmNH2d2BYc4Q8IW8n+UnVOtiY0Glx+jg5/iDmvqKal4hvucrtA5htiKuPyrFk2j1uD sGsQJFqs2F+7/jJmDxNOQ6GpOcKCy1ZzqBTql7tsPVZRbJbmgR5hiRglYmsRSu7mrg2D hhcOyBqTWSsOom0C213V0oGcOK86bzBpvPo5ScWfql3GsoBHnQmosCNvInMiefunEDRO VRxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:to:subject:message-id :date:from:in-reply-to:references:mime-version:dkim-signature; bh=eZUGFtAXuMZe17yfW6JNbiEkQsTCCgOHBT1JKffcwUg=; b=yAs0kYUVtbt7qMH57A8eRkRfkCz/AS9OR/vPGsFTZ3mLMRqHGdhT10IIidajtwOHhL QlcyzNrL62Qysxo+pVkFkh/jnyooPmuzhmcoyBLE/TxdwnrSJlCIHP3zoa+Ub/Wv587s nC1s+6FRza7+zJDDnhfueG4u8ImQGduTQU8G+DOH/NwCm/GNGO+9Qd6PJJe1z3Dw0M4O sShfbIMC9Yh48iEc4l7My0nKvwWjqf6ILNDcx+uOeFDpxWc08Xm7UFyXiJE166oCNLrd ZwVUs7yOOUXYmt/VwcaublyVS4zl/J7JCL+VyAphHGuHFMv9tCoAydv9pNOm1xpzNx81 NJbQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=SmwgurGV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b6-20020a170902d50600b0016f24553b11si403296plg.399.2022.08.31.07.24.31; Wed, 31 Aug 2022 07:24:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=SmwgurGV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231672AbiHaNoU (ORCPT + 99 others); Wed, 31 Aug 2022 09:44:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231570AbiHaNoO (ORCPT ); Wed, 31 Aug 2022 09:44:14 -0400 Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF7E3D51C0; Wed, 31 Aug 2022 06:43:54 -0700 (PDT) Received: by mail-vs1-xe30.google.com with SMTP id 190so14615891vsz.7; Wed, 31 Aug 2022 06:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date; bh=eZUGFtAXuMZe17yfW6JNbiEkQsTCCgOHBT1JKffcwUg=; b=SmwgurGVQ4BQOkrnJvaAD2p2aRFTuv1CS10HZuma0LOGm+P2RFJW8nq6tz9LQVLhS1 FUilQ94YCgld+4rpEfGMx1wj2mxqjPL2pPP6k3Y+yph4qnvhRERyJ6g82NPfH0oZTWsu 3m60kLAhVCMBUuP2LsU0i75kogfhMypx9mxFx8y+xwXkJDdeGqo5l1IRsOJedd+/fs1i asNd4zd9f/q+HIzurJ47VVv1MpubCdLhYYHu/Gyo3rOXSgGkH2wcuK6nlRHwAhHVP4aN ZA1XvtelmkFYNW7jj4WXQofkIwDaYg1WdW3sz5B0NwvhoWlInNWN7du6AFf/v1Iz5UZ/ 4TQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=eZUGFtAXuMZe17yfW6JNbiEkQsTCCgOHBT1JKffcwUg=; b=E8GYCtpjDXUwctnpC2CzdIrLGixahpHI7QRpdies0R300DbMdr0rcfM4HVJxdmQ4es 4Q4sFKh91XVsPSXfa1z275xj+nfsxq2u/1zX70MVtfT7YuZ3q0L1zFub4Yi2TiwopFWB djuTv0Q6LvpvQkYJ2ousEZqgCaSXbN6D0nDVFbrsNbuYgZCIlh5pcXAY7gTtbKkRqT/n aY9hZ10olSf5MZOKkcQjlVOLfbcyhZdoWNhPnVjnNbdE+FPIeuwTEA+KxP0JHWwyquFF KyBppPOkCM1j3qgs1afEkstfxCZPGe3AI381D/u5k4SFidz9gm/f2Y8D3Resgwq14+RS QmHQ== X-Gm-Message-State: ACgBeo2+P8xHn5bbYKcxlrZYkuKDeYSKKmuxVs74Wzz8AK4b5CnxtZqS n3ArG8jvx0dGjmLLN/0mONn3FOlQVAMdk5BLZ70= X-Received: by 2002:a67:b808:0:b0:388:b23e:8395 with SMTP id i8-20020a67b808000000b00388b23e8395mr6829657vsf.64.1661953432805; Wed, 31 Aug 2022 06:43:52 -0700 (PDT) MIME-Version: 1.0 References: <20220818125027.1131-1-yongsuyoo0215@gmail.com> In-Reply-To: <20220818125027.1131-1-yongsuyoo0215@gmail.com> From: =?UTF-8?B?7Jyg7Jqp7IiY?= Date: Wed, 31 Aug 2022 22:43:44 +0900 Message-ID: Subject: Re: [PATCH] media: dvb_ca_en50221: A bug is fixed for size write To: mchehab@kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, yongsu.yoo@lge.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear All Can you share how this patch is going ? 2022=EB=85=84 8=EC=9B=94 18=EC=9D=BC (=EB=AA=A9) =EC=98=A4=ED=9B=84 9:50, Y= ongSu Yoo =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > > Signed-off-by:Yongsu Yoo > > The function of "dvb_ca_en50221_write_data" at source/drivers/media > /dvb-core/dvb_ca_en50221.c is used for two cases. > The first case is for writing APDU data in the function of > "dvb_ca_en50221_io_write" at source/drivers/media/dvb-core/ > dvb_ca_en50221.c. > The second case is for writing the host link buf size on the > Command Register in the function of "dvb_ca_en50221_link_init" > at source/drivers/media/dvb-core/dvb_ca_en50221.c. > In the second case, there exists a bug like followings. > In the function of the "dvb_ca_en50221_link_init", > after a TV host calculates the host link buf_size, > the TV host writes the calculated host link buf_size on the > Size Register. > Accroding to the en50221 Spec (the page 60 of > https://dvb.org/wp-content/uploads/2020/02/En50221.V1.pdf), > before this writing operation, the "SW(CMDREG_SW)" flag in the > Command Register should be set. We can see this setting operation > in the function of the "dvb_ca_en50221_link_init" like below. > ... > if ((ret =3D ca->pub->write_cam_control(ca->pub, slot, > CTRLIF_COMMAND, IRQEN | CMDREG_SW)) !=3D 0) > return ret; > ... > But, after that, the real writing operation is implemented using > the function of the "dvb_ca_en50221_write_data" in the function of > "dvb_ca_en50221_link_init", and the "dvb_ca_en50221_write_data" > includes the function of "ca->pub->write_cam_control", > and the function of the "ca->pub->write_cam_control" in the > function of the "dvb_ca_en50221_wrte_data" does not include > "CMDREG_SW" flag like below. > ... > if ((status =3D ca->pub->write_cam_control(ca->pub, slot, > CTRLIF_COMMAND, IRQEN | CMDREG_HC)) !=3D 0) > ... > In the above source code, we can see only the "IRQEN | CMDREG_HC", > but we cannot see the "CMDREG_SW". > The "CMDREG_SW" flag which was set in the function of the > "dvb_ca_en50221_link_init" was rollbacked by the follwoing function > of the "dvb_ca_en50221_write_data". > This is a bug. and this bug causes that the calculated host link buf_size > is not properly written in the CI module. > Through this patch, we fix this bug. > --- > drivers/media/dvb-core/dvb_ca_en50221.c | 12 +++++++----- > 1 file changed, 7 insertions(+), 5 deletions(-) > > diff --git a/drivers/media/dvb-core/dvb_ca_en50221.c b/drivers/media/dvb-= core/dvb_ca_en50221.c > index 15a08d8c69ef..13f249b0a080 100644 > --- a/drivers/media/dvb-core/dvb_ca_en50221.c > +++ b/drivers/media/dvb-core/dvb_ca_en50221.c > @@ -187,7 +187,7 @@ static void dvb_ca_en50221_thread_wakeup(struct dvb_c= a_private *ca); > static int dvb_ca_en50221_read_data(struct dvb_ca_private *ca, int slot, > u8 *ebuf, int ecount); > static int dvb_ca_en50221_write_data(struct dvb_ca_private *ca, int slot= , > - u8 *ebuf, int ecount); > + u8 *ebuf, int ecount, int size_write= _flag); > > /** > * findstr - Safely find needle in haystack. > @@ -370,7 +370,7 @@ static int dvb_ca_en50221_link_init(struct dvb_ca_pri= vate *ca, int slot) > ret =3D dvb_ca_en50221_wait_if_status(ca, slot, STATUSREG_FR, HZ = / 10); > if (ret) > return ret; > - ret =3D dvb_ca_en50221_write_data(ca, slot, buf, 2); > + ret =3D dvb_ca_en50221_write_data(ca, slot, buf, 2, CMDREG_SW); > if (ret !=3D 2) > return -EIO; > ret =3D ca->pub->write_cam_control(ca->pub, slot, CTRLIF_COMMAND,= IRQEN); > @@ -778,11 +778,13 @@ static int dvb_ca_en50221_read_data(struct dvb_ca_p= rivate *ca, int slot, > * @buf: The data in this buffer is treated as a complete link-level pac= ket to > * be written. > * @bytes_write: Size of ebuf. > + * @size_write_flag: A flag on Command Register which says whether the l= ink size > + * information will be writen or not. > * > * return: Number of bytes written, or < 0 on error. > */ > static int dvb_ca_en50221_write_data(struct dvb_ca_private *ca, int slot= , > - u8 *buf, int bytes_write) > + u8 *buf, int bytes_write, int size_w= rite_flag) > { > struct dvb_ca_slot *sl =3D &ca->slot_info[slot]; > int status; > @@ -817,7 +819,7 @@ static int dvb_ca_en50221_write_data(struct dvb_ca_pr= ivate *ca, int slot, > > /* OK, set HC bit */ > status =3D ca->pub->write_cam_control(ca->pub, slot, CTRLIF_COMMA= ND, > - IRQEN | CMDREG_HC); > + IRQEN | CMDREG_HC | size_writ= e_flag); > if (status) > goto exit; > > @@ -1508,7 +1510,7 @@ static ssize_t dvb_ca_en50221_io_write(struct file = *file, > > mutex_lock(&sl->slot_lock); > status =3D dvb_ca_en50221_write_data(ca, slot, fr= agbuf, > - fraglen + 2); > + fraglen + 2, 0= ); > mutex_unlock(&sl->slot_lock); > if (status =3D=3D (fraglen + 2)) { > written =3D 1; > -- > 2.17.1 >