<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/dvb-frontends, branch linux-4.20.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.20.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.20.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-11-27T18:51:32Z</updated>
<entry>
<title>media: dvb-pll: don't re-validate tuner frequencies</title>
<updated>2018-11-27T18:51:32Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-11-23T17:10:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3420f65cbbd0555049bd02394bed33a0ef74d860'/>
<id>urn:sha1:3420f65cbbd0555049bd02394bed33a0ef74d860</id>
<content type='text'>
The dvb_frontend core already checks for the frequencies. No
need for any additional check inside the driver.

It is part of the fixes for the following bug:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1116374

Fixes: a3f90c75b833 ("media: dvb: convert tuner_info frequencies to Hz")
Reported-by: Stakanov Schufter &lt;stakanov@eclipso.eu&gt;
Reported-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Cc: stable@vger.kernel.org # For 4.19
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: dvb-pll: fix tuner frequency ranges</title>
<updated>2018-11-27T18:50:58Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-11-20T10:19:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3d8e450f517cdb33da77827ec75929354753e9c0'/>
<id>urn:sha1:3d8e450f517cdb33da77827ec75929354753e9c0</id>
<content type='text'>
Tuners should report frequencies in Hz. That works fine on most
drivers, but, in the case of dvb-pll, some settings are for
satellite tuners, while others are for terrestrial/cable ones.

The code was trying to solve it at probing time, but that doesn't
work, as, when _attach is called, the delivery system may be wrong.

Fix it by ensuring that all frequencies are in Hz at the per-tuner
max/min values.

While here, add a debug message, as this would help to debug any
issues there.

It partially fixes the following bug:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1116374

Fixes: a3f90c75b833 ("media: dvb: convert tuner_info frequencies to Hz")
Reported-by: Stakanov Schufter &lt;stakanov@eclipso.eu&gt;
Reported-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Cc: stable@vger.kernel.org # For 4.19
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'media/v4.20-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media</title>
<updated>2018-10-31T17:53:29Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2018-10-31T17:53:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b3491d8430dd25f0a4e00c33d60da22a9bd9d052'/>
<id>urn:sha1:b3491d8430dd25f0a4e00c33d60da22a9bd9d052</id>
<content type='text'>
Pull new experimental media request API from Mauro Carvalho Chehab:
 "A new media request API

  This API is needed to support device drivers that can dynamically
  change their parameters for each new frame. The latest versions of
  Google camera and codec HAL depends on such feature.

  At this stage, it supports only stateless codecs.

  It has been discussed for a long time (at least over the last 3-4
  years), and we finally reached to something that seem to work.

  This series contain both the API and core changes required to support
  it and a new m2m decoder driver (cedrus).

  As the current API is still experimental, the only real driver using
  it (cedrus) was added at staging[1]. We intend to keep it there for a
  while, in order to test the API. Only when we're sure that this API
  works for other cases (like encoders), we'll move this driver out of
  staging and set the API into a stone.

  [1] We added support for the vivid virtual driver (used only for
  testing) to it too, as it makes easier to test the API for the ones
  that don't have the cedrus hardware"

* tag 'media/v4.20-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: (53 commits)
  media: dt-bindings: Document the Rockchip VPU bindings
  media: platform: Add Cedrus VPU decoder driver
  media: dt-bindings: media: Document bindings for the Cedrus VPU driver
  media: v4l: Add definition for the Sunxi tiled NV12 format
  media: v4l: Add definitions for MPEG-2 slice format and metadata
  media: videobuf2-core: Rework and rename helper for request buffer count
  media: v4l2-ctrls.c: initialize an error return code with zero
  media: v4l2-compat-ioctl32.c: add missing documentation for a field
  media: media-request: update documentation
  media: media-request: EPERM -&gt; EACCES/EBUSY
  media: v4l2-ctrls: improve media_request_(un)lock_for_update
  media: v4l2-ctrls: use media_request_(un)lock_for_access
  media: media-request: add media_request_(un)lock_for_access
  media: vb2: set reqbufs/create_bufs capabilities
  media: videodev2.h: add new capabilities for buffer types
  media: buffer.rst: only set V4L2_BUF_FLAG_REQUEST_FD for QBUF
  media: v4l2-ctrls: return -EACCES if request wasn't completed
  media: media-request: return -EINVAL for invalid request_fds
  media: vivid: add request support
  media: vivid: add mc
  ...
</content>
</entry>
<entry>
<title>media: au8522: declare its own pads</title>
<updated>2018-09-17T17:16:19Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-08-01T09:06:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=44fd653bde54e49308efb77d121b66afae07d652'/>
<id>urn:sha1:44fd653bde54e49308efb77d121b66afae07d652</id>
<content type='text'>
As we don't need anymore to share pad numbers with similar
drivers, use its own pad definition instead of a global
model.

Acked-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l2: taint pads with the signal types for consumer devices</title>
<updated>2018-09-17T17:16:19Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-07-31T12:03:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c1a37dd5e87dc6a4c37e5fc68d7b26fb4a3ef097'/>
<id>urn:sha1:c1a37dd5e87dc6a4c37e5fc68d7b26fb4a3ef097</id>
<content type='text'>
Consumer devices are provided with a wide different range of types
supported by the same driver, allowing different configutations.

In order to make easier to setup media controller links, "taint"
pads with the signal type it carries.

While here, get rid of DEMOD_PAD_VBI_OUT, as the signal it carries
is actually the same as the normal video output.

The difference happens at the video/VBI interface:
	- for VBI, only the hidden lines are streamed;
	- for video, the stream is usually cropped to hide the
	  vbi lines.

Acked-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l2: remove VBI output pad</title>
<updated>2018-09-17T17:16:19Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-07-31T16:48:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=092a37875a22fbb75098e834fb1cc1c6220f0eaa'/>
<id>urn:sha1:092a37875a22fbb75098e834fb1cc1c6220f0eaa</id>
<content type='text'>
The signal there is the same as the video output (well,
except for sliced VBI, but let's simplify the model and ignore
it, at least for now - as it is routed together with raw
VBI).

Acked-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: drxj: fix spelling mistake in fall-through annotations</title>
<updated>2018-09-12T15:21:52Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2018-09-03T20:26:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=78cf8c842c111df656c63b5d04997ea4e40ef26a'/>
<id>urn:sha1:78cf8c842c111df656c63b5d04997ea4e40ef26a</id>
<content type='text'>
Replace "falltrough" with a proper "fall through" annotation.

This fix is part of the ongoing efforts to enabling
-Wimplicit-fallthrough

Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: dvb-frontends: add LNBH29 LNB supply driver</title>
<updated>2018-09-12T13:24:41Z</updated>
<author>
<name>Katsuhiro Suzuki</name>
</author>
<published>2018-08-03T02:08:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1b09dd9ff8a59b945fe8b5c4e4b8416a63252cac'/>
<id>urn:sha1:1b09dd9ff8a59b945fe8b5c4e4b8416a63252cac</id>
<content type='text'>
Add support for STMicroelectronics LNBH29 LNB supply driver.

Signed-off-by: Katsuhiro Suzuki &lt;suzuki.katsuhiro@socionext.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: mxl5xx: add a fall-trough annotation</title>
<updated>2018-09-12T12:24:54Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-09-12T12:19:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dfb7bcf0af2d819a01a978a5fd475b96a0700cb3'/>
<id>urn:sha1:dfb7bcf0af2d819a01a978a5fd475b96a0700cb3</id>
<content type='text'>
As pointed by Daniel Scheller &lt;d.scheller@gmx.net&gt;, sparse
warns that a segment may fall through. We're deprecating
this warning in favor of gcc 8 equivalent warning.

In this specific case, the code for DVB-S applies for DVB-S2.
In a matter of fact, several things there (like rolloff
factor logic) assume that the transponder is DVB-S2.

So, add the corresponding fall-trough markup, for gcc to
properly ignore it.

Reported-by: Daniel Scheller &lt;d.scheller@gmx.net&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: dvb-frontends/cxd2099: add SPDX license identifier</title>
<updated>2018-09-12T11:24:08Z</updated>
<author>
<name>Daniel Scheller</name>
</author>
<published>2018-06-19T18:51:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3dae3c96a5a893f94f127dd4d5f58697bd234d1b'/>
<id>urn:sha1:3dae3c96a5a893f94f127dd4d5f58697bd234d1b</id>
<content type='text'>
As both the MODULE_LICENSE and the boilerplates are now in sync and clear
that the driver is licensed under the terms of the GPLv2-only, add a
matching SPDX license identifier tag.

Cc: Ralph Metzler &lt;rjkm@metzlerbros.de&gt;
Cc: Manfred Voelkel &lt;mvoelkel@DigitalDevices.de&gt;
Signed-off-by: Daniel Scheller &lt;d.scheller@gmx.net&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
</feed>
