From mboxrd@z Thu Jan 1 00:00:00 1970 From: arjun rath Subject: Re: SPI-ADC Date: Mon, 26 Apr 2010 13:10:56 +0530 Message-ID: References: <0D753D10438DA54287A00B0270842697636D940B1C@AUSP01VMBX24.collaborationhost.net> <0D753D10438DA54287A00B0270842697636D941949@AUSP01VMBX24.collaborationhost.net> <20100426092646.11d8d71c@hskinnemoen-d830> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: "spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org" , "hskinnemoen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org" To: Haavard Skinnemoen Return-path: In-Reply-To: <20100426092646.11d8d71c@hskinnemoen-d830> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-spi.vger.kernel.org >> 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 Now i written the program with simple IO port reading/writing since those pins can be also configured as gpio pins.And when pulling the CS line LOW and checking the probe DOUT data is showing in the CRO but while reading the DOUT pin it always shows 1(high) only. Really its getting tougher and tougher On Mon, Apr 26, 2010 at 12:56 PM, Haavard Skinnemoen wrote: > H Hartley Sweeten wrote: >> The max124[0|1] is still a spi device so using the atmel_spi driver is >> the correct route. =A0You 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 > ---------------------------------------------------------------------------= ---