Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document power up ability of pin 5 #413

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

matthijskooijman
Copy link

No description provided.

@matthijskooijman
Copy link
Author

For full disclosure, I added a link to the documentation to my own blog, since I think this is the most comprehensive discussion of this wakup ability that I'm aware of. If there's better references, feel free to update the link.

@Gadgetoid
Copy link
Collaborator

Thank you- I'd say an external documentation link should be a primary source- ie: the elinux wiki or Raspberry Pi's own documentation- however neither seem to mention this in more than passing (which you mention).

In this case it might be better to make contributions to the elinux wiki (https://elinux.org/Special:RequestAccount) or Raspberry Pi documentation itself (https://github.com/raspberrypi/documentation).

@seamusdemora
Copy link

@Gadgetoid :

Thank you- I'd say an external documentation link should be a primary source- ie: the elinux wiki or Raspberry Pi's own documentation- however neither seem to mention this in more than passing (which you mention).

In this case it might be better to make contributions to the elinux wiki (https://elinux.org/Special:RequestAccount) or Raspberry Pi documentation itself (https://github.com/raspberrypi/documentation).

I see your point, but circumstances suggest that may result in quite a long wait:

The elinux wiki page seems out-of-date with only 2 revisions in the past 6 years, and no new material since Model A+, B+ and B2. Even the Raspberry Pi Hub page is years out-of-date. Is this considered to be a "reliable source"?

Wrt The Foundation's documentation: Oddly, the only concrete documentation I can find is in their /boot/overlays/README file under the overlay called gpio-shutdown. If that's not sufficient, then perhaps this pin (GPIO 3) may never be fully documented in Pinout.xyz?? There is an abundance of anecdotal documentation (RPi forums, independent blogs, Stack Exchange, etc) to support this function for GPIO 3, but given The Foundation's long-standing omission from their documentation, it seems doubtful it will ever be included.

In summary, and FWIW, I feel that @matthijskooijman's proposal would improve the utility of Pinout.xyz.

@matthijskooijman
Copy link
Author

In this case it might be better to make contributions to the elinux wiki (https://elinux.org/Special:RequestAccount) or Raspberry Pi documentation itself (https://github.com/raspberrypi/documentation).

I'm not willing to free up enough time to get that documentation up-to-date in this area, sorry.

Oddly, the only concrete documentation I can find is in their /boot/overlays/README file under the overlay called gpio-shutdown.

FWIW, that was also written by me when I submitted that overlay when I first wrote the linked blogpost.

If it helps: I have been taking the effort of keeping my blogpost up-to-date with newer developments, based on comments and my own discoveries (i.e. for newer hardware, or when relevant documentation or discussions show up).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants