Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751845Ab1DVGHh (ORCPT ); Fri, 22 Apr 2011 02:07:37 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:59457 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751572Ab1DVGHf (ORCPT ); Fri, 22 Apr 2011 02:07:35 -0400 Date: Fri, 22 Apr 2011 08:07:28 +0200 From: Wolfram Sang To: John Williams Cc: Michal Simek , devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca, linux-kernel@vger.kernel.org, hjk@hansjkoch.de, arnd@arndb.de Subject: Re: [PATCH v3] uio/pdrv_genirq: Add OF support Message-ID: <20110422060728.GC24653@pengutronix.de> References: <1303116654-5042-1-git-send-email-monstr@monstr.eu> <20110418160658.GD23814@pengutronix.de> <20110421120855.GC2135@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0lnxQi9hkpPO77W3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 2001:6f8:1178:2:215:17ff:fe12:23b0 X-SA-Exim-Mail-From: wsa@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1791 Lines: 55 --0lnxQi9hkpPO77W3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > The difference between what you are doing for these multifunction > devices, versus the generic-uio approach, is surely only a matter of > degree rather than fundamentals? I don't think so. If you write "uio-generic", then you explicitly specify uio which is linux specific and not hardware related. There is no uio-hardware :) If you write "fsl,mpc5200b-psc-uart" then you describe that in your hardware the psc is used as an UART (and not SPI) and every OS can make its assumpti= on about it. So, you could have "company, super-fpga64-uart" which would bind to the corresponding UART driver. And "company, super-fpga64-encryptor" would be handled in Linux by the uio-driver if you setup this way, for example. If y= ou later have a seperate driver for it, then it will match against this compatible-entry instead of uio. No change of the devicetree, the hardware = did not change. Regards, Wolfram --=20 Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ | --0lnxQi9hkpPO77W3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk2xGyAACgkQD27XaX1/VRsuKwCaA4fXlV4YyAvZoeN8BIXEd3Ig WuMAoMUiW72a5vfVvaq5LSfKI8abs8Vv =+a14 -----END PGP SIGNATURE----- --0lnxQi9hkpPO77W3-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/