Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 547d4c10 authored by Masanari Iida's avatar Masanari Iida Committed by Jonathan Corbet
Browse files

Doc: gpio: Fix typos in Documentation/gpio 



This patch fix some spelling typos found in Documentation/gpio.

Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 32d79b02

Documentation/gpio/consumer.txt

+1 −1
Original line number Diff line number Diff line
@@ -260,7 +260,7 @@ will be driven low. 


To summarize:



Function (example)               active-low proporty  physical line

Function (example)               active-low property  physical line

gpiod_set_raw_value(desc, 0);        don't care           low

gpiod_set_raw_value(desc, 1);        don't care           high

gpiod_set_value(desc, 0);       default (active-high)     low

Documentation/gpio/driver.txt

+3 −3
Original line number Diff line number Diff line
@@ -113,8 +113,8 @@ GPIO irqchips usually fall in one of two categories: 
  it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT

  (for example, see [3]).

  Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,

  so IRQ core will complain if it will be called from IRQ handler wich is forced

  thread. The "fake?" raw lock can be used to W/A this problem:

  so IRQ core will complain if it will be called from IRQ handler which is

  forced thread. The "fake?" raw lock can be used to W/A this problem:



	raw_spinlock_t wa_lock;

	static irqreturn_t omap_gpio_irq_handler(int irq, void *gpiobank)
@@ -224,7 +224,7 @@ Real-Time compliance for GPIO IRQ chips 
---------------------------------------



Any provider of irqchips needs to be carefully tailored to support Real Time

preemption. It is desireable that all irqchips in the GPIO subsystem keep this

preemption. It is desirable that all irqchips in the GPIO subsystem keep this

in mind and does the proper testing to assure they are real time-enabled.

So, pay attention on above " RT_FULL:" notes, please.

The following is a checklist to follow when preparing a driver for real

Documentation/gpio/drivers-on-gpio.txt

+3 −3
Original line number Diff line number Diff line
@@ -75,7 +75,7 @@ hardware descriptions such as device tree or ACPI: 


- gpio-wdt: drivers/watchdog/gpio_wdt.c is used to provide a watchdog timer

  that will periodically "ping" a hardware connected to a GPIO line by toggling

  it from 1-to-0-to-1. If that hardware does not recieve its "ping"

  it from 1-to-0-to-1. If that hardware does not receive its "ping"

  periodically, it will reset the system.



- gpio-nand: drivers/mtd/nand/gpio.c is used to connect a NAND flash chip to
@@ -91,5 +91,5 @@ usually connected directly to the flash. 


Use those instead of talking directly to the GPIOs using sysfs; they integrate

with kernel frameworks better than your userspace code could. Needless to say,

just using the apropriate kernel drivers will simplify and speed up your

just using the appropriate kernel drivers will simplify and speed up your

embedded hacking in particular by providing ready-made components.