public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark yao <mark.yao@rock-chips.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "Joerg Roedel" <jroedel@suse.de>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Boris BREZILLON" <boris.brezillon@free-electrons.com>,
	"Rob Clark" <robdclark@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"John Stultz" <john.stultz@linaro.org>,
	"Rom Lemarchand" <romlem@google.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-api@vger.kernel.org, linux-rockchip@lists.infradead.org,
	"Douglas Anderson" <dianders@chromium.org>,
	"Stéphane Marchesin" <marcheu@chromium.org>,
	dbehr@chromium.org, "Olof Johansson" <olof@lixom.net>,
	"Daniel Kurtz" <djkurtz@chromium.org>,
	"Eddie Cai" <cf@rock-chips.com>, "simon xue" <xxm@rock-chips.com>,
	"Tao Huang" <huangtao@rock-chips.com>,
	"Kever Yang" <kever.yang@rock-chips.com>,
	yxj@rock-chips.com, xw@rock-chips.com
Subject: Re: [PATCH v14 0/3] Add drm driver for Rockchip Socs
Date: Thu, 27 Nov 2014 15:08:39 +0800	[thread overview]
Message-ID: <5476CDF7.60208@rock-chips.com> (raw)
In-Reply-To: <CAPM=9tyZpDEPcipYDq2_qdQ9zK2bnPFYTUL2qDvAd7QoUOm-QQ@mail.gmail.com>

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?

- Mark




  reply	other threads:[~2014-11-27  7:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  1:46 [PATCH v14 0/3] Add drm driver for Rockchip Socs Mark Yao
2014-11-20  1:47 ` [PATCH v14 1/3] drm: rockchip: Add basic drm driver Mark Yao
2014-11-20  1:47 ` [PATCH v14 2/3] dt-bindings: video: Add for rockchip display subsytem Mark Yao
2014-11-20  1:47 ` [PATCH v14 3/3] dt-bindings: video: Add documentation for rockchip vop Mark Yao
2014-11-25 16:38 ` [PATCH v14 0/3] Add drm driver for Rockchip Socs Heiko Stübner
2014-11-25 23:12   ` Dave Airlie
2014-11-26  0:37     ` Heiko Stübner
2014-11-26  7:34       ` Joerg Roedel
2014-11-26 22:53         ` Dave Airlie
2014-11-27  1:40           ` Mark yao
2014-11-27  2:12             ` Dave Airlie
2014-11-27  7:08               ` Mark yao [this message]
2014-11-27 19:05                 ` Daniel Kurtz
2014-11-27 21:56                   ` Arnd Bergmann
2014-11-27 22:16                     ` Rob Clark
2014-11-27 22:17                   ` Heiko Stübner
2014-11-27  7:01 ` [GIT PULL] core drm support for Rockchip SoCs v14 Mark yao
2014-12-02  3:53   ` Dave Airlie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5476CDF7.60208@rock-chips.com \
    --to=mark.yao@rock-chips.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=cf@rock-chips.com \
    --cc=daniel@ffwll.ch \
    --cc=dbehr@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=djkurtz@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=john.stultz@linaro.org \
    --cc=jroedel@suse.de \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=marcheu@chromium.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=romlem@google.com \
    --cc=xw@rock-chips.com \
    --cc=xxm@rock-chips.com \
    --cc=yxj@rock-chips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox