---

yaml --- r: 319195 b: refs/heads/master c: f051c46 h: refs/heads/master i: 319193: 79fd9c3 319191: 35913d1 v: v3
git-mirror · Jun 15, 2012 · 01db6ed · 01db6ed
1 parent c0f374c
commit 01db6ed
Show file tree

Hide file tree

Showing 4 changed files with 255 additions and 94 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 0c2498f1660878339350bea8d18550b1b87ca055
+refs/heads/master: f051c466cf690ac661d713d3ceb56b4efcecc853
diff --git a/trunk/Documentation/pwm.txt b/trunk/Documentation/pwm.txt
@@ -33,9 +33,12 @@ there only has been the barebone API meaning that each driver has
 to implement the pwm_*() functions itself. This means that it's impossible
 to have multiple PWM drivers in the system. For this reason it's mandatory
 for new drivers to use the generic PWM framework.
-A new PWM device can be added using pwmchip_add() and removed again with
-pwmchip_remove(). pwmchip_add() takes a filled in struct pwm_chip as
-argument which provides the ops and the pwm id to the framework.
+
+A new PWM controller/chip can be added using pwmchip_add() and removed
+again with pwmchip_remove(). pwmchip_add() takes a filled in struct
+pwm_chip as argument which provides a description of the PWM chip, the
+number of PWM devices provider by the chip and the chip-specific
+implementation of the supported PWM operations to the framework.
 
 Locking
 -------