Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp1417052rwl; Sun, 25 Dec 2022 21:49:05 -0800 (PST) X-Google-Smtp-Source: AMrXdXuLGbn8zea1yCXzx5SkE0PlgFTz6d4w5mxYn8IcOMC8qX6fBMlc20EzloBGxuuBZ31phwL5 X-Received: by 2002:a17:90a:bb03:b0:225:a226:9fbb with SMTP id u3-20020a17090abb0300b00225a2269fbbmr18892144pjr.39.1672033744867; Sun, 25 Dec 2022 21:49:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672033744; cv=none; d=google.com; s=arc-20160816; b=eamBTZFJ6LxPcmlKLf5toxjLNt+i54GKeNjs/7fKBHo3bLxTqUB4wevnP6C/4DjPKa i5SqzEPS84BD3fDc8K72JFMDRG6ZEYS9jatWYXlm6h8rxJJEGC9ufHBzn10aBcOBi/Um +BPF8h9sCSwgCzo1154eK3oINK9cwevb6KXN2G8BMerlg300mYEweMDk3k+GZvh1TKA+ n0jQ7M4NjxgqxJy6BPDf5SJFdZXp8+TDm7lvIVwANFtOfpZOf+0CmaO11GJvpkZ3PaA0 MmQrIX60PmFgynrKN+zPBzOZe6qPKOZFgBeWknUbZoK6YPDNGW9huxl/xN3gVgCOSjF8 XcRw== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=LF9Mm3NqqH1nEG/wEah3Sd4XDD5tbfZrQgSyrQTtptI=; b=Gp1CEJPTmJkOPi+MQUdix7g382R0kepHkxfN/jNSgmzhPjN9WXJuVcNuKgLPQvK8U3 vzdDwmjufSfhWj53nQjVd2VIRNgHX3RF1nkU1xs6rYOVt06AQ2QiObj96GWlqzAKaRBO 5YYrPpisVc3P/dz65qB3T4wvRnWyaNSRutU5JORKhYiOt9LqGF23d/yXa+qTyIKZnOt6 rw4oWWR1nx7MKohi3FXPGAJAKQSeVbqEaWDGEoPLBv8n48egxiW13Q7rCThXb/jW8Isq WlQrewxBh+H35t9hnfJdQhvEJ+hGQOxs0nqKEsGQ3+BkR62IknxcFtTphOE/R8gcmE9h cdlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=ZwNZ39F5; 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 lt19-20020a17090b355300b0020cedba54fcsi9779355pjb.55.2022.12.25.21.48.50; Sun, 25 Dec 2022 21:49:04 -0800 (PST) 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=ZwNZ39F5; 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 S231558AbiLZF0U (ORCPT + 67 others); Mon, 26 Dec 2022 00:26:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60748 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229447AbiLZF0O (ORCPT ); Mon, 26 Dec 2022 00:26:14 -0500 Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F3FD555A3 for ; Sun, 25 Dec 2022 21:26:10 -0800 (PST) Received: by mail-pj1-x1036.google.com with SMTP id o1-20020a17090a678100b00219cf69e5f0so13940466pjj.2 for ; Sun, 25 Dec 2022 21:26:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=LF9Mm3NqqH1nEG/wEah3Sd4XDD5tbfZrQgSyrQTtptI=; b=ZwNZ39F5tgP/LmtcnHq6P1mt1fj6IDl0R4Ff2oPDtgYyy3gp3vWSgx5th50vG394dt hM5ENWhp6uzpqpEZlsbx3YmTo+2wniMh/K6FYX9wJ8BQHvNtk9MloVceTOyuu0d+3ltT vZ5rRjRPG95043TvJh6z7AT3/Mrans94SvF1c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LF9Mm3NqqH1nEG/wEah3Sd4XDD5tbfZrQgSyrQTtptI=; b=o4pU22cBja2dK/nhdGfOvg7Nf3SswcW1pIqlIS+soTzqLMd8pS8fPZ7PMsg4vL5LWi LdSDRpE+93zdFWsYdGtEPVf1r7N0aeY4qc4aiIjB40yLq9bZumASCJ3GakBhlTHHAwaW DbrCgJUsyHQlFCB1cet9M9Ni9b10kP0Co4f5ESJKBpwAQ1ixzu31d9hLPzTshvIepa7A 5gXQ3E2M2PllfdvuGCKTLjrrnrYIoTMoqdyTRNvXKKlHDNOTtbB3omLpiiOxJB9FjKSN Kgfh4Ujrdew9TSERpi/hMoE6M3T+cIxIdgoJse0ZaeVrK9zOu2kDwTVG29AL3ITq1uDV ywKg== X-Gm-Message-State: AFqh2kpeolwnZMs7Z4taZC/Q+jNELvAlXpOMMiS6pWC0l6y/CcEmWcSa jfmxig3EQIbnEE5OWl6yM4SSaw== X-Received: by 2002:a17:902:f550:b0:192:7258:15b5 with SMTP id h16-20020a170902f55000b00192725815b5mr7105435plf.50.1672032370405; Sun, 25 Dec 2022 21:26:10 -0800 (PST) Received: from wenstp920.tpe.corp.google.com ([2401:fa00:1:10:db30:c4d:3ee:e697]) by smtp.gmail.com with ESMTPSA id je20-20020a170903265400b001926c38cd42sm2966161plb.192.2022.12.25.21.26.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 25 Dec 2022 21:26:10 -0800 (PST) From: Chen-Yu Tsai To: Mauro Carvalho Chehab , Hans Verkuil , Ezequiel Garcia , Philipp Zabel Cc: Chen-Yu Tsai , linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2] media: hantro: Use core-generated bus_info value Date: Mon, 26 Dec 2022 13:26:06 +0800 Message-Id: <20221226052606.144109-1-wenst@chromium.org> X-Mailer: git-send-email 2.39.0.314.g84b9a713c41-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 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 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 Hantro driver uses a hardcoded value for the bus_info field in the media device and |struct v4l2_capability|. This worked well when there was just one device. However with the iMX.8 series we are now seeing two Hantro blocks on the same chip. The static bus_info is no longer sufficient for differentiating devices. Since commit f2d8b6917f3b ("media: v4l: ioctl: Set bus_info in v4l_querycap()"), the V4L2 core provides a default value for the bus_info field for platform and PCI devices. This value will match the default value for media devices added by commit cef699749f37 ("media: mc: Set bus_info in media_device_init()"). These defaults are stable and device-specific. Drop the static bus_info values from the hantro driver and use the defaults. Signed-off-by: Chen-Yu Tsai --- Changes since v1: - Dropped unrelated Makefile change drivers/media/platform/verisilicon/hantro_drv.c | 2 -- drivers/media/platform/verisilicon/hantro_v4l2.c | 2 -- 2 files changed, 4 deletions(-) diff --git a/drivers/media/platform/verisilicon/hantro_drv.c b/drivers/media/platform/verisilicon/hantro_drv.c index 8cb4a68c9119..b0aeedae7b65 100644 --- a/drivers/media/platform/verisilicon/hantro_drv.c +++ b/drivers/media/platform/verisilicon/hantro_drv.c @@ -1050,8 +1050,6 @@ static int hantro_probe(struct platform_device *pdev) vpu->mdev.dev = vpu->dev; strscpy(vpu->mdev.model, DRIVER_NAME, sizeof(vpu->mdev.model)); - strscpy(vpu->mdev.bus_info, "platform: " DRIVER_NAME, - sizeof(vpu->mdev.bus_info)); media_device_init(&vpu->mdev); vpu->mdev.ops = &hantro_m2m_media_ops; vpu->v4l2_dev.mdev = &vpu->mdev; diff --git a/drivers/media/platform/verisilicon/hantro_v4l2.c b/drivers/media/platform/verisilicon/hantro_v4l2.c index 2c7a805289e7..c1a116031013 100644 --- a/drivers/media/platform/verisilicon/hantro_v4l2.c +++ b/drivers/media/platform/verisilicon/hantro_v4l2.c @@ -142,8 +142,6 @@ static int vidioc_querycap(struct file *file, void *priv, strscpy(cap->driver, vpu->dev->driver->name, sizeof(cap->driver)); strscpy(cap->card, vdev->name, sizeof(cap->card)); - snprintf(cap->bus_info, sizeof(cap->bus_info), "platform: %s", - vpu->dev->driver->name); return 0; } -- 2.39.0.314.g84b9a713c41-goog