linux-kernel - Re: [RESEND PATCH 2/2] bus: ocp2scp: SYNC2 value should be changed to 0x6

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]

Message-ID: <20150326175035.GC10805@atomide.com>
Date:	Thu, 26 Mar 2015 10:50:35 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Kishon Vijay Abraham I <kishon@...com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
	linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
	devicetree@...r.kernel.org, linux-omap@...r.kernel.org,
	nsekhar@...com, nm@...com, praneeth@...com,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [RESEND PATCH 2/2] bus: ocp2scp: SYNC2 value should be changed
 to 0x6

* Kishon Vijay Abraham I <kishon@...com> [150317 04:25]:
> As per the TRMs of AM572x, OMAP4430, OMAP4460, OMAP543x, the value of
> SYNC2 must be set to 0x6 in order to ensure correct operation.
> 
> So modified the SYNC2 value of OCP2SCP TIMING register to 0x6 in all the
> platforms that use OCP2SCP driver except AM437x. Also introduced a new
> compatible property since we don't want to modify the OCP2SCP TIMING
> register for AM437x.

OK thanks I'll apply both into omap-for-v4.1/fixes-not-urgent as
it seems we've gotten away with it for quite a few years now, and
I don't see any specific description of what these fix.

If that's not the case, please let me know.

Regards,

Tony
--
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/