From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753110AbbHTVYu (ORCPT ); Thu, 20 Aug 2015 17:24:50 -0400 Received: from down.free-electrons.com ([37.187.137.238]:47796 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751849AbbHTVYs (ORCPT ); Thu, 20 Aug 2015 17:24:48 -0400 Date: Thu, 20 Aug 2015 23:24:46 +0200 From: Maxime Ripard To: Chen-Yu Tsai Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Greg Kroah-Hartman , Mark Brown , devicetree , linux-arm-kernel , linux-kernel , linux-sunxi , Hans de Goede , Meng Zhang , Shuge , Meng Zhang Subject: Re: [PATCH v3 1/8] rsb: Add generic Reduced Serial Bus (RSB) controller binding documentation Message-ID: <20150820212446.GK30520@lukather> References: <1439958009-14056-1-git-send-email-wens@csie.org> <1439958009-14056-2-git-send-email-wens@csie.org> <20150820150845.GB30520@lukather> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zQZ31nKYDGgulmZX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --zQZ31nKYDGgulmZX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 20, 2015 at 11:58:39PM +0800, Chen-Yu Tsai wrote: > >> +Child nodes: > >> + > >> +An RSB controller node can contain zero or more child nodes represent= ing > >> +slave devices on the bus. Child 'reg' properties are specified as a > >> +runtime address, hardware address pair. The hardware address is hardw= ired > >> +in the device, which can normally be found in the datasheet. The runt= ime > >> +address is set by software. No 2 devices on the same bus shall have t= he > >> +same runtime address. > >> + > >> +Valid runtime addresses - There are only 15 valid runtime addresses: > >> + > >> + 0x17, 0x2d, 0x3a, 0x4e, 0x59, 0x63, 0x74, 0x8b, > >> + 0x9c, 0xa6, 0xb1, 0xc5, 0xd2, 0xe8, 0xff > >> + > >> +It is highly recommended that one choose the same runtime addresses as > >> +vendor BSPs use so that a) the addresses remain the same across diffe= rent > >> +software systems, and b) addresses of supported and listed slave devi= ces > >> +don't conflict with unsupported or not yet listed devices. > > > > I'd expect to have the hardware address first, but maybe it's just me > > :) >=20 > I don't know. It's only used at init time. >=20 > And in my latest experience, once the runtime address is set by the > bootloader, it can't be changed. My earlier experience was the opposite, > though I haven't figured out why. Note that I'm only talking about the order of runtime and hardware addresses in the reg property, having both is fine. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --zQZ31nKYDGgulmZX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJV1kWeAAoJEBx+YmzsjxAgAjsP/183qK9dPBZsDO9W+cgvznN/ xOUo/mtNvMvC1RcD31Fj53AgMRl34iiLLsgVpGFR5gOhJQj4GaeFXd5sVhJiOrOL 4g1l6mCGnmzZQG92zxPGspCrXt6qdwW2qgIByjpM6wvyoJVlGPeopqsDRyVlJ7FW TyfNl91tmxWvIKWRifPG+kqPclHrZVYMDl+Bgx61ErScbOBY0wwnfSahJpyvnjXp sgZglLz4XZGTCJkKAxs5NWi7za26XUsgcF0+5qeifp+x1uffzEOPbwKzvW1gNniS fLG0Jcsk44XINbZWoOrsM8klNxlPjhnCd/4UvZ0+eRsCtCK1aocdTAIgbB/L+GZ0 6/YDbwIyCjufySbVA8K01/0ENhSHm9S4pHB8bEFSUxqaYUj7k+BmUJ7/TM8cJmRw KxwNQXMkkDP7+ablFwVFYtGoGcnR6hXwOQrU75DkscRpkRmHZXc8C5Ubc6/w6gs6 YIJnx7J4EI+B71Lwt+9lbqQ1ysbGN1sGOh4XRtKPdUA6nQT5A60JYx7bbTIv8JuK kInCdvo16TBI8lP7VuNyUBQNdm/DtLXahX6F963zry1udhQORJjAXw2yXUrw+EdY 0aq1u85e1Xmy0Bm1m9YktQgFDPaIFOGY4v9C/0NyiRc7Y+UDhrl5Iou6lHtweeqP hEwpbqd5Wy/bT/iNiEsB =n/IK -----END PGP SIGNATURE----- --zQZ31nKYDGgulmZX--