From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Neuendorffer Subject: RE: Device tree BSP Date: Sat, 4 Jul 2009 11:15:10 -0700 Message-ID: <20090704181837.4DC219B0051@mail75-va3.bigfish.com> References: <4A49F472.3030902@petalogix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1634850226==" Return-path: Content-Class: urn:content-classes:message 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: michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org, John Williams , John Linn , David DeBonis , devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org List-Id: devicetree@vger.kernel.org --===============1634850226== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9FCD3.D86AFE8F" ------_=_NextPart_001_01C9FCD3.D86AFE8F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm not exactly sure what you're trying to do here, but it doesn't look rig= ht to me. In particular, why would I have to have a separate core for these functions= ? Furthermore, I'm sure there must be some generic mechanisms that can/should= be used for these kind of things. In general, we shouldn't reinvent the wheel here.. CC'ing devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org, which is really the best place to ask= such questions. Steve -----Original Message----- From: Michal Simek [mailto:michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org] Sent: Tue 6/30/2009 4:18 AM To: John Williams; John Linn; David DeBonis; Stephen Neuendorffer Subject: Device tree BSP = Hi all, I need to talk to you about names for at least one new compatible property name. It is for heartbeat led gpio and (not important now) reset gpio. Currently linux kernel takes first gpio for heartbeat led which needn't be led gpio that's why we need to specify which gpio node is for it. I think we can't used it aliases because in case you enable gpio linux driver heartbeat go away because that node had gpio compatible property. Our proposed compatible names are xlnx,heartbeat-gpio-1.00.a and xlnx,reset-gpio-1.00.a which replaced all gpio compatible properties. Below are two parts of fragments. LEDs_8Bit: gpio@42000000 { compatible =3D "xlnx,heartbeat-gpio-1.00.a"; reg =3D < 0x42000000 0x10000 >; xlnx,all-inputs =3D <0x0>; Push_Buttons: gpio@42600000 { compatible =3D "xlnx,reset-gpio-1.00.a"; interrupt-parent =3D <&xps_intc_0>; interrupts =3D < 4 2 >; If you agree with heartbeat name, I will change it in linux kernel code. Thanks, Michal -- = Michal Simek, Ing. (M.Eng) PetaLogix - Linux Solutions for a Reconfigurable World w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663 This email and any attachments are intended for the sole use of the named r= ecipient(s) and contain(s) confidential information that may be proprietary= , privileged or copyrighted under applicable law. If you are not the intend= ed recipient, do not read, copy, or forward this email message or any attac= hments. Delete this email message and any attachments immediately. ------_=_NextPart_001_01C9FCD3.D86AFE8F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Device tree BSP

I'm not exactly sure what you're trying to do here, but i= t doesn't look right to me.
In particular, why would I have to have a separate core for these functions= ?
Furthermore, I'm sure there must be some generic mechanisms that can/should= be used for these kind of things.
In general, we shouldn't reinvent the wheel here..

CC'ing devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org, which is really the best place to ask= such questions.

Steve

-----Original Message-----
From: Michal Simek [mailto:mi= chal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org]
Sent: Tue 6/30/2009 4:18 AM
To: John Williams; John Linn; David DeBonis; Stephen Neuendorffer
Subject: Device tree BSP

Hi all,

I need to talk to you about names for at least one new compatible
property name.
It is for heartbeat led gpio and (not important now) reset gpio.
Currently linux kernel takes
first gpio for heartbeat led which needn't be led gpio that's why we
need to specify which gpio
node is for it. I think we can't used it aliases because in case you
enable gpio linux driver
heartbeat go away because that node had gpio compatible property.

Our proposed compatible names are xlnx,heartbeat-gpio-1.00.a and
xlnx,reset-gpio-1.00.a
which replaced all gpio compatible properties. Below are two parts of
fragments.

LEDs_8Bit: gpio@42000000 {
    compatible =3D "xlnx,heartbeat-gpio-1.00.a";     reg =3D < 0x42000000 0x10000 >;
    xlnx,all-inputs =3D <0x0>;

Push_Buttons: gpio@42600000 {
    compatible =3D "xlnx,reset-gpio-1.00.a";
    interrupt-parent =3D <&xps_intc_0>;
    interrupts =3D < 4 2 >;

If you agree with heartbeat name, I will change it in linux kernel code.
Thanks,
Michal

--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663



This email and any attachments are intended for the sole u= se of the named recipient(s) and contain(s) confidential information that m= ay be proprietary, privileged or copyrighted under applicable law. If you a= re not the intended recipient, do not read, copy, or forward this email mes= sage or any attachments. Delete this email message and any attachments imme= diately. ------_=_NextPart_001_01C9FCD3.D86AFE8F-- --===============1634850226== 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 --===============1634850226==--