From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel@ffwll.ch>,
Laura Abbott <labbott@redhat.com>,
devel@driverdev.osuosl.org, romlem@google.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
arve@android.com, linux-kernel@vger.kernel.org,
linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org,
Riley Andrews <riandrews@android.com>,
Mark Brown <broonie@kernel.org>,
Daniel Vetter <daniel.vetter@intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging
Date: Fri, 03 Mar 2017 18:45:40 +0200 [thread overview]
Message-ID: <10344634.XsotFaGzfj@avalon> (raw)
In-Reply-To: <20170303100433.lm5t4hqxj6friyp6@phenom.ffwll.local>
Hi Daniel,
On Friday 03 Mar 2017 11:04:33 Daniel Vetter wrote:
> On Thu, Mar 02, 2017 at 01:44:32PM -0800, Laura Abbott wrote:
> > Hi,
> >
> > There's been some recent discussions[1] about Ion-like frameworks. There's
> > apparently interest in just keeping Ion since it works reasonablly well.
> > This series does what should be the final clean ups for it to possibly be
> > moved out of staging.
> >
> > This includes the following:
> > - Some general clean up and removal of features that never got a lot of
> > use as far as I can tell.
> >
> > - Fixing up the caching. This is the series I proposed back in December[2]
> > but never heard any feedback on. It will certainly break existing
> > applications that rely on the implicit caching. I'd rather make an
> > effort to move to a model that isn't going directly against the
> > establishement though.
> >
> > - Fixing up the platform support. The devicetree approach was never well
> > recieved by DT maintainers. The proposal here is to think of Ion less as
> > specifying requirements and more of a framework for exposing memory to
> > userspace.
> >
> > - CMA allocations now happen without the need of a dummy device structure.
> > This fixes a bunch of the reasons why I attempted to add devicetree
> > support before.
> >
> > I've had problems getting feedback in the past so if I don't hear any
> > major objections I'm going to send out with the RFC dropped to be picked
> > up. The only reason there isn't a patch to come out of staging is to
> > discuss any other changes to the ABI people might want. Once this comes
> > out of staging, I really don't want to mess with the ABI.
> >
> > Feedback appreciated.
>
> Imo looks all good. And I just realized that cross-checking with the TODO,
> the 2 items about _CUSTOM and _IMPORT ioctls I noted are already there.
>
> Otherwise I looked through the patches, looks all really reasonable.
Two more items that need to be addressed in my opinion :
- Let's not export the ion_client API, we don't want drivers to be ion-
specific. Only the dma-buf interface should be visible to drivers.
- I haven't seen any proposal how a heap-based solution could be used in a
generic distribution. This needs to be figured out before committing to any
API/ABI.
> Wrt merging, my experience from destaging the android syncpt stuff was
> that merging the patches through the staging tree lead to lots of
> cross-tree issues with the gpu folks wanting to use that. Ion will
> probably run into similar things, so I'd propose we pull these cleanup
> patches and the eventual de-staging in throught drm. Yes that defacto
> means I'm also volunteering myself a bit :-)
>
> In the end we could put it all into drivers/gpu/ion or something like
> that.
>
> Thoughts? Greg?
> -Daniel
>
> > Thanks,
> > Laura
> >
> > [1] https://marc.info/?l=linux-kernel&m=148699712602105&w=2
> > [2] https://marc.info/?l=linaro-mm-sig&m=148176050802908&w=2
> >
> > Laura Abbott (12):
> > staging: android: ion: Remove dmap_cnt
> > staging: android: ion: Remove alignment from allocation field
> > staging: android: ion: Duplicate sg_table
> > staging: android: ion: Call dma_map_sg for syncing and mapping
> > staging: android: ion: Remove page faulting support
> > staging: android: ion: Remove crufty cache support
> > staging: android: ion: Remove old platform support
> > cma: Store a name in the cma structure
> > cma: Introduce cma_for_each_area
> > staging: android: ion: Use CMA APIs directly
> > staging: android: ion: Make Ion heaps selectable
> > staging; android: ion: Enumerate all available heaps
> >
> > drivers/base/dma-contiguous.c | 5 +-
> > drivers/staging/android/ion/Kconfig | 51 ++--
> > drivers/staging/android/ion/Makefile | 14 +-
> > drivers/staging/android/ion/hisilicon/Kconfig | 5 -
> > drivers/staging/android/ion/hisilicon/Makefile | 1 -
> > drivers/staging/android/ion/hisilicon/hi6220_ion.c | 113 ---------
> > drivers/staging/android/ion/ion-ioctl.c | 6 -
> > drivers/staging/android/ion/ion.c | 282
> > ++++++--------------- drivers/staging/android/ion/ion.h
> > | 5 +-
> > drivers/staging/android/ion/ion_carveout_heap.c | 16 +-
> > drivers/staging/android/ion/ion_chunk_heap.c | 15 +-
> > drivers/staging/android/ion/ion_cma_heap.c | 102 ++------
> > drivers/staging/android/ion/ion_dummy_driver.c | 156 ------------
> > drivers/staging/android/ion/ion_enumerate.c | 89 +++++++
> > drivers/staging/android/ion/ion_of.c | 184 --------------
> > drivers/staging/android/ion/ion_of.h | 37 ---
> > drivers/staging/android/ion/ion_page_pool.c | 3 -
> > drivers/staging/android/ion/ion_priv.h | 57 ++++-
> > drivers/staging/android/ion/ion_system_heap.c | 14 +-
> > drivers/staging/android/ion/tegra/Makefile | 1 -
> > drivers/staging/android/ion/tegra/tegra_ion.c | 80 ------
> > include/linux/cma.h | 6 +-
> > mm/cma.c | 25 +-
> > mm/cma.h | 1 +
> > mm/cma_debug.c | 2 +-
> > 25 files changed, 312 insertions(+), 958 deletions(-)
> > delete mode 100644 drivers/staging/android/ion/hisilicon/Kconfig
> > delete mode 100644 drivers/staging/android/ion/hisilicon/Makefile
> > delete mode 100644 drivers/staging/android/ion/hisilicon/hi6220_ion.c
> > delete mode 100644 drivers/staging/android/ion/ion_dummy_driver.c
> > create mode 100644 drivers/staging/android/ion/ion_enumerate.c
> > delete mode 100644 drivers/staging/android/ion/ion_of.c
> > delete mode 100644 drivers/staging/android/ion/ion_of.h
> > delete mode 100644 drivers/staging/android/ion/tegra/Makefile
> > delete mode 100644 drivers/staging/android/ion/tegra/tegra_ion.c
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-03-03 16:46 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 21:44 [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 01/12] staging: android: ion: Remove dmap_cnt Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 02/12] staging: android: ion: Remove alignment from allocation field Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 03/12] staging: android: ion: Duplicate sg_table Laura Abbott
2017-03-03 8:18 ` Hillf Danton
2017-03-03 18:41 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 04/12] staging: android: ion: Call dma_map_sg for syncing and mapping Laura Abbott
2017-03-03 11:04 ` Dan Carpenter
2017-03-03 11:58 ` Eric Engestrom
2017-03-03 16:37 ` Laurent Pinchart
2017-03-03 18:40 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 05/12] staging: android: ion: Remove page faulting support Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 06/12] staging: android: ion: Remove crufty cache support Laura Abbott
2017-03-03 9:56 ` Daniel Vetter
2017-03-03 16:39 ` Laurent Pinchart
2017-03-03 18:46 ` Laura Abbott
2017-03-06 10:29 ` Daniel Vetter
2017-03-06 17:00 ` Emil Velikov
2017-03-06 19:20 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 07/12] staging: android: ion: Remove old platform support Laura Abbott
2017-03-03 10:31 ` Daniel Vetter
2017-03-02 21:44 ` [RFC PATCH 08/12] cma: Store a name in the cma structure Laura Abbott
2017-03-10 8:53 ` Sumit Semwal
2017-03-17 18:02 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 09/12] cma: Introduce cma_for_each_area Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 10/12] staging: android: ion: Use CMA APIs directly Laura Abbott
2017-03-03 16:41 ` Laurent Pinchart
2017-03-03 18:50 ` Laura Abbott
2017-03-06 10:32 ` Daniel Vetter
2017-03-06 13:43 ` Laurent Pinchart
2017-03-06 15:52 ` Daniel Vetter
2017-03-06 19:14 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 11/12] staging: android: ion: Make Ion heaps selectable Laura Abbott
2017-03-03 10:33 ` Daniel Vetter
2017-03-03 19:10 ` Laura Abbott
2017-03-02 21:44 ` [RFC PATCH 12/12] staging; android: ion: Enumerate all available heaps Laura Abbott
2017-03-03 10:39 ` Daniel Vetter
2017-03-03 10:04 ` [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging Daniel Vetter
2017-03-03 10:27 ` Daniel Vetter
2017-03-03 12:54 ` Benjamin Gaignard
2017-03-03 16:45 ` Laurent Pinchart [this message]
2017-03-03 19:16 ` Laura Abbott
2017-03-06 10:38 ` Daniel Vetter
2017-03-06 15:02 ` Laurent Pinchart
2017-03-06 16:01 ` Daniel Vetter
2017-03-03 13:29 ` Michal Hocko
2017-03-03 17:37 ` Laura Abbott
2017-03-06 7:42 ` Michal Hocko
2017-03-06 10:40 ` Daniel Vetter
2017-03-06 10:58 ` Mark Brown
2017-03-06 16:04 ` Daniel Vetter
2017-03-09 10:00 ` Benjamin Gaignard
2017-03-09 17:38 ` Laura Abbott
2017-03-10 10:31 ` Brian Starkey
2017-03-10 11:46 ` Robin Murphy
2017-03-10 14:27 ` Brian Starkey
2017-03-10 16:46 ` Laura Abbott
2017-03-10 12:40 ` Daniel Vetter
2017-03-10 13:56 ` Rob Clark
2017-03-12 13:34 ` Benjamin Gaignard
2017-03-12 19:05 ` Daniel Vetter
2017-03-13 21:09 ` Laura Abbott
2017-03-13 21:29 ` Rob Clark
2017-03-13 21:59 ` Laura Abbott
2017-03-14 14:47 ` Benjamin Gaignard
2017-03-14 19:45 ` Laura Abbott
2017-03-14 20:28 ` Nicolas Dufresne
2017-03-13 10:54 ` Brian Starkey
2017-03-13 13:21 ` Mark Brown
2017-03-13 21:45 ` Laura Abbott
2017-03-13 21:29 ` Laura Abbott
2017-03-06 13:34 ` Michal Hocko
2017-03-03 16:25 ` Laurent Pinchart
2017-03-03 19:14 ` Laura Abbott
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=10344634.XsotFaGzfj@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=arve@android.com \
--cc=broonie@kernel.org \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riandrews@android.com \
--cc=romlem@google.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;
as well as URLs for NNTP newsgroup(s).