From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762075AbcINRFv (ORCPT ); Wed, 14 Sep 2016 13:05:51 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:59126 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761877AbcINRFr (ORCPT ); Wed, 14 Sep 2016 13:05:47 -0400 Date: Wed, 14 Sep 2016 18:05:35 +0100 From: Mark Brown To: Martin Kaiser Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <20160914170535.GE27974@sirena.org.uk> References: <20160901203840.GA7972@reykholt.kaiser.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/3yNEOqWowh/8j+e" Content-Disposition: inline In-Reply-To: <20160901203840.GA7972@reykholt.kaiser.cx> X-Cookie: Even bytes get lonely for a little bit. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 1/2] spi: imx: set spi_bus_clk for mx1, mx31 and mx35 X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --/3yNEOqWowh/8j+e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 01, 2016 at 10:38:40PM +0200, Martin Kaiser wrote: > Modify spi_imx_clkdiv_2() to return the resulting bus clock frequency > when the selected clock divider is applied. Set spi_imx->spi_bus_clk to > this frequency. >=20 > If spi_bus_clk is unset, spi_imx_calculate_timeout() causes a > division by 0. >=20 > [ 90.356106] Division by zero in kernel. > [ 90.362631] CPU: 0 PID: 130 Comm: spidev_test Not tainted 4.8.0-rc3-ne= xt-20160825+ #105 > [ 90.372461] Hardware name: Freescale i.MX25 (Device Tree Support) > [ 90.378708] Backtrace: Please think hard before including backtraces in upstream reports, they are large and contain almost no useful information relative to their size so often obscure the relevant content in your message. If part of the backtrace is usefully illustrative then it's usually better to pull out the relevant sections. --/3yNEOqWowh/8j+e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX2YNeAAoJECTWi3JdVIfQ3g0H/1z8V0ZoiJMcAeg65q0WOFGT Dnt36YbeBp5fHd27+nlUC2NouO0OAbFnPWk/iNAqoKIfNP50aM8DzDhrlJrAXLHk Qg1qojJJFtxut7NExyMzI/V+N7ocMQ58E3csCloQj8Hw2yF5ylClM8+3TG975vXi jolnwlx1B2dhhOaGfgWnZlWnZTX/GdEfk89xntHK6MRtidWTG26JuoP8aAyeGpvd SFt76JfS9lGo8NZR9Rfhfpv1lNedyNdJ20m6saGQB732EZ5G0hAwY27ATGXPKc5I zlxsERXFPe3do3H652Ii2UQiyJdqTcCGNaUbDKEL57G+u7XvM2g9vhYznkWLkGQ= =weeX -----END PGP SIGNATURE----- --/3yNEOqWowh/8j+e--