linux-kernel - Re: [PATCH v14 0/3] Add drm driver for Rockchip Socs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Nov 2014 14:05:00 -0500
From:	Daniel Kurtz <djkurtz@...omium.org>
To:	Mark yao <mark.yao@...k-chips.com>, Arnd Bergmann <arnd@...db.de>
Cc:	Dave Airlie <airlied@...il.com>, Joerg Roedel <jroedel@...e.de>,
	Heiko Stübner <heiko@...ech.de>,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>,
	Rob Clark <robdclark@...il.com>,
	Daniel Vetter <daniel@...ll.ch>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Grant Likely <grant.likely@...aro.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	John Stultz <john.stultz@...aro.org>,
	Rom Lemarchand <romlem@...gle.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	linux-api@...r.kernel.org,
	"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
	Douglas Anderson <dianders@...omium.org>,
	Stéphane Marchesin <marcheu@...omium.org>,
	Dominik Behr <dbehr@...omium.org>,
	Olof Johansson <olof@...om.net>, Eddie Cai <cf@...k-chips.com>,
	simon xue <xxm@...k-chips.com>,
	Tao Huang <huangtao@...k-chips.com>,
	Kever Yang <kever.yang@...k-chips.com>,
	闫孝军 <yxj@...k-chips.com>, xw@...k-chips.com
Subject: Re: [PATCH v14 0/3] Add drm driver for Rockchip Socs

On Thu, Nov 27, 2014 at 2:08 AM, Mark yao <mark.yao@...k-chips.com> wrote:
>
> On 2014年11月27日 10:12, Dave Airlie wrote:
>>>>
>>>>
>>> Hi Dave
>>>      Do you mean that I need send you a branch, based on drm-next, merge with
>>> iommu tree and rockchip drm?
>>
>> Yes, grab drm-next, git pull the arm/rockchip branch from Joerg's
>> tree, put rockchip drm
>> patches on top, send me pull request.
>>
>> I'll validate it then.
>>
>> Dave.
>>
> Hi Dave
>     I have send a pull request to you, with Joerg's iommu arm/rockchip branch.
>
>     I got a same problem when use "make multi_v7_defconfig" as Heiko said:
>         drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
>         drivers/video/fbdev/Kconfig:5:    symbol FB is selected by DRM_KMS_FB_HELPER
>         drivers/gpu/drm/Kconfig:34:    symbol DRM_KMS_FB_HELPER is selected by DRM_ROCKCHIP
>         drivers/gpu/drm/rockchip/Kconfig:1:    symbol DRM_ROCKCHIP depends on ARM_DMA_USE_IOMMU
>         arch/arm/Kconfig:95:    symbol ARM_DMA_USE_IOMMU is selected by VIDEO_OMAP3
>         drivers/media/platform/Kconfig:96:    symbol VIDEO_OMAP3 depends on VIDEO_V4L2
>         drivers/media/v4l2-core/Kconfig:6:    symbol VIDEO_V4L2 depends on I2C
>         drivers/i2c/Kconfig:7:    symbol I2C is selected by FB_DDC
>         drivers/video/fbdev/Kconfig:59:    symbol FB_DDC is selected by FB_CYBER2000_DDC
>         drivers/video/fbdev/Kconfig:374:    symbol FB_CYBER2000_DDC depends on FB_CYBER2000
>         drivers/video/fbdev/Kconfig:362:    symbol FB_CYBER2000 depends on FB
>
>     I was confused how to solve the recursive dependency, remove depends on ARM_DMA_USE_IOMMU & IOMMU_API?

The "depends on ARM_DMA_USE_IOMMU & IOMMU_API" was suggested by Arnd
Bergmann during code review (originally they were selected).

Removing them definitely fixes the dependency recursion.
Also, since they are both already selected by ROCKCHIP_IOMMU,
everything will build correctly.
So, this sounds good to me, but I am no expert on Kconfig.

-Dan

>
> - Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/