From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sat, 12 Oct 2019 16:21:36 -0400 Subject: [U-Boot] [PATCH V3 04/10] spi: bcm63xx_hsspi: Continue init when using no reset and fixed-clock. In-Reply-To: <1565788721-21866-4-git-send-email-philippe.reynes@softathome.com> References: <1565788721-21866-1-git-send-email-philippe.reynes@softathome.com> <1565788721-21866-4-git-send-email-philippe.reynes@softathome.com> Message-ID: <20191012202136.GI16029@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Aug 14, 2019 at 03:18:35PM +0200, Philippe Reynes wrote: > From: Kursad Oney > > The Broadcom ARM implementations do not yet have a clock framework so > one can use a fixed clock as the root clock of the hsspi block. The > fixed clock does not have an "enable" routine, since it's always > enabled. So when we hit this issue, getting an ENOSYS return, do not > bail but continue initialization. > > Similarly the block might already have been out of reset, say, when > we are booting from a SPI device. So if the reset signal is not configured > in the device tree, do not bail out and instead skip deasserting the reset. > > Signed-off-by: Kursad Oney > Reviewed-by: Philippe Reynes Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: