From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 07D6CC433F5 for ; Wed, 6 Apr 2022 14:43:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=HmxOXru+7703z31Z8XL9fPcydvFa4BILi51AXVWLUN8=; b=Z6v//zMXKN0oiY LsRfoelP6umTD+RrX325PyDw5w4DamFlT6dUrXf/2wSJhkhOyba+rw2+wIQt7c25wGMRu5TheqobS pNopaMKAGIaMZnxS12Bj6ZxB4ILotaR6vLp7evjFZ8DubWWhgG/NAwyLsIbIxMLZG+RF/aIMfuKOd Y/xEPiVedJyYXXiRR7oiVJ40AjzKBJ3kcl454kT/m+TS+uek1qvYyQlptE0Gemogyw/bJUUnJ+ZPT +KtV+zadcJLNdZB9k+UhhGHlUvlh9GorZj2b4ZmR/qQ5FaVcimqTermPgLRXiMxY+sW8asNnECNDk mDChCSG1i4RJHMUSSjYg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nc6rr-006bPD-Kt; Wed, 06 Apr 2022 14:42:43 +0000 Received: from bhuna.collabora.co.uk ([2a00:1098:0:82:1000:25:2eeb:e3e3]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nc6ml-006Ynk-Si for linux-arm-kernel@lists.infradead.org; Wed, 06 Apr 2022 14:37:29 +0000 Received: from [IPV6:2a00:5f00:102:0:10b3:10ff:fe5d:4ec1] (unknown [IPv6:2a00:5f00:102:0:10b3:10ff:fe5d:4ec1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dmitry.osipenko) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 59CFC1F43AFB; Wed, 6 Apr 2022 15:37:21 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1649255841; bh=oYbhhKf585FGxtfFi8U5NPanPDke0qUq43aCdjprdg4=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=D1bjXlub0DKhAHX9eC1Mskz0kpNJlgDL3vTdlnllLhD33qQf2iGfE9ZEhza4pUxMf tgdezZsYawteXM2vOiBoXJbdPVKM6QJgytCw3zlpSfcSjNGmIsUrxs+7lfUmsHCLoG OY6jDqxHEkn0wesscJL/7V/51VUrEQChxdGJgQvwKaxc8E2wTCaH4BqZi5MOVa9LS9 27xppc8hPVukIL1s/r4HHGV30lYkXOqIdSCd0xW0eBviSb1tXE15EkD3dj61meZQ4L L4b7wKDcxOUqYOZwlJscF0phZBpMIJIFm7BdMQG0otle3ANi12iYU7S/ogHdca8n1R ZfKi145lqJWfw== Message-ID: <89c70eab-da76-36f7-0576-0122a7861c9c@collabora.com> Date: Wed, 6 Apr 2022 17:37:18 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH] ARM: tegra_defconfig: Fix enabling of the Tegra VDE driver Content-Language: en-US To: Jon Hunter , Thierry Reding Cc: linux-arm-kernel@lists.infradead.org, linux-tegra@vger.kernel.org, Dmitry Osipenko References: <20220406135920.129589-1-jonathanh@nvidia.com> From: Dmitry Osipenko In-Reply-To: <20220406135920.129589-1-jonathanh@nvidia.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220406_073728_117651_B93DE692 X-CRM114-Status: GOOD ( 20.71 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 4/6/22 16:59, Jon Hunter wrote: > Commit 8bd4aaf438e3 ("media: staging: tegra-vde: De-stage driver") moved > the Tegra VDE driver out of staging and updated the Kconfig symbol for > enabling the driver from CONFIG_TEGRA_VDE to CONFIG_VIDEO_TEGRA_VDE. > However, the tegra_defconfig was not updated and so the driver is no > longer enabled by default. Furthermore, now that the Tegra VDE driver > has been moved under the Kconfig symbol CONFIG_V4L_MEM2MEM_DRIVERS, it > is now also necessary to enable CONFIG_V4L_MEM2MEM_DRIVERS in order to > enable CONFIG_VIDEO_TEGRA_VDE. Fix this by ensuring that > CONFIG_V4L_MEM2MEM_DRIVERS and CONFIG_VIDEO_TEGRA_VDE are both enabled > in the tegra_defconfig. > > Fixes: 8bd4aaf438e3 ("media: staging: tegra-vde: De-stage driver") > Signed-off-by: Jon Hunter > --- > arch/arm/configs/tegra_defconfig | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig > index 289d022acc4b..c209722399d7 100644 > --- a/arch/arm/configs/tegra_defconfig > +++ b/arch/arm/configs/tegra_defconfig > @@ -286,7 +286,8 @@ CONFIG_SERIO_NVEC_PS2=y > CONFIG_NVEC_POWER=y > CONFIG_NVEC_PAZ00=y > CONFIG_STAGING_MEDIA=y > -CONFIG_TEGRA_VDE=y > +CONFIG_V4L_MEM2MEM_DRIVERS=y > +CONFIG_VIDEO_TEGRA_VDE=y > CONFIG_CHROME_PLATFORMS=y > CONFIG_CROS_EC=y > CONFIG_CROS_EC_I2C=m There are per-existing patches updating the defconfigs, unfortunately they were not applied together with the driver patches. https://patchwork.ozlabs.org/project/linux-tegra/patch/20220220204623.30107-8-digetx@gmail.com/ https://patchwork.ozlabs.org/project/linux-tegra/patch/20220220204623.30107-9-digetx@gmail.com/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel