From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Drivers <Drivers@analog.com>
Subject: Re: [RFC PATCH] staging: iio: adc: ad7476 new SPI ADC driver
Date: Fri, 08 Oct 2010 12:14:08 +0100 [thread overview]
Message-ID: <4CAEFD00.4090008@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917712F35A102B4@LIMKCMBX1.ad.analog.com>
On 10/08/10 12:05, Hennerich, Michael wrote:
> Jonathan Cameron wrote on 2010-10-08:
>> On 10/07/10 15:36, michael.hennerich@analog.com wrote:
>>> From: Michael Hennerich <michael.hennerich@analog.com>
>>>
>>> New driver handling: AD7475, AD7476, AD7477, AD7478, AD7466, AD7467,
>>> AD7468, AD7495 SPI micropower and high speed 12-/10-/8-Bit ADCs
>>
>> Hi Michael,
>>
>> Another pretty clean driver. Thanks, it makes reviewing much easier!
>> A few more suggestions this morning.
>>
>> * Might be a cache line issue with having buffer directly allocated
>> inside the state structure. In summary the issue is that another
>> element of the structure may be touched whilst dma is occuring into
>> buffer. With really bad luck this can mean that the value dma'd in is
>> wiped out with that in the cache before it is read. If I'm missing a
>> reason we are fine here, please tell me.
>
> Hi Jonathan,
>
> Thanks for your detailed review!
>
> I remember this conversation on linux-input. It was also around my AD7877
> touch screen driver. I'm not a friend of malloc and free short junks of data
> every time we make a transfer. I'll probably add the ____cacheline_aligned thing
> to the data buffer.
That will do, or just do the allocation once and put a pointer to it in the
structure (which is what a lot of in tree drivers do).
>
>> This stuff always gives me a
>> headache.
>> * Don't (I think) need scan_attrs in chip info structure.
>> They all seem to be set to the same pointer. Guess you can probably
>> shift the scan el code off into the ring buffer file.
>
> Well I did it that way for future usage - I'm going to add support for more
> SPI ADC devices to that driver in future. I remove it until it is actually
> used.
cool. Best that way or people will start assuming it's necessary even if
their drivers don't need it.
>
>> * Is platform data vital? Probably not if using the id_table.
>
> When using id_table together with the regulator framework, we don't need it.
>
>> * Could use helper to alloc the pollfunc.
>
> Will do.
>
>> * I may be imagining issues that don't exist with the bit
>> about whether the the contents of spi elements is guaranteed
>> not to be eaten by the bus drivers! Worth verifying perhaps though?
>
> I think it is - at least I have done various drivers doing the same here.
> Without any complains yet...
Cool.
>
> Greetings,
> Michael
>
> Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
> Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
>
>
>
prev parent reply other threads:[~2010-10-08 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 14:36 [RFC PATCH] staging: iio: adc: ad7476 new SPI ADC driver michael.hennerich
2010-10-07 17:17 ` Jonathan Cameron
2010-10-08 8:33 ` Hennerich, Michael
2010-10-08 9:58 ` Jonathan Cameron
2010-10-08 11:05 ` Hennerich, Michael
2010-10-08 11:14 ` Jonathan Cameron [this message]
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=4CAEFD00.4090008@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Drivers@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=linux-iio@vger.kernel.org \
/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