From: Lars-Peter Clausen <lars@metafoo.de>
To: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: JESD204B support
Date: Fri, 19 Jun 2015 10:10:56 +0200 [thread overview]
Message-ID: <5583CE90.4050203@metafoo.de> (raw)
In-Reply-To: <CAM=Q2cv5r=F25uFpZXUQh1vj3Dd+a91hJoQ2A+oBdPhTMts+qg@mail.gmail.com>
On 06/19/2015 08:45 AM, Shubhrajyoti Datta wrote:
> On Thu, Jun 18, 2015 at 8:44 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>> On 06/18/2015 02:46 PM, Shubhrajyoti Datta wrote:
>>>
>>> Hi ,
>>>
>>> I was wondering if there is any plans or existing support for JESD204B.
>>> I was thinking of IIO. However any other ideas may be welcome.
>>
>>
>> Yes, IIO is the way to go. We have some out-of-tree drivers for JESD204B
>> chips.
>
> Great.
>
>> They are not quite ready yet, but we'll get there
> May be sharing early could get some alignment.
It mostly all at
https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/iio/adc/
E.g.
https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/iio/adc/cf_axi_jesd204b_v51.c
and
https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/iio/adc/cf_axi_adc_core.c
But it is nothing you'd want to copy infrastructure wise. The drivers have a
lot of built-in assumptions about the underlying topology and will really
only work with a certain JESD converter and JESD host controller combination.
>
>
> The thing is the data rate change and the related clock tree
> dependencies that it may bring.
> That part looked tricky to me. So thought of talking to the community
> before sketching something
> not compatible. :-)
Yeah, I think that's one of the parts we haven't really figured out yet. The
JESD transceiver that we are using on the host system unfortunately is not
re-programmable at runtime.
But otherwise we are using the normal clock framework to model the various
clock relationships and use it to enable/disable and setup the clocks as
required.
- Lars
next prev parent reply other threads:[~2015-06-19 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:46 JESD204B support Shubhrajyoti Datta
2015-06-18 15:14 ` Lars-Peter Clausen
2015-06-19 6:45 ` Shubhrajyoti Datta
2015-06-19 8:10 ` Lars-Peter Clausen [this message]
2015-06-22 5:41 ` Shubhrajyoti Datta
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=5583CE90.4050203@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=omaplinuxkernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.