From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Mon, 25 Jul 2016 15:39:22 +0200 From: Thierry Reding To: Mirza Krak Cc: Jon Hunter , Stephen Warren , Alexandre Courbot , pdeschrijver@nvidia.com, Prashant Gaikwad , Michael Turquette , sboyd@codeaurora.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, Kumar Gala , linux@armlinux.org.uk Subject: Re: [RFC 3/6] dt/bindings: Add bindings for Tegra20/30 NOR bus driver Message-ID: <20160725133922.GK21170@ulmo.ba.sec> References: <1468935397-11926-1-git-send-email-mirza.krak@gmail.com> <1468935397-11926-4-git-send-email-mirza.krak@gmail.com> <434561ec-510e-a3bf-c7b6-c961db299bd6@nvidia.com> <20160725115923.GF21170@ulmo.ba.sec> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nzri8VXeXB/g5ayr" In-Reply-To: List-ID: --nzri8VXeXB/g5ayr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 25, 2016 at 03:30:34PM +0200, Mirza Krak wrote: > 2016-07-25 13:59 GMT+02:00 Thierry Reding : > > On Thu, Jul 21, 2016 at 10:56:44AM +0100, Jon Hunter wrote: > >> > > > >> > +Note that the NOR controller does not have any internal chip-select= address > >> > +decoding and if you want to access multiple devices external chip-s= elect > >> > +decoding must be provided. > >> > >> Although it is true, you do have the MIO address space and so you could > >> support two devices via the SNOR address space and MIO address space > >> (assuming that the MIO can be used for the 2nd device). > > > > Now I'm even more confused. If the GMI controller itself can't select a > > chip, what is the SNOR_SEL field in the SNOR_CONFIG_0 register for? Does > > that not select a specific chip? > > > >> Furthermore, if you do have external logic to support multiple devices > >> this would assume that the devices use the same timing and so are > >> probably the same type. It also assumes both can fit in the 256MB > >> address range. May be worth mentioning. > > > > Similarly if you switch between different devices, wouldn't you have to > > reprogram the timing registers if they are different? > > > > The way I remember this kind of interface to work (it's been a long time > > since I used one) is that in order to operate on a chip you need to > > acquire the bus first. Typically that would be an API exposed by the bus > > driver or some framework that the bus driver registers with. That API > > arbitrates between multiple devices on the bus and makes sure that the > > proper chip select is asserted and timing is programmed when you're > > granted access. A driver that has acquired the bus can then perform what > > operations they need and release the bus when done. > > > > SPI uses a mechanism like this, for example. > > > > Thierry >=20 > From my experience (maybe not as long as yours :)) but these kind of > things would be handled by the controller. At least with previous SOCs > that I have used, PXA270, PXA300 and i.MX SOCs. >=20 > That it has an address range per chip-select PIN and timing registers > per chip-select. And thus eliminating a need for a infrastructure or > framework. Okay, so the controllers have a translation table that needs to be programmed and which maps address ranges to chip-selects. That's a nifty feature, but I think it's also fairly specialized. In such a setup there doesn't need to be a concept of chip-selects in software because it's all transparently handled by the controller. Effectively the only time a chip-select is needed is during the initial programming of the controller when the translation table is set up. =46rom a software point of view the devices are then addressed by memory address alone, so they aren't on a "manually switched" bus using chip- selects. Thierry --nzri8VXeXB/g5ayr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJXlhaKAAoJEN0jrNd/PrOhoCIP/ioNAe4W4/LZZipU04ckvf7B HA4bbh8fWANkpFmwofLiE+3LkWoL9duMGORx0aHrLrKfa+L+q2ZHaY/Wjld5oNtP O59xUdSOaAMZILq63/QxIpeo/hC7O0J7gvavzovOYlN54slYUVYmmK/xMwcRzdAA WE5dx2jbonKYfSdRjJrUiHnBMlFNWKKYQF8NhaX5skNtI8JwTZEclP9U99tpogCi FcWQTBYP2XxiWJM03xDllZGDDltjkOJM0rSf5KBQN3DTNkWuAp4UIyVxzBHNW0K4 dAGHf3eUvj+XTwO0BhladBzpcOD+j/mKn+GNoj6xwLModxf0nZO5oR1NkIZl5/wb Zc5sP03lQMeWOvGcezMm5Qcx/GKuCsWxkc6lqTZFjksVeNMz731g+fdILGmBM14L tpQJ2ig17V/uzxCUAQ5ENqYKb1JjooSOtbWZPionactKrtXL4XdRZUKOiOvkGaad JVodVYnClyaV1Tt7Pqdl8/3IzffV1rb1oA+Ac+2tEtzU/tBgDan85jK1VqH1sHkB 46CWoGBZtjNEkYIQx+xunEbY/6usKYHOeWQ+gO7IRR4RYRhir5jKMJKnCcm0geGP QFTcV9QLGXTnRRqxM+QwOaL4TIotF7Yy9vPWGpcEHAPpaGksvb8qoLOhPQd2dq8k uZ8QCO2ViBkLK/zMVogA =KGlk -----END PGP SIGNATURE----- --nzri8VXeXB/g5ayr--