linux-rockchip.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [GIT PULL] drm/rockchip: convert to drm_mm
@ 2017-02-16  3:02 Mark yao
       [not found] ` <58A51647.2040003-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Mark yao @ 2017-02-16  3:02 UTC (permalink / raw)
  To: David Airlie; +Cc: open list:ARM/Rockchip SoC..., dri-devel

[-- Attachment #1: Type: text/html, Size: 2099 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [GIT PULL] drm/rockchip: convert to drm_mm
       [not found] ` <58A51647.2040003-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
@ 2017-02-26 20:45   ` Daniel Vetter
       [not found]     ` <20170226204554.y3dqu52hzrgbv5rj-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Vetter @ 2017-02-26 20:45 UTC (permalink / raw)
  To: Mark yao
  Cc: David Airlie, open list:ARM/Rockchip SoC...,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On Thu, Feb 16, 2017 at 11:02:31AM +0800, Mark yao wrote:
> Hi Dave
> 
> After convert to drm_mm, rockchip arm64 platform can works with iommu, like
> rk3399. it's import patches for rockchip arm64 platform
> 
> And these patches already have full reviewed, I hope these patches can be
> landed.
>  
> Best regards
> 
> The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442:
> 
>   Merge branch 'drm-next-4.11' of git://people.freedesktop.org/~agd5f/linux
> into drm-next (2017-02-10 10:13:30 +1000)
> 
> are available in the git repository at:
> 
> 
>   https://github.com/markyzq/kernel-drm-rockchip.git
> drm-rockchip-next-2017-02-16
> 
> for you to fetch changes up to 1aa5ca6e3ec63aa5815d78646748e88a7ceb1c8e:
> 
>   drm/rockchip: Use common IOMMU API to attach devices (2017-02-15 08:52:13
> +0800)
> 
> ----------------------------------------------------------------
> Shunqian Zheng (1):
>       drm/rockchip: Use common IOMMU API to attach devices
> 
> Tomasz Figa (1):
>       drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

I thought we've moved rockchip into drm-misc ...?

Can you and Sean Paul please talk and figure out how exactly you want to
maintain this driver? The current situation where we have stuff going in
independently through different maintainers is not great at all. If you
can't get agreement, we'll just make you agree by arbitrarily rolling the
dice or something silly like that :-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [GIT PULL] drm/rockchip: convert to drm_mm
       [not found]     ` <20170226204554.y3dqu52hzrgbv5rj-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
@ 2017-02-27  2:20       ` Mark yao
  0 siblings, 0 replies; 3+ messages in thread
From: Mark yao @ 2017-02-27  2:20 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: David Airlie, open list:ARM/Rockchip SoC...,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 2017年02月27日 04:45, Daniel Vetter wrote:
> On Thu, Feb 16, 2017 at 11:02:31AM +0800, Mark yao wrote:
>> Hi Dave
>>
>> After convert to drm_mm, rockchip arm64 platform can works with iommu, like
>> rk3399. it's import patches for rockchip arm64 platform
>>
>> And these patches already have full reviewed, I hope these patches can be
>> landed.
>>   
>> Best regards
>>
>> The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442:
>>
>>    Merge branch 'drm-next-4.11' of git://people.freedesktop.org/~agd5f/linux
>> into drm-next (2017-02-10 10:13:30 +1000)
>>
>> are available in the git repository at:
>>
>>
>>    https://github.com/markyzq/kernel-drm-rockchip.git
>> drm-rockchip-next-2017-02-16
>>
>> for you to fetch changes up to 1aa5ca6e3ec63aa5815d78646748e88a7ceb1c8e:
>>
>>    drm/rockchip: Use common IOMMU API to attach devices (2017-02-15 08:52:13
>> +0800)
>>
>> ----------------------------------------------------------------
>> Shunqian Zheng (1):
>>        drm/rockchip: Use common IOMMU API to attach devices
>>
>> Tomasz Figa (1):
>>        drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain
> I thought we've moved rockchip into drm-misc ...?

Sorry, I'm not clear understand how the drm-misc maintain before, later 
patches would go through drm-misc

> Can you and Sean Paul please talk and figure out how exactly you want to
> maintain this driver?

Move drm/rockchip into drm-misc is good, Thanks Sean Paul's work.
I'm learning how to maintain drm/rockchip with drm-misc.

But I'm not understand drm-misc's step, I'm confused that:  do I need to 
pick up patches to drm-misc by myself?
or I just give a ACK on patches, and then Sean or other drm-misc's guys 
will pick patches up to drm-misc?

Thanks.
> The current situation where we have stuff going in
> independently through different maintainers is not great at all. If you
> can't get agreement, we'll just make you agree by arbitrarily rolling the
> dice or something silly like that :-)
> -Daniel

-- 
Mark Yao



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-02-27  2:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-16  3:02 [GIT PULL] drm/rockchip: convert to drm_mm Mark yao
     [not found] ` <58A51647.2040003-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-26 20:45   ` Daniel Vetter
     [not found]     ` <20170226204554.y3dqu52hzrgbv5rj-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-02-27  2:20       ` Mark yao

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).