From: pankaj chauhan <pankaj.chauhan@freescale.com>
To: Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"Getz, Robin" <robin.getz@analog.com>
Cc: Goyal Akhil-B35197 <B35197@freescale.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chauhan Pankaj-B32944 <B32944@freescale.com>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Lars-Peter Clausen <lars-peter.clausen@analog.com>
Subject: Re: [PATCH 3/5] drivers/misc: rf/ad9361: AD9361 device driver for Radio phy
Date: Fri, 5 Jul 2013 11:44:08 +0530 [thread overview]
Message-ID: <51D66430.60209@freescale.com> (raw)
In-Reply-To: <20130703193640.GF27646@sirena.org.uk>
On 7/4/2013 1:06 AM, Mark Brown wrote:
> On Thu, Jun 20, 2013 at 04:05:20PM +0530, pankaj chauhan wrote:
>
>> Yes modifying registers from user space is part of the patch set and
>> register read/write interface is aimed only for two purposes:
>>
>> 1. Debugging : taking register dumps etc.
>
> Use regmap, it should have the infrastructure you need here.
>
Thanks! I looked into regmap, and it is exactly what we want. We'll
remove reg read/write from our patch and use regmap.
>> 2. Initializing AD9361 using Low level script generated by ADI GUI tool.
>
> This sounds like generating a firmmware blob that the driver can load.
> You may have to cook the GUI output to be more amenable to loading in
> the kernel (or persuade the GUI guys to generate something useful here).
>
Yes it is kind of generating firmware blob from GUI tool. They reason
why we choose to initialize AD9361 using script generated by GUI tool
was lack of our insight in AD9361, and script is the quickest way to
bring-up AD9361. This GUI is developed by analog devices, so we don't
have much control on it. Lars and Robin are developing full fledged
driver for Ad9661, We intend to use that driver only, that's why in next
version of patch we'll remove AD9361 driver from our patchset, and
integrate with Lars' driver once it is available.
next prev parent reply other threads:[~2013-07-05 6:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 8:09 [PATCH 0/5] Radio device framework akhil.goyal
2013-06-17 8:09 ` [PATCH 1/5] drivers/misc: Support for RF interface " akhil.goyal
2013-06-17 8:09 ` [PATCH 2/5] drivers/misc/rf: AIC: Freescale Antenna Interface controller driver akhil.goyal
2013-06-17 8:09 ` [PATCH 3/5] drivers/misc: rf/ad9361: AD9361 device driver for Radio phy akhil.goyal
2013-06-17 8:09 ` [PATCH 4/5] binding: Add device tree bindings for freescale AIC and AD phy akhil.goyal
2013-06-17 8:09 ` [PATCH 5/5] BSC9131rdb/dts: Add nodes for supporting AIC and AD PHY akhil.goyal
2013-06-19 12:57 ` [PATCH 3/5] drivers/misc: rf/ad9361: AD9361 device driver for Radio phy Lars-Peter Clausen
2013-06-19 14:30 ` Greg KH
2013-06-19 14:58 ` Arnd Bergmann
2013-06-20 10:35 ` pankaj chauhan
2013-06-21 23:46 ` pankaj chauhan
2013-06-24 8:19 ` Getz, Robin
2013-06-24 12:05 ` pankaj chauhan
2013-07-03 19:36 ` Mark Brown
2013-07-05 6:14 ` pankaj chauhan [this message]
2013-06-17 21:28 ` [PATCH 1/5] drivers/misc: Support for RF interface device framework Arnd Bergmann
2013-06-18 7:44 ` Akhil Goyal
2013-06-18 13:40 ` Arnd Bergmann
2013-06-19 6:00 ` Akhil Goyal
2013-06-19 11:31 ` Lars-Peter Clausen
2013-06-20 10:47 ` pankaj chauhan
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=51D66430.60209@freescale.com \
--to=pankaj.chauhan@freescale.com \
--cc=B32944@freescale.com \
--cc=B35197@freescale.com \
--cc=Michael.Hennerich@analog.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lars-peter.clausen@analog.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.getz@analog.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).