All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [GIT FIXES FOR v5.9] Remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag
Date: Thu, 17 Sep 2020 09:20:25 +0200	[thread overview]
Message-ID: <20200917092025.285f18a5@coco.lan> (raw)
In-Reply-To: <9347220a-a039-93ff-5dd7-f35613631a29@xs4all.nl>

Em Fri, 11 Sep 2020 12:52:57 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> From the commit log of the patch:
> 
> --------------------------------------------------------------------
> The patch partially reverts some of the UAPI bits of the buffer
> cache management hints. Namely, the queue consistency (memory
> coherency) user-space hint because, as it turned out, the kernel
> implementation of this feature was misusing DMA_ATTR_NON_CONSISTENT.
> 
> The patch revers both kernel and user space parts: removes the
> DMA consistency attr functions, rolls back changes to v4l2_requestbuffers,
> v4l2_create_buffers structures and corresponding UAPI functions
> (plus compat32 layer) and cleans up the documentation.
> --------------------------------------------------------------------
> 
> The intention is that this feature will return once proper low-level support
> for this has been sorted. A patch to revert the v4l-utils changes is ready
> to be merged once this patch made it's way to our master branch:
> 
> https://patchwork.linuxtv.org/project/linux-media/patch/20200911030952.74468-1-sergey.senozhatsky@gmail.com/
> 
> I've tested this with the test-media script.
> 
> Regards,
> 
> 	Hans
> 
> The following changes since commit 93c16fabdb74a9c1a427402fc1fe588a45130c5b:
> 
>   media: ov8856: Add support for 3264x2448 mode (2020-09-10 14:29:35 +0200)
> 
> are available in the Git repository at:
> 
>   git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.9-mem
> 
> for you to fetch changes up to d36642b40255022dda1cfcaebe82e40a592d4ee8:
> 
>   media/v4l2: remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag (2020-09-11 12:26:54 +0200)

This caused a warning when building the html books. Not sure why the robot
didn't warn. I'll be posting a fix at the ML.

Thanks,
Mauro

      parent reply	other threads:[~2020-09-17  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 10:52 [GIT FIXES FOR v5.9] Remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag Hans Verkuil
2020-09-11 11:26 ` [GIT FIXES FOR v5.9] Remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag (#66890) Jenkins
2020-09-17  7:20 ` Mauro Carvalho Chehab [this message]

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=20200917092025.285f18a5@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.