linux-kernel - Re: [PATCH] spi: img-spfi: same edge bit set to double spfi speeds

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:	Tue, 3 Feb 2015 22:10:15 -0800
From:	Andrew Bresticker <abrestic@...omium.org>
To:	Sifan Naeem <sifan.naeem@...tec.com>
Cc:	"broonie@...nel.org" <broonie@...nel.org>,
	linux-spi@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] spi: img-spfi: same edge bit set to double spfi speeds

Hi Sifan,

On Tue, Feb 3, 2015 at 9:46 AM, Sifan Naeem <sifan.naeem@...tec.com> wrote:
> Setting the same edge bit is required for operating at full bitrate
> programmed into the SPFI control register. Without this bit set the
> max operating bitrate supported would be half the maximum bitrate
> supported by the img-spfi block.
> It's safe to set this bit for all transactions.
>
> Signed-off-by: Sifan Naeem <sifan.naeem@...tec.com>

> @@ -435,6 +436,9 @@ static void img_spfi_config(struct spi_master *master, struct spi_device *spi,
>                 val |= SPFI_CONTROL_CONTINUE;
>         spfi_writel(spfi, val, SPFI_CONTROL);
>
> +       /* Double the transfer speed by setting Same Edge. */

I'm not sure a comment here is totally necessary, but if you do want
one, I don't think "Double the transfer speed" is the best way to put
this.  Something explaining what the SE bit does and that failing to
set it results in us operating at half the specified bitrate would be
more useful.
--
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/