devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>
To: Ezequiel Garcia
	<ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Geert Uytterhoeven
	<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
	linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
	Thomas Petazzoni
	<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	Gregory Clement
	<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
	Sebastian Hesselbarth
	<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2] spi: orion: support armada extended baud rates
Date: Sun, 07 Sep 2014 22:14:16 +1000	[thread overview]
Message-ID: <540C4C18.5030903@uclinux.org> (raw)
In-Reply-To: <20140906120600.GA11500-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>

Hi Ezequiel,

On 06/09/14 22:06, Ezequiel Garcia wrote:
> Hi Greg,
>
> (Ccing mvebu guys, full discussion here: http://www.spinics.net/lists/devicetree/msg47806.html)
>
> On 05 Sep 11:11 PM, Greg Ungerer wrote:
>> On 05/09/14 17:36, Geert Uytterhoeven wrote:
>>> No, the other way around (from most-specific to least-specific):
>>>
>>>      compatible = "marvell,armada-spi", "marvell,orion-spi"
>>>
>>> So the Armada version is used if available, and the Orion version
>>> is used as a fallback.
> Since you are doing another spin, please split this in two patches.
> The driver and devicetree binding documentation should be in one patch,
> and the devicetree .dtsi change in another patch.
>
> By following Geert's request about the compatible, you make sure both
> patches can be merged through different maintainers, and that an old devicetree
> blob can be used safely.

Sure, yes, I would prefer that too. I didn't do it for this because 
checkpatch
complained for the spi-orion.c change in its own:

WARNING: DT compatible string "marvell,armada-spi" appears un-documented 
-- check ./Documentation/devicetree/bindings/
#170: FILE: drivers/spi/spi-orion.c:412:
+    { .compatible = "marvell,armada-spi", .data = &armada_spi_dev_data, },

But I am happy to ignore that :-)


>>>   Also what about armada370-xp, armada375, armada380
>>> and any other variants out there?
>> I don't know. I don't have access to functional specs for anything
>> other than the 370. I expect they are probably the same though.
>> (Can anyone confirm?)
>>
> Confirmed. Judging from the specs, seems the same SPI IP is on all the
> Armada SoCs; you can do the 'armada-spi' compatible addition on 375 and 38x.
>
> Did a few tests on the AXP-GP board (which has an SPI flash) using
> 'orion-spi' and 'armada-spi' compatibles.
>
> Tested-by: Ezequiel Garcia <ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
> Reviewed-by: Ezequiel Garcia <ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>

Thanks, appreciate that.


> I haven't been able to spot any speed difference, though (perhaps my
> test is too limited?), so I wonder if there's any improvement with this
> patch?

Try setting a speed like 2MHz for an SPI device. It will fail because that
is below the minimum divisor it can calculate with the old orion style
behavior. I have an armada 370 based board with an ethernet switch
that is controlled by SPI. Its typical SPI bus speed is 2MHz, that is how I
came up against this.

Regards
Greg

--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-09-07 12:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 12:54 [PATCH v2] spi: orion: support armada extended baud rates gerg-JBU5SbJe1FlAfugRpC6u6w
     [not found] ` <1409835268-29555-1-git-send-email-gerg-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>
2014-09-04 13:17   ` Geert Uytterhoeven
     [not found]     ` <CAMuHMdWDOaPnmCzThqCo2848eDj6jmi-eaXM1YAXQLi41da34A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-05  0:36       ` Greg Ungerer
     [not found]         ` <5409057A.6090900-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>
2014-09-05  7:36           ` Geert Uytterhoeven
     [not found]             ` <CAMuHMdWf6_yBhpNgK=wJcQqzLNJvTnC95SrqrcZyRH+jGL93vA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-05 13:11               ` Greg Ungerer
     [not found]                 ` <5409B68A.7010604-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>
2014-09-06 12:06                   ` Ezequiel Garcia
     [not found]                     ` <20140906120600.GA11500-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-09-06 13:16                       ` Thomas Petazzoni
     [not found]                         ` <20140906151654.49584b70-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-09-07 12:18                           ` Greg Ungerer
2014-09-07 12:14                       ` Greg Ungerer [this message]
     [not found]                         ` <540C4C18.5030903-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>
2014-09-07 15:12                           ` Ezequiel Garcia
     [not found]                             ` <20140907151250.GA692-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-09-08  1:52                               ` Greg Ungerer

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=540C4C18.5030903@uclinux.org \
    --to=gerg-jbu5sbje1flafugrpc6u6w@public.gmane.org \
    --cc=andrew-g2DYL2Zd6BY@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
    --cc=gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@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).