From: Stefan Agner <stefan@agner.ch>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: thierry.reding@gmail.com, linux@arm.linux.org.uk,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
marcel@ziswiler.com
Subject: Re: [PATCH 2/2] ARM: tegra: initial add of Colibri T30
Date: Wed, 14 May 2014 18:16:16 +0200 [thread overview]
Message-ID: <107aeb48982529858267cb85c792b35e@agner.ch> (raw)
Am 2014-05-13 21:49, schrieb Stephen Warren:
> On 05/13/2014 11:27 AM, stefan@agner.ch wrote:
>> + /* SPI1: Colibri SSP */
>> + spi@7000d400 {
>> + status = "okay";
>> + spi-max-frequency = <25000000>;
>> + can0: can@0 {
>> + compatible = "microchip,mcp2515";
>> + reg = <0>;
>> + clocks = <&clk16m>;
>> + interrupt-parent = <&gpio>;
>> + interrupts = <TEGRA_GPIO(S, 0) GPIO_ACTIVE_LOW>;
>> + spi-max-frequency = <10000000>;
>
> So this chip doesn't get confused by a faster clock frequency when its
> chip-select line isn't asserted? I would have expected spi-max-frequency
> for the bus to be the minimum value that any device on the bus would
> tolerate.
And from the other mail:
> I'm not convinced about this. The clock signal still reaches all the
> chips, and hence still reaches some logic inside those chips. If the
> setup/hold timings aren't met (for internal parts of the chip's SPI
> state machine), then presumably all bets are off re: performance of the
> chip, irrespective of whether the CS line happens to gate how much of
> the chip actually does anything.
SPI is by default not a multi-master Bus, hence the slaves only have to
listen when the CS is asserted. I talked with our hardware expert, and
he told me that he would expect that the whole input stage (input
driver) is in reset/off logic when the CS line is not asserted. IMHO,
this makes sense, this would also save power. At least he would expect
that the communication state machine is resetted on CS assertion, so
that it doesn't matter what happend before.
Wikipedia also states something similar.
But, since SPI is no real standard, devices which work differently and
claim to communicate through SPI could exist :-)
I have had not seen issues with this device when using faster clocks for
other devices on the same bus.
>> + panel: panel {
>> + compatible = "edt,et057090dhu", "simple-panel";
>
> The panel-simple driver doesn't seem to know about that EDT panel. How
> will it work out the display timings?
I will send a patch adding our two default panels.
Will send a second revision soon.
next reply other threads:[~2014-05-14 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 16:16 Stefan Agner [this message]
[not found] ` <107aeb48982529858267cb85c792b35e-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 18:13 ` [PATCH 2/2] ARM: tegra: initial add of Colibri T30 Stephen Warren
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 17:27 [PATCH 0/2] ARM: tegra: initial support for " stefan
2014-05-13 17:27 ` [PATCH 2/2] ARM: tegra: initial add of " stefan
[not found] ` <d45ec5351ce8ef03256061bdc4b0ba673bd40c66.1400001937.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-13 19:49 ` Stephen Warren
[not found] ` <53727738.4080901-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-14 7:22 ` Marcel Ziswiler
2014-05-14 14:32 ` Thierry Reding
2014-05-14 15:38 ` Stephen Warren
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=107aeb48982529858267cb85c792b35e@agner.ch \
--to=stefan@agner.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marcel@ziswiler.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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