Received: by 2002:ac0:c50a:0:0:0:0:0 with SMTP id y10csp1158905imi; Fri, 1 Jul 2022 04:27:52 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tWk2H0oXABrG8JRqICQPNkm9sJpoqvWZc+NbW2OEDHGdfjdypxnQAAcG4Dt133t4o5KFH4 X-Received: by 2002:aa7:da45:0:b0:437:de3d:8ca4 with SMTP id w5-20020aa7da45000000b00437de3d8ca4mr16201464eds.139.1656674872134; Fri, 01 Jul 2022 04:27:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656674872; cv=none; d=google.com; s=arc-20160816; b=YJ7yMZO3/tAQfKQwXy/B7nv0KOWKPvOX9Kh183ymK5M8P+2x/mf0COEMd9CM8LZjza IoMjwIrDYbJZoXO84oONMJ3LUyTI+axGqPC/oeXbHyFAlsqNmKoi3Q51Jzh0D4/oOSsn 2cjBtCNY2juX2utWZkDvLT8Y8JgVq4GF93EAD8fmQd6ntL0v+nAXF5gn0CIgxs+31bam nMMnlRhCQzlKlX/KRzMkENiQuYtp/RSnodJux9dlsCWVO2vCsQ5hlFLXynJbu0/WqGMT uSddVh8LGMsb9TE2BKPddi6PRziKXz1cH0rFakskBJW28remNlCs7lrNofZtEHsIoQmc Hgdw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=I4MDjjO8BzInQr5TM6t/zvnDVVooHxE4yuX82IM60po=; b=yBxBkNmF66OCKtsyb9/R9AxnmIfxhM8fQpqOOwy+Ae4kdUztes8vlcP3tesbqY9mFI O7dj5O/zMsLV730Rc8f8E0bnQfQCRGNEZxnobZKE865SRMY9LO2cKB4pL895WJMTVZVN KEDqbvb72NQuQz8k4ypOVuy/pk6oSjR0ve30vrIGqk+Kv9Nfn6VqTgZPGu7vSTrhPmGS 1A0ZHu9g63w6epEVoX+d+4ATM4+Ch9bUZk853vRzFrcxZ3tHnk5x/WJGom1DnV/UTWyX Q761dfJcTeyZlwkBWcpgZJUocNxPvomJ7X/OJLS4YRDVOjCiWGh4FsV2skL8IetFAyb3 RJ4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=F3QxikYl; 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=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qa41-20020a17090786a900b006fe9609be80si13054569ejc.870.2022.07.01.04.27.26; Fri, 01 Jul 2022 04:27:52 -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=@chromium.org header.s=google header.b=F3QxikYl; 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=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236585AbiGAKxS (ORCPT + 99 others); Fri, 1 Jul 2022 06:53:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50126 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235792AbiGAKxL (ORCPT ); Fri, 1 Jul 2022 06:53:11 -0400 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E64DD109D for ; Fri, 1 Jul 2022 03:53:09 -0700 (PDT) Received: by mail-pj1-x1032.google.com with SMTP id m14-20020a17090a668e00b001ee6ece8368so6040612pjj.3 for ; Fri, 01 Jul 2022 03:53:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=I4MDjjO8BzInQr5TM6t/zvnDVVooHxE4yuX82IM60po=; b=F3QxikYl5N3X8/xOvdJRq17w3/NvwpiHC3GsLbFy1xYBZcDslcuAXxxjAOmbRx+2Da JYZdAUyxWrab4Pt6Qpwnf19kDkkaaul5CO8fcfr5Lszh9rOuNFTCFUMOJl6sDAjDDbeT FnCw6/fhwibl1Y2uUb0unP3OSQTZgVklKjUgA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=I4MDjjO8BzInQr5TM6t/zvnDVVooHxE4yuX82IM60po=; b=lfiTGtjnWt86cNvPgTDWJRlTmlkfGSicCPbFjkE4+0YglzW6KLaa1N6Al8JcIfuNwQ MgKxBOWXctZQbFy/jNZYlAca88xyxD1QKWZLpsy7dHtRXPoTikjeV8iitcke1AT54GyT 1E/w1Zz8h1vQaIu24RIiZvczRZafsyrmYpGhcqgi6WNEGFPNfR4jpV+Zd1cL6nq2PmTG cbYaI9Nt4JkXNo060G93gIAO0KVMRVI9nJjN4dBfIVxgIMJwPNZjIZFjfIOnXqO+P3XA LlF1jLgmRSZVakz9fnuZ104psjC60+0VKPkfXQqZwyum2s5SaEWCZruK1pewaJjw9/nb awBA== X-Gm-Message-State: AJIora9Jdp+LwJGNHahIMUQsmvFIeGbR8e8tMPOVnBFzMF3W1XuLG8Z2 m/WzwhgVfRi/949feFhZhRVkcw== X-Received: by 2002:a17:90b:2245:b0:1ed:fef:5656 with SMTP id hk5-20020a17090b224500b001ed0fef5656mr15588223pjb.100.1656672789632; Fri, 01 Jul 2022 03:53:09 -0700 (PDT) Received: from wenstp920.tpe.corp.google.com ([2401:fa00:1:10:59bf:8b47:50a0:b04f]) by smtp.gmail.com with ESMTPSA id j2-20020a170902758200b0016a058b7547sm14906670pll.294.2022.07.01.03.53.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 01 Jul 2022 03:53:09 -0700 (PDT) From: Chen-Yu Tsai To: Tiffany Lin , Andrew-CT Chen , Yunfei Dong , Mauro Carvalho Chehab , Hans Verkuil Cc: AngeloGioacchino Del Regno , Nicolas Dufresne , Chen-Yu Tsai , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, Matthias Brugger Subject: [PATCH 2/6] media: mediatek: vcodec: Use meaningful decoder card name including chip name Date: Fri, 1 Jul 2022 18:52:33 +0800 Message-Id: <20220701105237.932332-3-wenst@chromium.org> X-Mailer: git-send-email 2.37.0.rc0.161.g10f37bed90-goog In-Reply-To: <20220701105237.932332-1-wenst@chromium.org> References: <20220701105237.932332-1-wenst@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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 The card name for the video decoder previously held a static platform name, that was fixed to match MT8173. This obviously doesn't make sense for newer chips. Since commit a8a7a278c56a ("media: mediatek: vcodec: Change decoder v4l2 capability value"), this field was changed to hold the driver's name, or "mtk-vcodec-dec". This doesn't make much sense either, since this still doesn't reflect what chip this is. Instead, fill in the card name with "MTxxxx video decoder" with the proper chip number. Fixes: a8a7a278c56a ("media: mediatek: vcodec: Change decoder v4l2 capability value") Signed-off-by: Chen-Yu Tsai --- drivers/media/platform/mediatek/vcodec/mtk_vcodec_dec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/platform/mediatek/vcodec/mtk_vcodec_dec.c b/drivers/media/platform/mediatek/vcodec/mtk_vcodec_dec.c index e7ea632a3f94..7f03dab518a4 100644 --- a/drivers/media/platform/mediatek/vcodec/mtk_vcodec_dec.c +++ b/drivers/media/platform/mediatek/vcodec/mtk_vcodec_dec.c @@ -248,7 +248,7 @@ static int vidioc_vdec_querycap(struct file *file, void *priv, int platform_name = mtk_vcodec_dec_get_chip_name(priv); strscpy(cap->driver, dev->driver->name, sizeof(cap->driver)); - strscpy(cap->card, MTK_VCODEC_DEC_NAME, sizeof(cap->card)); + snprintf(cap->card, sizeof(cap->card), "MT%d video decoder", platform_name); snprintf(cap->bus_info, sizeof(cap->bus_info), "platform:mt%d-dec", platform_name); return 0; -- 2.37.0.rc0.161.g10f37bed90-goog