From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL] Selection API and fixes for v3.2
Date: Mon, 26 Sep 2011 08:13:50 -0300 [thread overview]
Message-ID: <4E805E6E.3080007@redhat.com> (raw)
In-Reply-To: <1316704391-13596-1-git-send-email-m.szyprowski@samsung.com>
Em 22-09-2011 12:13, Marek Szyprowski escreveu:
> Hello Mauro,
>
> I've collected pending selection API patches together with pending
> videobuf2 and Samsung driver fixes to a single git branch. Please pull
> them to your media tree.
>
> Best regards,
> Marek Szyprowski
> Samsung Poland R&D Center
>
> The following changes since commit 699cc1962c85351689c27dd46e598e4204fdd105:
>
> [media] TT-budget S2-3200 cannot tune on HB13E DVBS2 transponder (2011-09-21 17:06:56 -0300)
>
> are available in the git repository at:
> git://git.infradead.org/users/kmpark/linux-2.6-samsung for_mauro
Continuing the patches review from this series:
0689133 [media] s5p-tv: fix mbus configuration
17b2747 [media] s5p-tv: hdmi: use DVI mode
0f6c565 [media] s5p-tv: Add PM_RUNTIME dependency
Applied, thanks!
> Scott Jiang (1):
> vb2: add vb2_get_unmapped_area in vb2 core
> diff --git a/include/media/videobuf2-core.h b/include/media/videobuf2-core.h
> index ea55c08..977410b 100644
> --- a/include/media/videobuf2-core.h
> +++ b/include/media/videobuf2-core.h
> @@ -309,6 +309,13 @@ int vb2_streamon(struct vb2_queue *q, enum v4l2_buf_type type);
> int vb2_streamoff(struct vb2_queue *q, enum v4l2_buf_type type);
>
> int vb2_mmap(struct vb2_queue *q, struct vm_area_struct *vma);
> +#ifndef CONFIG_MMU
> +unsigned long vb2_get_unmapped_area(struct vb2_queue *q,
> + unsigned long addr,
> + unsigned long len,
> + unsigned long pgoff,
> + unsigned long flags);
> +#endif
> unsigned int vb2_poll(struct vb2_queue *q, struct file *file, poll_table *wait);
> size_t vb2_read(struct vb2_queue *q, char __user *data, size_t count,
> loff_t *ppos, int nonblock);
This sounds me like a hack, as it is passing the problem of working with a non-mmu
capable hardware to the driver, inserting architecture-dependent bits on them.
The proper way to do it is to provide a vb2 core support to handle the non-mmu case
inside it.
Thanks,
Mauro
next prev parent reply other threads:[~2011-09-26 11:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:13 [GIT PULL] Selection API and fixes for v3.2 Marek Szyprowski
2011-09-24 3:58 ` Mauro Carvalho Chehab
2011-09-26 8:42 ` Tomasz Stanislawski
2011-09-26 12:10 ` Mauro Carvalho Chehab
2011-09-26 12:17 ` Mauro Carvalho Chehab
2011-09-27 13:02 ` Tomasz Stanislawski
2011-09-27 14:10 ` Mauro Carvalho Chehab
2011-09-27 16:46 ` Tomasz Stanislawski
2011-09-28 8:01 ` Hans Verkuil
2011-09-28 8:29 ` Laurent Pinchart
2011-09-28 9:00 ` Hans Verkuil
2011-09-28 9:59 ` Tomasz Stanislawski
2011-09-28 10:40 ` Mauro Carvalho Chehab
2011-09-28 15:17 ` Tomasz Stanislawski
2011-09-28 11:20 ` Hans Verkuil
2011-09-26 10:03 ` Marek Szyprowski
2011-09-26 11:18 ` Mauro Carvalho Chehab
2011-09-26 12:45 ` Hans Verkuil
2011-09-26 11:13 ` Mauro Carvalho Chehab [this message]
2011-09-26 11:21 ` Marek Szyprowski
2011-09-26 13:30 ` Mauro Carvalho Chehab
2011-09-26 14:41 ` Laurent Pinchart
2011-09-27 8:23 ` Marek Szyprowski
2011-09-27 11:40 ` Mauro Carvalho Chehab
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=4E805E6E.3080007@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.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).