From: Haavard Skinnemoen <haavard.skinnemoen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
To: H Hartley Sweeten
<hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
Cc: "spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"hskinnemoen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org"
<hskinnemoen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>,
arjun rath <rath.arjun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: SPI-ADC
Date: Mon, 26 Apr 2010 09:26:46 +0200 [thread overview]
Message-ID: <20100426092646.11d8d71c@hskinnemoen-d830> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636D941949-gaq956PjLg32KbjnnMDalRurcAul1UnsRrxOEX5GOmysTnJN9+BGXg@public.gmane.org>
H Hartley Sweeten <hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org> wrote:
> The max124[0|1] is still a spi device so using the atmel_spi driver is
> the correct route. You just need to add the necessary support to the
> driver to handle the SPI_READY mode.
If there's only one master driver which supports this flag, it sounds
to me like it would be a _lot_ easier in the long run to instead teach
the device driver to deal with drivers which don't support this mode.
The atmel_spi hardware doesn't have any hardware support for this mode
as far as I know, so the implementation will be very CPU-intensive
either way.
But the best solution is probably to replace the ADC with one that
doesn't have a completely boneheaded interface.
Haavard
------------------------------------------------------------------------------
next prev parent reply other threads:[~2010-04-26 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 6:20 SPI-ADC arjun rath
[not found] ` <o2idc6d3181004212320neaf99b0az27938c369e1a5557-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-22 16:23 ` SPI-ADC H Hartley Sweeten
[not found] ` <y2tdc6d3181004222208uf6f4a9ecl7d0e2f084fd56a08@mail.gmail.com>
[not found] ` <y2tdc6d3181004222208uf6f4a9ecl7d0e2f084fd56a08-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-23 16:58 ` SPI-ADC H Hartley Sweeten
[not found] ` <0D753D10438DA54287A00B0270842697636D941949-gaq956PjLg32KbjnnMDalRurcAul1UnsRrxOEX5GOmysTnJN9+BGXg@public.gmane.org>
2010-04-26 7:26 ` Haavard Skinnemoen [this message]
2010-04-26 7:40 ` SPI-ADC arjun rath
-- strict thread matches above, loose matches on Subject: below --
2010-02-13 5:48 SPI-ADC arjun rath
[not found] ` <dc6d3181002122148v6451ebffka164de288738485d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-13 6:38 ` SPI-ADC Ben Gamari
2010-02-13 13:48 ` [spi-devel-general] SPI-ADC Linus Walleij
2010-02-13 16:51 ` Jonathan Cameron
2010-02-13 21:20 ` Linus Walleij
[not found] ` <63386a3d1002131320u5afbc35ak2bc3533aab3f1e54-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-15 4:29 ` SPI-ADC arjun rath
[not found] ` <dc6d3181002142029j13a9e57la45aa90a269404fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-15 8:49 ` SPI-ADC jassi brar
2010-02-15 17:33 ` SPI-ADC Ben Gamari
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=20100426092646.11d8d71c@hskinnemoen-d830 \
--to=haavard.skinnemoen-aife0yeh4naavxtiumwx3w@public.gmane.org \
--cc=hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org \
--cc=hskinnemoen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
--cc=rath.arjun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).