From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Ungerer Subject: Re: [PATCH v2] spi: orion: support armada extended baud rates Date: Sun, 07 Sep 2014 22:18:52 +1000 Message-ID: <540C4D2C.3050703@uclinux.org> References: <1409835268-29555-1-git-send-email-gerg@uclinux.org> <5409057A.6090900@uclinux.org> <5409B68A.7010604@uclinux.org> <20140906120600.GA11500@arch.cereza> <20140906151654.49584b70@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Geert Uytterhoeven , linux-spi , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Jason Cooper , Gregory Clement , Andrew Lunn , Sebastian Hesselbarth To: Thomas Petazzoni , Ezequiel Garcia Return-path: In-Reply-To: <20140906151654.49584b70-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> Sender: linux-spi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Hi Thomas, On 06/09/14 23:16, Thomas Petazzoni wrote: > Hello, > > On Sat, 6 Sep 2014 09:06:00 -0300, Ezequiel Garcia wrote: > >> 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. > However, I believe a compatible string like "armada-370-spi" should be > used instead of "armada-spi". The normal rule is to use the oldest SoC > that introduced a certain feature as the compatible string. Ok, will make it that then. > Remember for example that Armada 1500 (Berlin) is a completely different > line of SoC, which cannot use this SPI driver. > > Thanks Greg for working on this! I noticed this as well recently when > doing an SPI development, but you were faster than me in proposing a > patch! > No problem :-) 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