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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D2A3C433E0 for ; Fri, 31 Jul 2020 16:47:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 28A6622B40 for ; Fri, 31 Jul 2020 16:47:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596214070; bh=jHyITw6tiKBPTOT1fTSCnphJCVlLgnN8j8XhPK8DIVY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ZQhGmUGyYoHFrGeJEzSd/tIfkq4gv7xjHJE4lkZUTZ570i77hRXL7YXQvqoc3W49J I0sNMxKQlimm7kZIekKaGd8KBX8AfRDXbfyP0SDYeikYwx8fBZ8KmcfRxf7UcCXt91 F8rLRkysMbZnFW7NEGewzNQ4L+7r9tlxDE6SDZzk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732481AbgGaQrt (ORCPT ); Fri, 31 Jul 2020 12:47:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:38918 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728898AbgGaQrt (ORCPT ); Fri, 31 Jul 2020 12:47:49 -0400 Received: from localhost (unknown [122.171.202.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 44F782245C; Fri, 31 Jul 2020 16:47:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596214069; bh=jHyITw6tiKBPTOT1fTSCnphJCVlLgnN8j8XhPK8DIVY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UfyqsydV9DH/rQ5nQgZJpTMBJmerJlYsb4k8Rf3UJW3Y6518PNxtuR7KjRALQE062 xcQzN+StQUPzRhCEAxjEf2eWGVHHfmayWUD7IdiDJKW71nAGviAayW+fN3W5IyQB3M cIDQJwER9vvoCOvkD4IIxJORD0OHITUN4r2NyGL8= Date: Fri, 31 Jul 2020 22:17:44 +0530 From: Vinod Koul To: Laurent Pinchart Cc: dmaengine@vger.kernel.org, dri-devel@lists.freedesktop.org, alsa-devel@alsa-project.org, Hyun Kwon , Randy Dunlap , Liam Girdwood , Michal Simek , Alexandre Bounine , Mark Brown , Matt Porter Subject: Re: [PATCH v2 0/3] Fix Kconfig dependency issue with DMAENGINES selection Message-ID: <20200731164744.GF12965@vkoul-mobl> References: <20200731152433.1297-1-laurent.pinchart@ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200731152433.1297-1-laurent.pinchart@ideasonboard.com> Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org On 31-07-20, 18:24, Laurent Pinchart wrote: > Hello, > > This small series fixes a Kconfig dependency issue with the recently > merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but > requires a separate fixes in patches 1/3 and 2/3 to avoid circular > dependencies: > > drivers/i2c/Kconfig:8:error: recursive dependency detected! > drivers/i2c/Kconfig:8: symbol I2C is selected by FB_DDC > drivers/video/fbdev/Kconfig:63: symbol FB_DDC depends on FB > drivers/video/fbdev/Kconfig:12: symbol FB is selected by DRM_KMS_FB_HELPER > drivers/gpu/drm/Kconfig:80: symbol DRM_KMS_FB_HELPER depends on DRM_KMS_HELPER > drivers/gpu/drm/Kconfig:74: symbol DRM_KMS_HELPER is selected by DRM_ZYNQMP_DPSUB > drivers/gpu/drm/xlnx/Kconfig:1: symbol DRM_ZYNQMP_DPSUB depends on DMA_ENGINE > drivers/dma/Kconfig:44: symbol DMA_ENGINE depends on DMADEVICES > drivers/dma/Kconfig:6: symbol DMADEVICES is selected by SND_SOC_SH4_SIU > sound/soc/sh/Kconfig:30: symbol SND_SOC_SH4_SIU is selected by SND_SIU_MIGOR > sound/soc/sh/Kconfig:60: symbol SND_SIU_MIGOR depends on I2C > For a resolution refer to Documentation/kbuild/kconfig-language.rst > subsection "Kconfig recursive dependency limitations" > > Due to the DPSUB driver being merged in v5.9, this is a candidate fix > for v5.9 as well. 1/3 and 2/3 can be merged independently, 3/3 depends > on the first two. What's the best course of action, can I merge this all > in a single tree, or should the rapidio and ASoC patches be merged > independently early in the -rc cycle, and the DRM patch later on top ? I > don't expect conflicts (especially in 2/3 and 3/3), so merging the whole > series in one go would be simpler in my opinion. Acked-By: Vinod Koul -- ~Vinod