From: Vladimir Zapolskiy <vz@mleia.com>
To: Stuvart S <lovelinuxdeeply@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: TI Deserializer DT node configuration
Date: Tue, 26 Nov 2019 18:52:38 +0200 [thread overview]
Message-ID: <8137b15e-084d-417a-6ee8-b425b74140df@mleia.com> (raw)
In-Reply-To: <CAAMGra5wp8o3DAFQdYk3Ky2oaWaNcX-o4gejW7jro5Rm1pkVug@mail.gmail.com>
Hello Stuvart,
On 11/26/19 5:55 PM, Stuvart S wrote:
> Hello team,
>
> I am integrating DS90UB964 deserializer into my custom board based on
> Rcar H3 Salvator XS. Deserializer is connected in i2c6.Also I have my
> four serializers as DS90UB913 and cameras OV10635.
>
> Can any one please help with the following?
>
> How Deserializer connects to Serializer in DT node?I came accross
> about the terms remote i2c, i2c-mux,i2c-atr.but I dont understand.I am
> not using any i2c switches.
> Any DT example is helpful for me
>
once in the past I've shared the essential part of my device drivers
and the device tree configuration of connecting a serializer/deserializer
to a display panel [1][2]. Unfortunately for dealing with camera sensors
there should be one more device driver present, and MIPI CSI-2 controllers
are very specific to particular deserializer/serializer ICs.
Both TI DS90UB964 and DS90UB913 are supported in my driver suite,
however your hardware configuration may require some adjustments, also
note that my selected approach is different from Luca's one, and to my
knowledge anyone's published work is still under development.
I feel I have to find more time and complete the driver series,
the precondition is quite difficult though...
[1] https://lore.kernel.org/lkml/f0a52a64-a7e7-b266-a402-1279036fad36@mleia.com/
[2] https://lore.kernel.org/lkml/20181012060314.GU4939@dell/T/#mead5ea226550b6f0
Slides for introduction into the patch series:
* https://schd.ws/hosted_files/ossalsjp18/8a/vzapolskiy_als2018.pdf
* https://events19.linuxfoundation.org/wp-content/uploads/2018/07/Vladimir_Zapolskiy_Bridging.pdf
Hope it helps.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2019-11-26 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:55 TI Deserializer DT node configuration Stuvart S
2019-11-26 16:11 ` Baruch Siach
2019-11-26 16:17 ` Stuvart S
2019-11-26 16:52 ` Vladimir Zapolskiy [this message]
2019-11-26 17:34 ` Stuvart S
[not found] ` <42a4508d-c199-4ab0-0c62-7387be3b8d55@ideasonboard.com>
[not found] ` <CAAMGra4cq+hsVcG2A_-WBDiDzkBc+1t8JjEJEhXd8RJb6ocqiw@mail.gmail.com>
[not found] ` <CAAMGra7AVGYSHcqJ1sW30H9ChiSRQq4Tfpx2yfBUkrF4Qf6mEQ@mail.gmail.com>
2020-01-15 8:45 ` Anjali S S
2020-01-15 8:49 ` Anjali S S
2020-01-15 8:59 ` Anjali S S
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=8137b15e-084d-417a-6ee8-b425b74140df@mleia.com \
--to=vz@mleia.com \
--cc=linux-media@vger.kernel.org \
--cc=lovelinuxdeeply@gmail.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).