I Mikhail Fridman. has selected you specially as one of my beneficiaries
for my Charitable Donation, Just as I have declared on May 23, 2016 to give
my fortune as charity.
Check the link below for confirmation:
http://www.ibtimes.co.uk/russias-second-wealthiest-man-mikhail-fridman-plans-leaving-1
On Fri, Mar 30, 2018 at 12:46:42PM -0600, Logan Gunthorpe wrote:
>
>
> On 29/03/18 07:58 PM, Jerome Glisse wrote:
> > On Thu, Mar 29, 2018 at 10:25:52AM -0600, Logan Gunthorpe wrote:
> >>
> >>
> >> On 29/03/18 10:10 AM, Christian König wrote:
> >>> Why not? I mean the dma_map_resource() function
On 29/03/18 07:58 PM, Jerome Glisse wrote:
> On Thu, Mar 29, 2018 at 10:25:52AM -0600, Logan Gunthorpe wrote:
>>
>>
>> On 29/03/18 10:10 AM, Christian König wrote:
>>> Why not? I mean the dma_map_resource() function is for P2P while other
>>> dma_map_* functions are only for system memory.
>>
>>
On 03/30/2018 04:21 PM, Akihiro TSUKADA wrote:
I simply cannot see why it cannot work. Just add i2c adapter and
suitable logic there. Transaction on your example is simply and there is
no problem to implement that kind of logic to demod i2c adapter.
I might be totally wrong, but...
i2c trans
On Thu, Mar 29, 2018 at 11:33:34PM -0700, Christoph Hellwig wrote:
> On Thu, Mar 29, 2018 at 09:58:54PM -0400, Jerome Glisse wrote:
> > dma_map_resource() is the right API (thought its current implementation
> > is fill with x86 assumptions). So i would argue that arch can decide to
> > implement i
> I simply cannot see why it cannot work. Just add i2c adapter and
> suitable logic there. Transaction on your example is simply and there is
> no problem to implement that kind of logic to demod i2c adapter.
I might be totally wrong, but...
i2c transactions to a tuner must use:
1. usb_control_ms
Hi all,
As was suggested to me during the Portland ELC I have created a wiki page
listing open
source projects in the media subsystem for which we need volunteers.
https://www.linuxtv.org/wiki/index.php/Media_Open_Source_Projects:_Looking_for_Volunteers
These are all projects that are limited t
V4L2_CID_DV_RX_POWER_PRESENT refers to a receiver, not a transmitter.
Signed-off-by: Hans Verkuil
---
diff --git a/Documentation/media/uapi/v4l/extended-controls.rst
b/Documentation/media/uapi/v4l/extended-controls.rst
index d5f3eb6e674a..03931f9b1285 100644
--- a/Documentation/media/uapi/v4l/ex
On 30/03/18 09:23, asadpt iqroot wrote:
> Hi Hans,
>
> Thanks for the reply.
>
> In HDMI receivers, when we need to use this control. What scenario?
https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/extended-controls.html#digital-video-control-reference
"Detects whether the receiver r
Hi Hans,
Thanks for the reply.
In HDMI receivers, when we need to use this control. What scenario?
-Thanks.
On 30 March 2018 at 12:13, Hans Verkuil wrote:
> On 30/03/18 08:16, asadpt iqroot wrote:
>> Hi All,
>>
>> In reference sensor drivers, they used the
>> V4L2_CID_DV_RX_POWER_PRESENT v4l2
Hi All,
Need to write the Sensor driver. I have the below doubts:
1. What are the dependencies between the bridge driver and Sensor driver?
2. To write the sensor driver, what are the things, we need to look in
bridge driver?
3. What are the Sensor driver functions called from bridge driver.
4 .
11 matches
Mail list logo
