Changes between Version 24 and Version 25 of faq

Timestamp:

08/24/2018 10:01:56 PM (6 years ago)

Author:

Ryan Erbstoesser

Comment:

update URLS as internal wiki URLS rather than using the whole path. add gsc sleep

faq

@@ -269 +269 @@
 Getting our GSC driver to be adopted by the mainline kernel community has been an up hill battle, hence the long delay in its implementation.  Many of its features are still accessible using I2C commands and other methods: 
 * The RTC is compatible with the standard Linux ds1672 RTC driver and thus works with the standard Linux RTC device API. 
- * http://trac.gateworks.com/wiki/gsc#RealTimeClock
+ * [wiki:gsc#RealTimeClock GSC RTC]
 * Voltage and temperature monitoring can be accomplished using I2C commands.
- * http://trac.gateworks.com/wiki/gsc#SystemTemperatureandVoltageMonitor
+ * [wiki:gsc#SystemTemperatureandVoltageMonitor Temp & Voltage Monitor]
 * GPIO expansion does not require GSC drivers.
- * http://trac.gateworks.com/wiki/gsc#GeneralPurposeInputandOutputGPIO
- * http://trac.gateworks.com/wiki/gpio
+ * [wiki:gsc#GeneralPurposeInputandOutputGPIO GSC GPIO]
+ * [wiki:gpio Generic GPIO]
 * Linux input event support will be lost, there is currently no work around for this.
- * http://trac.gateworks.com/wiki/gsc#GSCInputkerneldriver
+ * [wiki:gsc#GSCInputkerneldriver GSC Input Driver]
 * Hardware watchdog, this is where you may run into trouble using GSC, though the CPU watchdog will be adequate in many cases.  The issue here will be the inability for the GSC to disable board power. 
- * http://trac.gateworks.com/wiki/gsc#HardwareWatchdog
+ * [wiki:gsc#HardwareWatchdog GSC Watchdog]
 * Field firmware updates (via gsc_update tool) do not depend on the gsc driver
- * http://trac.gateworks.com/wiki/gsc#GSCUpdates
+ * [wiki:gsc#GSCUpdates GSC Updates]
+* GSC Sleep
+ * [wiki:gsc#HardwareSleepandWake GSC Sleep]