linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] iio: frequency: New driver for Analog Devices ADF4350/ADF4351 Wideband Synthesizers
Date: Fri, 11 May 2012 13:31:56 +0100	[thread overview]
Message-ID: <4FAD06BC.7020905@cam.ac.uk> (raw)
In-Reply-To: <4FACF459.3020800@analog.com>

On 5/11/2012 12:13 PM, Michael Hennerich wrote:
> On 05/11/2012 09:45 AM, Jonathan Cameron wrote:
>> On 5/11/2012 8:43 AM, Jonathan Cameron wrote:
>>> On 5/11/2012 8:41 AM, Michael Hennerich wrote:
>>>> On 05/10/2012 02:36 PM, Jonathan Cameron wrote:
>>>>> On 5/8/2012 4:34 PM, Michael Hennerich wrote:
>>>>>> On 05/08/2012 04:51 PM, Jonathan Cameron wrote:
>>>>>>> On 5/7/2012 2:49 PM, michael.hennerich@analog.com wrote:
>>>>>>>> From: Michael Hennerich<michael.hennerich@analog.com>
>>>>>>>>
>>>>>>>>
>>>>>>>> +
>>>>>>>> +static const struct iio_chan_spec_ext_info adf4350_ext_info[] = {
>>>>>>>> + /* Ideally we use IIO_CHAN_INFO_FREQUENCY, but there are
>>>>>>>> + * values> 2^32 in order to support the entire frequency range
>>>>>>>> + * in Hz. Using scale is a bit ugly.
>>>>>>>> + */
>>>>>>> hmm.. Add IIO_VAL_MEGA_PLUS_INT.. We were always going to need a
>>>>>>> bigger
>>>>>>> version at somepoint...
>>>>>> Well - we then need an s64, however read|write_raw feature s32 for
>>>>>> val and val2. So shall we pass low word in val and high word in val2?
>>>>> I was thinking
>>>>> val*1e6 + val2 would fit with what we have done elsewhere? Is that
>>>>> enough room?
>>>> Hi Jonathan,
>>>>
>>>> IIO_VAL_MEGA_PLUS_INT versus IIO_VAL_LONG_LONG
>>>>
>>>> It is enough room. But I wonder why we would do costly divide and
>>>> modulus operations, when we can do sifts and ANDs? Splitting a s64
>>>> would
>>>> give is the maximum available room with very little overhead.
>>> human readability. I'm anti breaking that if we can possibly avoid it.
>> That an consistency with the others. There it makes sense because of
>> breaking round the decimal point.
> Hi Jonathan,
>
> Ideally I leave the driver as is.
Leave it for now. Lets revisit this in the future...
>
> If we really want the keep consistency, I would need to make integer
> type s64, that will add a lot of unnecessary overhead.
Agreed.  Might need it for other reasons at somepoint, but we put
a fair bit of effort into avoiding this in the first place, so would
be nice not to have to add it now!
>
>
>>>> Thoughts?
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>


  reply	other threads:[~2012-05-11 12:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 13:49 [PATCH] iio: frequency: New driver for Analog Devices ADF4350/ADF4351 Wideband Synthesizers michael.hennerich
2012-05-08 14:51 ` Jonathan Cameron
2012-05-08 15:34   ` Michael Hennerich
2012-05-10 12:36     ` Jonathan Cameron
2012-05-11  7:41       ` Michael Hennerich
2012-05-11  7:43         ` Jonathan Cameron
2012-05-11  7:45           ` Jonathan Cameron
2012-05-11 11:13             ` Michael Hennerich
2012-05-11 12:31               ` Jonathan Cameron [this message]
2013-06-03  8:18         ` Michael Hennerich
2013-06-04 18:33           ` Jonathan Cameron

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=4FAD06BC.7020905@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@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).