From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [RFC] Device Tree Overlays Proposal (Was Re: capebus moving omap_devices to mach-omap2) Date: Tue, 06 Nov 2012 15:17:58 -0700 Message-ID: <50998C96.9090601@wwwdotorg.org> References: <02FF5400-9F97-4B8A-AEF0-267B01C8099F@antoniou-consulting.com> <20121106183531.GH6801@atomide.com> <56051C08-3ECF-4C0A-9B88-64B4C1DDDF45@antoniou-consulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from avon.wwwdotorg.org ([70.85.31.133]:50265 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751270Ab2KFWSC (ORCPT ); Tue, 6 Nov 2012 17:18:02 -0500 In-Reply-To: <56051C08-3ECF-4C0A-9B88-64B4C1DDDF45@antoniou-consulting.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Pantelis Antoniou Cc: Russ Dill , Kevin Hilman , Matt Porter , Koen Kooi , linux-kernel , Felipe Balbi , Deepak Saxena , Scott Wood , linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org On 11/06/2012 12:41 PM, Pantelis Antoniou wrote: > Hi Russ, >=20 > On Nov 6, 2012, at 8:29 PM, Russ Dill wrote: >=20 >> On Tue, Nov 6, 2012 at 10:35 AM, Tony Lindgren wr= ote: >>> * Grant Likely [121106 03:16]: >>>> On Tue, Nov 6, 2012 at 10:30 AM, Pantelis Antoniou >>>> wrote: >>>>> >>>>> Another can of worms is the pinctrl nodes. >>>> >>>> Yes... new pinctrl data would need to trigger adding new data to >>>> pinctrl. I don't know if the pinctrl api supports that. >>> >>> The actual pins stay the same, just their configuration >>> changes. AFAIK all that is already supported using the >>> pinctrl framework. >>> >>> For example, considering hotplugging capes on the beaglebone: =2E.. >> That assumes that for a particular external bus, certain pins aren't >> already shared with functions already on the board, for instance if = an >> I=B2C bus brought out to the external bus already has a chip connect= ed >> to it. >=20 > This is our case on the bone. We don't enable the peripheral until > a cape that references it is enabled. >=20 > I don't think that very big changes are going to be needed TBH. =2E.. > Ideally if we could do this in the cape definition: >=20 > cape_pinmux { > parent =3D <&am3358_pinmux>; I think the cape overlay would simply add nodes to the existing pin controller node, so I'd presume you would replace the two lines immediately above with: am3358_pinmux: pinmux { >=20 > bone_dvi_cape_led_pins: pinmux_bone_dvi_cape_led_pins= { > pinctrl-single,pins =3D < > 0x48 0x07 /* gpmc_a2.gpio1_18, = OUTPUT | MODE7 */ > 0x4c 0x07 /* gpmc_a3.gpio1_19, = OUTPUT | MODE7 */ > >; > }; >=20 > pinctrl-0 =3D <&bone_geiger_cape_pins>; -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html