Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
Am Wed, 4 Jul 2018 13:08:31 -0300
schrieb Mauro Carvalho Chehab :
> Em Sat, 12 May 2018 13:24:29 +0200
> Daniel Scheller escreveu:
>
> > From: Daniel Scheller
> >
> > Third iteration of the IOCTL patches for ddbridge, split into multiple
> > patches:
> >
From: Daniel Scheller
Add a break statement in set_params() for the SYS_DVBT(2) case to silence
this sparse warning:
drivers/media/dvb-frontends/tda18271c2dd.c:1144:3: warning: this statement
may fall through [-Wimplicit-fallthrough=]
as reported in Hans' daily media_tree builds.
Signed
From: Daniel Scheller
ddbridge has a few MDIO related remainders (defines, hwinfo struct) which
aren't of any use for the in-kernel driver at all (they're only used in
conjunction with the OctoNet SAT>IP boxes which the kernel driver doesn't
have any support for), so clean this up.
Signed-
From: Daniel Scheller
Adjustments to match the FPGA firmware, and the signal I/Q values are
reported as s16 types from the card firmware.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-mci.c | 2 +-
drivers/media/pci/ddbridge
From: Daniel Scheller
To avoid miscalculations related to the BER denominator, the shift
expression needs to be casted as ULL.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/stv0910.c | 4 ++--
1 file changed, 2 insertions(+), 2
From: Daniel Scheller
Throughout the function, dev->link[l] is used several times. Unclutter
this a bit by declaring a ddb_link var at the top of the function, assign
the address of dev->link[l] to it and use that var to access the link[]
struct member.
Picked up from the upstream ddd
From: Daniel Scheller
The SX8 cards by default do an automatic search for the PLS code. This
is not necessarily wanted as this can eventually be detected wrong, so
disable this.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-sx8
From: Daniel Scheller
In demod_attach_stv0910(), the LNBH25 IC is being blindly attached and,
if the result is bad, blindly attached on another possible I2C address.
The LNBH25 uses it's set_voltage function to test for the IC and will
print an error to the kernel log on failure. Prevent
From: Daniel Scheller
The MCI can report the command status more finegrained, so, add more
status code defines and update the MCI_SUCCESS macro.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-mci.h | 8 ++--
1 file changed, 6
From: Daniel Scheller
Recent FPGA firmware reports more data and values in sent command
responses. Adjust the mci_command and mci_result structs including it's
unions to match these changes and add a few comments explaining things.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel
From: Daniel Scheller
Update the copyright year information in the MCI headers to 2017-2018.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-mci.c | 6 +++---
drivers/media/pci/ddbridge/ddbridge-mci.h | 6 +++---
2 files changed
From: Daniel Scheller
Implement querying signal statistics from the MCI and report this data
in read_status() as DVBv5 statistics.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-mci.c | 47 ++-
1 file
From: Daniel Scheller
For better support for future MCI based cards, rename the mci struct
member to mci_ports to carry the number of ports on the cards, and add a
mci_type member to identify the card type to handle differing hardware.
Picked up from the upstream dddvb GIT.
Signed-off
From: Daniel Scheller
Take note that the SX8 IQ mode is only available on a single tuner, and
remove the MCI/SX8 DIAG CMD defines.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-mci.h | 24
1 file changed
From: Daniel Scheller
Split off all code specific to the MaxSX8 cards to a separate ddbridge-sx8
module and hook it up in the Makefile. This also adds evaluation of the
mci_type to allow for using different attach handling for different cards.
As different cards can implement things differently
From: Daniel Scheller
In preparation for splitting all MaxSX8 related code parts from the common
MCI code, prefix both mci_cmd() and mci_config() functions with ddb_,
remove the static marking and add matching function prototypes to
ddbridge-mci.h so these functions can be reused from other
From: Daniel Scheller
Allow for tuning to transponders with specific modulations in
set_parameters(). Setting a specific modulation will also enable lower
modulations.
Picked up from the upstream dddvb GIT. Upstream also has support for
APSK64/128/256 modulations which aren't supported yet
From: Daniel Scheller
Devices supporting dummy tuner operation can exist on any link, not only
on link 0, so fix this accordingly.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci/ddbridge/ddbridge-core.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Daniel Scheller
The I2C_COMMAND response reports an error in the I2C bus communication
using bit 17. Evaluate the response more thoroughly and log an error
if an I2C problem was detected.
Picked up from the upstream dddvb GIT.
Signed-off-by: Daniel Scheller
---
drivers/media/pci
From: Daniel Scheller
A bunch of commits as they appeared in the dddvb upstream GIT as of
2018-06-23, mainly cleanups, cosmetics and code move in preparation for
new MCI card types, plus improvements to the existing SX8 code, ie.
DVBv5 signal statistics.
Also fixes one sparse warning as being
From: Daniel Scheller
Change the start of the MCI ID range (internally used only) to 48 and
define an ID for the SX8 card type. Use this new ID to handle device
attachment.
This change is done in preparation for support of more MCI based cards.
Picked up from the upstream dddvb GIT.
Signed
From: Daniel Scheller
Fix one sparse warning:
drivers/media/dvb-frontends/mxl5xx.c:731:3: warning: this statement may
fall through [-Wimplicit-fallthrough=]
as seen in Hans' daily media_tree builds.
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/mxl5xx.c | 1 +
1 file
From: Daniel Scheller
There's a superfluous whitespace in the boilerplate license text in both
.c and .h files. Fix this.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/cxd2099.c | 2 +-
drivers/media/dvb-frontends/cxd2099.h | 2 +-
2
From: Daniel Scheller
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
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media
From: Daniel Scheller
Upstream committed a change to the dddvb driver package ([1]) that makes
things clear everything is licensed under the terms of the GPLv2-only.
So, apply the MODULE_LICENSE change to cxd2099 and, as things are sorted
now, apply SPDX license identifiers (and fix two spurious
From: Daniel Scheller
In commit 3db30defab4b ("use correct MODULE_LINCESE for GPL v2 only
according to notice in header") in the upstream repository for the
mentioned driver at https://github.com/DigitalDevices/dddvb.git, the
MODULE_LICENSE was fixed to "GPL v2" and is now
From: Daniel Scheller
The stv6111.h doesn't carry any header nor any licensing boilerplate at
all, so copy this from the main driver file stv6111.c. While at it,
apply the usual whitespace/blank line cleanup.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers
From: Daniel Scheller
The stv0910.h doesn't carry any header nor any licensing boilerplate at
all, so copy this from the main driver file stv0910.c. While at it,
apply the usual whitespace/blank line cleanup aswell.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
From: Daniel Scheller
mxl5xx.h doesn't carry any licensing boilerplate at all right now, so copy
the boilerplate over from the main driver file mxl5xx.c. Also, mxl5xx_defs
is missing a part of the licensing boilerplate text, so add it. While at
it, fix up some minor whitespace and blank line
From: Daniel Scheller
Upstream committed a change to the dddvb driver package ([1]) that makes
things clear everything is licensed under the terms of the GPLv2-only.
So, apply the MODULE_LICENSE change to ddbridge, mxl5xx, stv0910 and
stv6111, and, as things are sorted now, apply SPDX license
From: Daniel Scheller
Cleanup whitespaces and blank lines, remove wrong links to
http://www.gnu.org/copyleft/gpl.html (the driver is licensed under the
terms of GPLv2, but the link points to a copy of the GPLv3), and fix
the filename reference in ddbridge-i2c.h.
Cc: Ralph Metzler
Cc: Manfred
From: Daniel Scheller
As it is clear that the driver is licensed under the terms of GPLv2-only
by now, add a matching SPDX license identifier to all driver files.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/stv6111.c | 1 +
drivers
From: Daniel Scheller
As it is clear that the driver is licensed under the terms of GPLv2-only
by now, add a matching SPDX license identifier to all driver files.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/stv0910.c | 1
From: Daniel Scheller
As it is clear that the driver is licensed under the terms of GPLv2-only
by now, add a matching SPDX license identifier to all driver files.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media/dvb-frontends/mxl5xx.c | 1
From: Daniel Scheller
Since the boilerplates and MODULE_LICENSE are now in sync regarding the
used license (GPL v2 only), add a matching GPLv2 SPDX license identifier
to all files of the ddbridge driver.
Cc: Ralph Metzler
Cc: Manfred Voelkel
Signed-off-by: Daniel Scheller
---
drivers/media
From: Daniel Scheller
In commit 3db30defab4b ("use correct MODULE_LINCESE for GPL v2 only
according to notice in header") in the upstream repository for the
mentioned four drivers at https://github.com/DigitalDevices/dddvb.git
(plus a few more which aren't part of the mainline k
the more
generic function dma_request_slave_channel().
Signed-off-by: Robert Jarzmik <robert.jarz...@free.fr>
Reviewed-by: Daniel Mack <dan...@zonque.org>
---
sound/arm/pxa2xx-ac97.c | 14 ++
sound/arm/pxa2xx-pcm-lib.c | 6 +++---
sound/soc/pxa/pxa2xx
. is a 1-1 match to
ssp., and the channels are either "rx" or "tx".
- for device tree platforms, the dma node should be hooked into the
pxa2xx-ac97 or pxa-ssp-dai node.
Signed-off-by: Robert Jarzmik <robert.jarz...@free.fr>
Acked-by: Daniel Mack <dan...@zonque.org
Hi Robert,
Please refer to the attached patch instead of the one I sent earlier. I
missed to also remove the platform_get_resource(IORESOURCE_DMA) call.
Thanks,
Daniel
On Friday, May 18, 2018 11:31 PM, Daniel Mack wrote:
Hi Robert,
Thanks for this series.
On Monday, April 02, 2018 04:26
onditioning remote controls and decode the target
> temperature in bpf, and pass that to an input device.
Mauro, are you fine with this series going via bpf-next? How ugly would this
get with regards to merge conflicts wrt drivers/media/rc/?
Thanks,
Daniel
> Thanks,
>
> Sean Y
, and it's hardcoded to the same value
all the time, so I guess this is not the reason it doesn't work on
MIPI CSI anymore.
Daniel, could you test:
http://code.bulix.org/ki6kgz-339327?raw
[Note that there's a missing parenthesis in this snippet]
Hmm, no, that doesn't change anything. Streaming
a V4L2_CID_PIXEL_RATE control. The qcom camss
platform needs that in order to calculate its own clock rates. When I
tested this patch set, I hard-coded the setting the camss driver.
I can send a patch that adds this control once this patch set has landed.
Thanks,
Daniel
mtd/nand/raw/marvell_nand.c
recently, so this patch can be dropped. I attached a version for the new
driver which you can pick instead.
Thanks,
Daniel
>From c63bc40bdfe2d596e42919235840109a2f1b2776 Mon Sep 17 00:00:00 2001
From: Daniel Mack <dan...@zonque.org>
Date: Sat, 12 May 2018 2
seems
that writes to registers after 0x3035/0x3036/0x3037 seem to depend on
the values of these timing registers. You might need to leave these
values as dummies in the array. Confusing.
Any idea?
Thanks,
Daniel
a new regression
for me, unfortunately, possibly for the same reason. I'll dig a bit more.
What cameras are you testing this with? MIPI or parallel?
Thanks,
Daniel
Fixes: 5999f381e023 ("media: ov5640: Add horizontal and vertical totals")
Signed-off-by: Samuel Bobrowicz <s...@e
patch set be applied
on? I had no luck with media_tree/for-4.18-6.
Thanks,
Daniel
Let me know what you think,
Maxime
Changes from v2:
- Rebased on latest Sakari PR
- Fixed the issues reported by Hugues: improper FPS returned for
formats, improper rounding of the FPS, some with his s
On Tue, May 15, 2018 at 01:16:30PM +0100, Chris Wilson wrote:
> Quoting Ezequiel Garcia (2018-05-14 22:28:31)
> > On Mon, 2018-05-14 at 18:48 +0200, Daniel Vetter wrote:
> > > On Fri, May 11, 2018 at 08:27:41AM +0100, Chris Wilson wrote:
> > > > Quoting Ezequi
needs this behaviour so we
can discuss how to best handle your use-case.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
From: Daniel Scheller <d.schel...@gmx.net>
This patch adds back the IOCTL API/functionality which is present in the
upstream dddvb driver package. In comparison, the IOCTL handler has been
factored to a separate object (and with that, some functionality from
-core, such as re
From: Daniel Scheller <d.schel...@gmx.net>
drivers/media/pci/ddbridge exposes a few IOCTLs which are used by userspace
utilities to ie. update PCIe card's FPGA firmware.
The IOCTLs chosen are in the range 0xDD/0xE0 up to 0xDD/0xFF, with 0xDD as
sort of gimmick for "Digi
From: Daniel Scheller <d.schel...@gmx.net>
Add a uAPI header to define the IOCTLs and the related data structs used by
ddbridge, which currently are IOCTL_DDB_FLASHIO and IOCTL_DDB_IO. The
header can be included by userspace applications directly to make use of
the IOCTLs, and they even
From: Daniel Scheller <d.schel...@gmx.net>
Third iteration of the IOCTL patches for ddbridge, split into multiple
patches:
Patch 1 just adds the reservation/information of the used IOCTLs into
ioctl-numbers.txt in the Docs dir. Doc, s390 and LKML are Cc'ed on
this patch.
Patch 2 adds the
Hi Colin,
Am Tue, 8 May 2018 11:39:56 +0100
schrieb Colin Ian King <colin.k...@canonical.com>:
> On 08/05/18 11:38, Daniel Scheller wrote:
> > Hi Colin,
> >
> > Am Tue, 8 May 2018 00:08:42 +0100
> > schrieb Colin King <colin.k...@canonical.com>:
&g
From: Daniel Scheller <d.schel...@gmx.net>
CineS2 V7(A) and Octopus CI S2 Pro/Advanced cards support faster TS speeds
on the card's contained stv0910 demodulator when their FPGA was updated
with a recent (>= 1.7, version number applies to all mentioned cards)
vendor firmware. Enable th
From: Daniel Scheller <d.schel...@gmx.net>
In stop(), an (unlikely) out-of-bounds write error can occur when setting
the demod_in_use element indexed by state->demod to zero, as state->demod
isn't checked for being in the range of the array size of demod_in_use, and
state->demod
From: Daniel Scheller <d.schel...@gmx.net>
Add a tsspeed config option to struct stv0910_cfg which can be used by
users of the driver to set the (parallel) TS speed (higher speeds enable
support for higher bitrate transponders). If tsspeed isn't set in the
config, it'll default to a sane
From: Daniel Scheller <d.schel...@gmx.net>
Fixes two checkpatch warnings
WARNING: function definition argument 'xxx' should also have an identifier
name
in the ddb_mci_attach() prototype definition. checkpatch keeps complaining
on the "int (**fn_set_input)" as it seem
From: Daniel Scheller <d.schel...@gmx.net>
Four post-ddbridge-0.9.33 patches fixing and improving a few things:
Patch 1 adds protection into the new ddbridge-mci code against an
out-of-bounds array write access as reported by CoverityScan and brought
to attention by Colin Ian King.
Patch
k);
> state->started = 0;
Thanks for the patch, or - better - pointing this out. While it's
unlikely this will ever be an issue, I'm fine with changing the code
like that, but I'd prefer to change it a bit differently (ie.
DEMOD_STOPPED should be DEMOD_UNUSED, and I'd add defines for max.
tuners and use/compare against them).
I'll send out a different patch that will cover the potential
coverityscan problem throughout the end of the week.
Best regards,
Daniel Scheller
--
https://github.com/herrnst
Am Fri, 4 May 2018 12:51:02 -0300
schrieb Mauro Carvalho Chehab <mchehab+sams...@kernel.org>:
> Em Tue, 13 Mar 2018 23:18:03 +0100
> Daniel Scheller <d.scheller@gmail.com> escreveu:
>
> > From: Daniel Scheller <d.schel...@gmx.net>
> >
> > Ad
uiel Garcia <ezequ...@collabora.com>
Applied, thanks.
-Daniel
> ---
> drivers/dma-buf/sync_debug.h | 10 --
> 1 file changed, 10 deletions(-)
>
> diff --git a/drivers/dma-buf/sync_debug.h b/drivers/dma-buf/sync_debug.h
> index d615a89f774c..05e33f937ad0 100644
> --- a
one. Instead just check if the callback is present. Suggested by
Maarten.
Also move misplaced kerneldoc hunk to the right patch.
Cc: Maarten Lankhorst <maarten.lankho...@linux.intel.com>
Reviewed-by: Christian König <christian.koe...@amd.com> (v1)
Signed-off-by: Daniel Vetter <danie
- Intro section that links to how this is exposed to userspace.
- Lots more hyperlinks.
- Minor clarifications and style polish
v2: Add misplaced hunk of kerneldoc from a different patch.
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
On Fri, May 04, 2018 at 03:17:08PM +0200, Christian König wrote:
> Am 04.05.2018 um 11:25 schrieb Daniel Vetter:
> > On Fri, May 4, 2018 at 11:16 AM, Chris Wilson <ch...@chris-wilson.co.uk>
> > wrote:
> > > Quoting Daniel Vetter (2018-05-04 09:57:59)
> > &g
On Fri, May 4, 2018 at 11:16 AM, Chris Wilson <ch...@chris-wilson.co.uk> wrote:
> Quoting Daniel Vetter (2018-05-04 09:57:59)
>> On Fri, May 04, 2018 at 09:31:33AM +0100, Chris Wilson wrote:
>> > Quoting Daniel Vetter (2018-05-04 09:23:01)
>> > > On Fri, May
On Fri, May 04, 2018 at 09:31:33AM +0100, Chris Wilson wrote:
> Quoting Daniel Vetter (2018-05-04 09:23:01)
> > On Fri, May 04, 2018 at 10:17:22AM +0200, Daniel Vetter wrote:
> > > On Fri, May 04, 2018 at 09:09:10AM +0100, Chris Wilson wrote:
> > > > Quoting Dani
On Fri, May 04, 2018 at 10:17:22AM +0200, Daniel Vetter wrote:
> On Fri, May 04, 2018 at 09:09:10AM +0100, Chris Wilson wrote:
> > Quoting Daniel Vetter (2018-05-03 15:25:52)
> > > Almost everyone uses dma_fence_default_wait.
> > >
> > > v2: Also remove the BU
On Fri, May 04, 2018 at 09:09:10AM +0100, Chris Wilson wrote:
> Quoting Daniel Vetter (2018-05-03 15:25:52)
> > Almost everyone uses dma_fence_default_wait.
> >
> > v2: Also remove the BUG_ON(!ops->wait) (Chris).
>
> I just don't get the rationale for i
Almost everyone uses dma_fence_default_wait.
v2: Also remove the BUG_ON(!ops->wait) (Chris).
Reviewed-by: Christian König <christian.koe...@amd.com> (v1)
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Chris Wilson <ch...@chris-wilson.co.uk>
Cc: Sumit Semwal <
Let's remove this restriction.
Reviewed-by: Christian König <christian.koe...@amd.com>
Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustavo Padovan <gust...@padovan.org>
Cc: linux-media@vger.kernel.org
Cc: linaro-mm-...@
- Intro section that links to how this is exposed to userspace.
- Lots more hyperlinks.
- Minor clarifications and style polish
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustavo Padovan <gust...@padovan.org&g
Many drivers have a trivial implementation for ->enable_signaling.
Let's make it optional by assuming that signalling is already
available when the callback isn't present.
Reviewed-by: Christian König <christian.koe...@amd.com>
Signed-off-by: Daniel Vetter <daniel.vet...@intel.co
on the v4l side). Acked-by: me.
-Daniel
>
> On Saturday, 28 April 2018 23:50:19 EEST Laurent Pinchart wrote:
>> Hello,
>>
>> (Dave, there's a request for you below)
>>
>> This patch series adds support for CRC calculation to the rcar-du-drm
>> driver.
>>
The format specifier %p can leak kernel addresses
while not valuing the kptr_restrict system settings.
Use %pK instead of %p, which also evaluates whether
kptr_restrict is set.
Signed-off-by: Divya Ponnusamy <pdi...@codeaurora.org>
Signed-off-by: Daniel Rosenberg <dro...@google.com>
On Mon, Apr 30, 2018 at 10:49:00AM -0700, Eric Anholt wrote:
> Daniel Vetter <daniel.vet...@ffwll.ch> writes:
> > + /**
> > +* @fill_driver_data:
> > +*
> > +* Callback to fill in free-form debug info Returns amount of bytes
> > +* filled, o
On Sun, Apr 29, 2018 at 09:11:31AM +0200, Christian König wrote:
> Am 27.04.2018 um 08:17 schrieb Daniel Vetter:
> > When this was introduced in
> >
> > commit a519435a96597d8cd96123246fea4ae5a6c90b02
> > Author: Christian König <christian.koe...@amd.com>
>
- Intro section that links to how this is exposed to userspace.
- Lots more hyperlinks.
- Minor clarifications and style polish
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustavo Padovan <gust...@padovan.org&g
Almost everyone uses dma_fence_default_wait.
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustavo Padovan <gust...@padovan.org>
Cc: linux-media@vger.kernel.org
Cc: linaro-mm-...@lists.linaro.org
---
drivers/dma-buf/dma-
- Switch to inline member docs for dma_fence_ops.
- Mild polish all around.
- hyperlink all the things!
v2: - Remove the various [in] annotations, they seem really uncommon
in kerneldoc and look funny.
Signed-off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: Sumit Semwal <
Let's remove this restriction.
Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustavo Padovan <gust...@padovan.org>
Cc: linux-media@vger.kernel.org
Cc: linaro-mm-...@lists.linaro.org
Cc: Christian König <christian.koe...@amd.com&
Many drivers have a trivial implementation for ->enable_signaling.
Let's make it optional by assuming that signalling is already
available when the callback isn't present.
Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
Cc: Sumit Semwal <sumit.sem...@linaro.org>
Cc: Gustav
On Thu, Apr 26, 2018 at 11:09 AM, Christoph Hellwig <h...@infradead.org> wrote:
> On Wed, Apr 25, 2018 at 11:35:13PM +0200, Daniel Vetter wrote:
>> > get_required_mask() is supposed to tell you if you are safe. However
>> > we are missing lots of implementations of it
On Thu, Apr 26, 2018 at 11:24 AM, Christoph Hellwig <h...@infradead.org> wrote:
> On Thu, Apr 26, 2018 at 11:20:44AM +0200, Daniel Vetter wrote:
>> The above is already what we're implementing in i915, at least
>> conceptually (it all boils down to clflush instructions
On Thu, Apr 26, 2018 at 12:54 AM, Russell King - ARM Linux
<li...@armlinux.org.uk> wrote:
> On Wed, Apr 25, 2018 at 08:33:12AM -0700, Christoph Hellwig wrote:
>> On Wed, Apr 25, 2018 at 12:04:29PM +0200, Daniel Vetter wrote:
>> > - dma api hides the cache flushing require
On Thu, Apr 26, 2018 at 1:26 AM, Russell King - ARM Linux
<li...@armlinux.org.uk> wrote:
> On Wed, Apr 25, 2018 at 11:35:13PM +0200, Daniel Vetter wrote:
>> On arm that doesn't work. The iommu api seems like a good fit, except
>> the dma-api tends to get in the way a bit (d
On Wed, Apr 25, 2018 at 5:33 PM, Christoph Hellwig <h...@infradead.org> wrote:
> On Wed, Apr 25, 2018 at 12:04:29PM +0200, Daniel Vetter wrote:
>> > Coordinating the backport of a trivial helper in the arm tree is not
>> > the end of the world. Really, this cowbo
erything).
For display drivers the dma api mostly works, until you start sharing
buffers with other devices.
So from our perspective it looks fairly often that core folks just don't
want to support gpu use-cases, so we play a bit more cowboy and get things
done some other way. Since this has been
On Wed, Apr 25, 2018 at 12:09:05AM -0700, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 09:02:17AM +0200, Daniel Vetter wrote:
> > Can we please not nack everything right away? Doesn't really motivate
> > me to show you all the various things we're doing in gpu to make the
>
On Wed, Apr 25, 2018 at 8:43 AM, Christoph Hellwig <h...@infradead.org> wrote:
> On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
>> For more fun:
>>
>> https://www.spinics.net/lists/dri-devel/msg173630.html
>>
>> Yeah, sometimes we want
On Wed, Apr 25, 2018 at 8:13 AM, Daniel Vetter <dan...@ffwll.ch> wrote:
> On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig <h...@infradead.org> wrote:
>> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>>> Out of curiosity, how much virtual flu
On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig <h...@infradead.org> wrote:
> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>> Out of curiosity, how much virtual flushing stuff is there still out
>> there? At least in drm we've pretty much ignore this, and
On Tue, Apr 24, 2018 at 8:48 PM, Christoph Hellwig <h...@infradead.org> wrote:
> On Fri, Apr 20, 2018 at 05:21:11PM +0200, Daniel Vetter wrote:
>> > At the very lowest level they will need to be handled differently for
>> > many architectures, the question
get_algo(struct dvb_frontend *fe)
> +static enum dvbfe_algo get_algo(struct dvb_frontend *fe)
> {
> return DVBFE_ALGO_HW;
> }
Acked-by: Daniel Scheller <d.schel...@gmx.net>
Best regards,
Daniel Scheller
--
https://github.com/herrnst
gt; -static int get_algo(struct dvb_frontend *fe)
> +static enum dvbfe_algo get_algo(struct dvb_frontend *fe)
> {
> return DVBFE_ALGO_HW;
> }
Acked-by: Daniel Scheller <d.schel...@gmx.net>
Best regards,
Daniel Scheller
--
https://github.com/herrnst
Hi,
On Tuesday, April 24, 2018 12:22 PM, Sakari Ailus wrote:
> On Fri, Apr 20, 2018 at 11:44:18AM +0200, Daniel Mack wrote:
>> Add v4l2 controls to report the pixel and MIPI link rates of each mode.
>> The camss camera subsystem needs them to set up the correct hardware
>>
From: Daniel Scheller <d.schel...@gmx.net>
s/shifs/shifts/
Signed-off-by: Daniel Scheller <d.schel...@gmx.net>
---
drivers/media/pci/ngene/ngene-dvb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/pci/ngene/ngene-dvb.c
b/drivers/media/pci/ngene
From: Daniel Scheller <d.schel...@gmx.net>
Commit ee93340e98bc ("media: ngene: deduplicate I2C adapter evaluation")
added a helper to evaluate the I2C adapter to be used for demod/tuner
attachment based on the given ngene_channel, and that helper is used in
many attach functio
Hi,
On Wed, Apr 18, 2018 at 08:29:59PM +0200, Daniel Glöckner wrote:
> The VBI instruction queue read pointer points outside the VBI instruction
> queue and into the video y/packed CMDS (to 0x18+0x11*4). The values
> next to the iq rd ptr look ok.
>
> We only initialize the iq
1 - 100 of 1225 matches
Mail list logo
