From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Cc: John Williams <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Gpio reset handling
Date: Tue, 15 Sep 2009 20:32:49 +0200 [thread overview]
Message-ID: <4AAFDDD1.9070702@monstr.eu> (raw)
Hi All,
I would like to find out proper way how to handle xilinx reset gpio.
We are using gpio for soft reset.
I read led.txt in Documentation and currently are used/supported some triggers
but reset is not there.
Led gpio is clear because example is in kernel (xpedite5301.dts for example)
Here is description for mixed reset/heartbeat/led gpio
1. line - soft reset
2. line - phy reset for example or any different one
3. line - heartbeat
4. line - led
Not sure if is first line from 1 or 0 - but doesn't matter right now.
gpio_res: gpio@81400000 {
compatible = "xlnx,xps-gpio-1.00.a";
interrupt-parent = <&xps_intc_0>;
interrupts = < 7 2 >;
reg = < 0x81400000 0x10000 >;
...
xlnx,gpio-width = <0x8>;
...
} ;
gpio-leds {
compatible = "gpio-leds";
heartbeat {
label = "Heartbeat";
gpios = <&gpio_res 4 1>;
linux,default-trigger = "heartbeat";
}
green {
label = "Green"
gpios = <&gpio_res 5 1>;
}
}
Ok and here about description of reset port
I see two option to write new trigger
1. new reset trigger and add it to gpio-leds node - but this should be in gpio-leds node which make
no sense to me
reset {
label = "Heartbeat";
gpios = <&gpio_res 3 1>;
linux,default-trigger = "reset";
}
2. create own reset node
reset {
compatible = "gpio-reset";
reset0 {
label "Soft reset";
gpios = <&gpio_res 1 1>;
}
reset1 {
label "Phy reset";
gpios = <&gpio_res 2 1>;
}
}
For this node there should be better reset description not just label with different description.
I expect that it will be useful soft and hard reset and maybe you can find some others.
Thanks for you help,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next reply other threads:[~2009-09-15 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 18:32 Michal Simek [this message]
[not found] ` <4AAFDDD1.9070702-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2009-09-15 22:27 ` Gpio reset handling Grant Likely
[not found] ` <fa686aa40909151527r36334528ne1194523f141a8a2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-15 22:40 ` John Williams
[not found] ` <1d3f23370909151540p411f0bc0r1c81b68ceb2fb45e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-15 23:07 ` Grant Likely
[not found] ` <fa686aa40909151607u29d4025ay101e89d9eae5f30a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-17 6:46 ` Michal Simek
[not found] ` <4AB1DB2A.6050109-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2009-09-17 13:42 ` Grant Likely
[not found] ` <fa686aa40909170642j63ccef7bnf162cb88b9733023-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-17 13:46 ` Michal Simek
2009-09-16 11:07 ` Martin Donnelly
2009-09-16 0:24 ` David Gibson
[not found] ` <20090916002459.GA8891-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2009-09-17 6:46 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAFDDD1.9070702@monstr.eu \
--to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox