public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: David Lechner <david@lechnology.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Sekhar Nori <nsekhar@ti.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 087/209] ARM: dts: da850-lego-ev3: slow down A/DC as much as possible
Date: Thu, 21 Nov 2019 22:24:22 -0500	[thread overview]
Message-ID: <20191122032422.GK16867@sasha-vm> (raw)
In-Reply-To: <96753746-79ae-3db2-c6d8-e4d5615c0354@lechnology.com>

On Wed, Nov 13, 2019 at 10:10:30AM -0600, David Lechner wrote:
>On 11/12/19 7:48 PM, Sasha Levin wrote:
>>From: David Lechner <david@lechnology.com>
>>
>>[ Upstream commit aea4762fb46e048c059ff49565ee33da07c8aeb3 ]
>>
>>Due to the electrical design of the A/DC circuits on LEGO MINDSTORMS EV3,
>>if we are reading analog values as fast as possible (i.e. using DMA to
>>service the SPI) the A/DC chip will read incorrect values - as much as
>>0.1V off when the SPI is running at 10MHz. (This has to do with the
>>capacitor charge time when channels are muxed in the A/DC.)
>>
>>This patch slows down the SPI as much as possible (if CPU is at 456MHz,
>>SPI runs at 1/2 of that, so 228MHz and has a max prescalar of 256, so
>>we could get ~891kHz, but we're just rounding it to 1MHz). We also use
>>the max allowable value for WDELAY to slow things down even more.
>>
>>These changes reduce the error of the analog values to about 5mV, which
>>is tolerable.
>>
>>Commits a3762b13a596 ("spi: spi-davinci: Add support for SPI_CS_WORD")
>>and e2540da86ef8 ("iio: adc: ti-ads7950: use SPI_CS_WORD to reduce
>>CPU usage") introduce changes that allow DMA transfers to be used, so
>>this slow down is needed now.
>>
>
>I doubt that the commits above would be backported, so it does not
>make sense to backport this patch.

I've dropped it, thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2019-11-22  3:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191113015025.9685-1-sashal@kernel.org>
2019-11-13  1:46 ` [PATCH AUTOSEL 4.19 003/209] ARM: dts: dra7: Enable workaround for errata i870 in PCIe host mode Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 004/209] ARM: dts: omap5: enable OTG role for DWC3 controller Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 008/209] ARM: dts: sun8i: h3-h5: ir register size should be the whole memory block Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 009/209] ARM: dts: sun8i: h3: bpi-m2-plus: Fix address for external RGMII Ethernet PHY Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 058/209] ARM: dts: at91: sama5d4_xplained: fix addressable nand flash size Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 059/209] ARM: dts: at91: at91sam9x5cm: " Sasha Levin
2019-11-13  1:47 ` [PATCH AUTOSEL 4.19 060/209] ARM: dts: at91: sama5d2_ptc_ek: fix bootloader env offsets Sasha Levin
2019-11-13  1:48 ` [PATCH AUTOSEL 4.19 087/209] ARM: dts: da850-lego-ev3: slow down A/DC as much as possible Sasha Levin
2019-11-13 16:10   ` David Lechner
2019-11-22  3:24     ` Sasha Levin [this message]
2019-11-13  1:50 ` [PATCH AUTOSEL 4.19 202/209] ARM: dts: omap5: Fix dual-role mode on Super-Speed port Sasha Levin

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=20191122032422.GK16867@sasha-vm \
    --to=sashal@kernel.org \
    --cc=david@lechnology.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=stable@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