linux-kernel - Re: [PATCH V4 0/4] ARM: tegra: Enable SLINK controller driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 1 Nov 2012 09:15:58 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	"linux@....linux.org.uk" <linux@....linux.org.uk>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V4 0/4] ARM: tegra: Enable SLINK controller driver

On Thursday 01 November 2012 12:46 AM, Stephen Warren wrote:
> On 10/31/2012 11:31 AM, Laxman Dewangan wrote:
>> On Wednesday 31 October 2012 09:59 PM, Stephen Warren wrote:
>>> On 10/31/2012 03:02 AM, Laxman Dewangan wrote:
>>>> This series modify the dts file to add the slink addresses,
>>>> make AUXDATA in board dt files, enable slink4 for tegra30-cardhu and
>>>> enable slink controller defconfig.
>>> I don't appear to have received patch 1/4 this time around. I'll assume
>>> it's identical to V3, since I don't think anything needed to change
>>> there...
>> Yes, it is identical to V3, no change on the 1/4.
> OK, I have applied the series now. Thanks.
>
> BTW, I noticed that the Cardu board files sets the SPI controller's max
> frequency to 25MHZ (which is consistent with the commit description) but
> the SPI flash node's frequency to 20MHz. Was that intended, or should I
> fix it up to be 25MHz?
If device provide the max frequency then the spi communciation will on 
this requested frequency.
If device does not provide the max spi frequency then it will 
communciate with the controller max frequency.

In this case we provide the 20MHz for device and 25MHz for controller. 
So spi communciation with this device will be always 20MHz.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/