From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp4.netcologne.de ([194.8.194.137]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1MGcJY-0007Xw-Go for linux-mtd@lists.infradead.org; Tue, 16 Jun 2009 17:19:23 +0000 Date: Tue, 16 Jun 2009 19:19:06 +0200 From: Albrecht =?iso-8859-1?b?RHJl3w==?= Subject: Re: [PATCH V2 2/2] mtd/maps/mtd-ram: add an of-platform driver To: Grant Likely In-Reply-To: (from grant.likely@secretlab.ca on Tue Jun 16 14:53:17 2009) Message-Id: <1245172753.3400.0@antares> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; protocol="application/pgp-signature"; boundary="=-3vEv1y6AYteInxT4S5bC" Cc: devicetree-discuss@ozlabs.org, Wolfram Sang , linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, Ben Dooks , David Woodhouse List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --=-3vEv1y6AYteInxT4S5bC Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 16.06.09 14:53 schrieb(en) Grant Likely: > I'm not happy about the use case though. It probably shouldn't =20 > appear in this binding, or if it does it should be tagged as an =20 > optional property. I agree with you that the naming is really misleading - other devices =20 which are not mtd's may suffer from the same problem of the lpb (in my =20 case, I have an extra memory-mapped Ethernet chip which I didn't try to =20 access yet...). As it is actually a chip select property, what about defining an =20 optional property like "cs-width =3D (8|16|32)" which defaults to 8 and =20 may be added to each 5200 lpb child? > It is only in the 5200 localplus case that bank-width is needed to =20 > figure out how to apply the workaround. Just out of curiosity: what about the "localbus" of other Freescale =20 chips (82xx? 83xx? Maybe others?)? Thanks, Albrecht. --=-3vEv1y6AYteInxT4S5bC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQBKN9QRn/9unNAn/9ERAgcZAKCDBRHS+2sgGwIwB2vjxbbyuycbjwCfQBnb 016afTZRn4vmVMeRgCX/P/Y= =RUF4 -----END PGP SIGNATURE----- --=-3vEv1y6AYteInxT4S5bC-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id B0105B7136 for ; Wed, 17 Jun 2009 03:19:18 +1000 (EST) Date: Tue, 16 Jun 2009 19:19:06 +0200 From: Albrecht =?iso-8859-1?b?RHJl3w==?= Subject: Re: [PATCH V2 2/2] mtd/maps/mtd-ram: add an of-platform driver To: Grant Likely In-Reply-To: (from grant.likely@secretlab.ca on Tue Jun 16 14:53:17 2009) Message-Id: <1245172753.3400.0@antares> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; protocol="application/pgp-signature"; boundary="=-3vEv1y6AYteInxT4S5bC" Cc: devicetree-discuss@ozlabs.org, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, Ben Dooks , David Woodhouse List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --=-3vEv1y6AYteInxT4S5bC Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 16.06.09 14:53 schrieb(en) Grant Likely: > I'm not happy about the use case though. It probably shouldn't =20 > appear in this binding, or if it does it should be tagged as an =20 > optional property. I agree with you that the naming is really misleading - other devices =20 which are not mtd's may suffer from the same problem of the lpb (in my =20 case, I have an extra memory-mapped Ethernet chip which I didn't try to =20 access yet...). As it is actually a chip select property, what about defining an =20 optional property like "cs-width =3D (8|16|32)" which defaults to 8 and =20 may be added to each 5200 lpb child? > It is only in the 5200 localplus case that bank-width is needed to =20 > figure out how to apply the workaround. Just out of curiosity: what about the "localbus" of other Freescale =20 chips (82xx? 83xx? Maybe others?)? Thanks, Albrecht. --=-3vEv1y6AYteInxT4S5bC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQBKN9QRn/9unNAn/9ERAgcZAKCDBRHS+2sgGwIwB2vjxbbyuycbjwCfQBnb 016afTZRn4vmVMeRgCX/P/Y= =RUF4 -----END PGP SIGNATURE----- --=-3vEv1y6AYteInxT4S5bC-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albrecht =?iso-8859-1?b?RHJl3w==?= Subject: Re: [PATCH V2 2/2] mtd/maps/mtd-ram: add an of-platform driver Date: Tue, 16 Jun 2009 19:19:06 +0200 Message-ID: <1245172753.3400.0@antares> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0649232822==" Return-path: In-Reply-To: (from grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org on Tue Jun 16 14:53:17 2009) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: Grant Likely Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org, linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org, linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Ben Dooks , David Woodhouse List-Id: devicetree@vger.kernel.org --===============0649232822== Content-Type: multipart/signed; micalg=PGP-SHA1; protocol="application/pgp-signature"; boundary="=-3vEv1y6AYteInxT4S5bC" --=-3vEv1y6AYteInxT4S5bC Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 16.06.09 14:53 schrieb(en) Grant Likely: > I'm not happy about the use case though. It probably shouldn't =20 > appear in this binding, or if it does it should be tagged as an =20 > optional property. I agree with you that the naming is really misleading - other devices =20 which are not mtd's may suffer from the same problem of the lpb (in my =20 case, I have an extra memory-mapped Ethernet chip which I didn't try to =20 access yet...). As it is actually a chip select property, what about defining an =20 optional property like "cs-width =3D (8|16|32)" which defaults to 8 and =20 may be added to each 5200 lpb child? > It is only in the 5200 localplus case that bank-width is needed to =20 > figure out how to apply the workaround. Just out of curiosity: what about the "localbus" of other Freescale =20 chips (82xx? 83xx? Maybe others?)? Thanks, Albrecht. --=-3vEv1y6AYteInxT4S5bC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQBKN9QRn/9unNAn/9ERAgcZAKCDBRHS+2sgGwIwB2vjxbbyuycbjwCfQBnb 016afTZRn4vmVMeRgCX/P/Y= =RUF4 -----END PGP SIGNATURE----- --=-3vEv1y6AYteInxT4S5bC-- --===============0649232822== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ devicetree-discuss mailing list devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org https://ozlabs.org/mailman/listinfo/devicetree-discuss --===============0649232822==--