Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history 
yaml
---
r: 127871
b: refs/heads/master
c: 71610f5
h: refs/heads/master
i:
  127869: 0b1417d
  127867: 55f008e
  127863: e8be41a
  127855: 336179e
  127839: e362ad5
  127807: 0f30761
  127743: 3e60ee1
v: v3
  • Loading branch information
Kay Sievers authored and James Bottomley committed Jan 2, 2009
1 parent 5c83e9d commit 262e8f9
Show file tree
Hide file tree
Showing 3,868 changed files with 90,939 additions and 627,702 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
2 changes: 1 addition & 1 deletion [refs]
View file
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: 97d61b8e3aef163a75f80f4762794c154572293d
refs/heads/master: 71610f55fa4db63dbf5385929a47c9fb2451f332
1 change: 0 additions & 1 deletion trunk/.mailmap
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,6 @@ Christoph Hellwig <hch@lst.de>
Corey Minyard <minyard@acm.org>
David Brownell <david-b@pacbell.net>
David Woodhouse <dwmw2@shinybook.infradead.org>
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Domen Puncer <domen@coderock.org>
Douglas Gilbert <dougg@torque.net>
Ed L. Cashin <ecashin@coraid.com>
Expand Down
27 changes: 5 additions & 22 deletions trunk/CREDITS
View file
Original file line number Diff line number Diff line change
Expand Up @@ -369,10 +369,10 @@ P: 1024/8462A731 4C 55 86 34 44 59 A7 99 2B 97 88 4A 88 9A 0D 97
D: sun4 port, Sparc hacker

N: Hugh Blemings
E: hugh@blemings.org
W: http://blemings.org/hugh
D: Original author of the Keyspan USB to serial drivers, random PowerPC hacker
S: PO Box 234
E: hugh@misc.nu
W: http://misc.nu/hugh/
D: Author and maintainer of the Keyspan USB to Serial drivers
S: Po Box 234
S: Belconnen ACT 2616
S: Australia

Expand Down Expand Up @@ -464,11 +464,6 @@ S: 1200 Goldenrod Dr.
S: Nampa, Idaho 83686
S: USA

N: Dirk J. Brandewie
E: dirk.j.brandewie@intel.com
E: linux-wimax@intel.com
D: Intel Wireless WiMAX Connection 2400 SDIO driver

N: Derrick J. Brashear
E: shadow@dementia.org
W: http://www.dementia.org/~shadow
Expand Down Expand Up @@ -1686,7 +1681,7 @@ E: ajoshi@shell.unixbox.com
D: fbdev hacking

N: Jesper Juhl
E: jj@chaosbits.net
E: jesper.juhl@gmail.com
D: Various fixes, cleanups and minor features all over the tree.
D: Wrote initial version of the hdaps driver (since passed on to others).
S: Lemnosvej 1, 3.tv
Expand Down Expand Up @@ -2124,11 +2119,6 @@ N: H.J. Lu
E: hjl@gnu.ai.mit.edu
D: GCC + libraries hacker

N: Yanir Lubetkin
E: yanirx.lubatkin@intel.com
E: linux-wimax@intel.com
D: Intel Wireless WiMAX Connection 2400 driver

N: Michal Ludvig
E: michal@logix.cz
E: michal.ludvig@asterisk.co.nz
Expand Down Expand Up @@ -2703,13 +2693,6 @@ S: RR #5, 497 Pole Line Road
S: Thunder Bay, Ontario
S: CANADA P7C 5M9

N: Inaky Perez-Gonzalez
E: inaky.perez-gonzalez@intel.com
E: linux-wimax@intel.com
E: inakypg@yahoo.com
D: WiMAX stack
D: Intel Wireless WiMAX Connection 2400 driver

N: Yuri Per
E: yuri@pts.mipt.ru
D: Some smbfs fixes
Expand Down
136 changes: 76 additions & 60 deletions trunk/Documentation/ABI/testing/sysfs-class-regulator
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,8 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
state. This reports the regulator enable status, for
regulators which can report that value.
Each regulator directory will contain a field called
state. This holds the regulator output state.

This will be one of the following strings:

Expand All @@ -19,8 +18,7 @@ Description:
'disabled' means the regulator output is OFF and is not
supplying power to the system..

'unknown' means software cannot determine the state, or
the reported state is invalid.
'unknown' means software cannot determine the state.

NOTE: this field can be used in conjunction with microvolts
and microamps to determine regulator output levels.
Expand Down Expand Up @@ -55,10 +53,9 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
microvolts. This holds the regulator output voltage setting
measured in microvolts (i.e. E-6 Volts), for regulators
which can report that voltage.
measured in microvolts (i.e. E-6 Volts).

NOTE: This value should not be used to determine the regulator
output voltage level as this value is the same regardless of
Expand All @@ -70,10 +67,9 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
microamps. This holds the regulator output current limit
setting measured in microamps (i.e. E-6 Amps), for regulators
which can report that current.
setting measured in microamps (i.e. E-6 Amps).

NOTE: This value should not be used to determine the regulator
output current level as this value is the same regardless of
Expand All @@ -85,9 +81,8 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
opmode. This holds the current regulator operating mode,
for regulators which can report it.
Each regulator directory will contain a field called
opmode. This holds the regulator operating mode setting.

The opmode value can be one of the following strings:

Expand All @@ -97,7 +92,7 @@ Description:
'standby'
'unknown'

The modes are described in include/linux/regulator/consumer.h
The modes are described in include/linux/regulator/regulator.h

NOTE: This value should not be used to determine the regulator
output operating mode as this value is the same regardless of
Expand All @@ -109,10 +104,9 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
min_microvolts. This holds the minimum safe working regulator
output voltage setting for this domain measured in microvolts,
for regulators which support voltage constraints.
output voltage setting for this domain measured in microvolts.

NOTE: this will return the string 'constraint not defined' if
the power domain has no min microvolts constraint defined by
Expand All @@ -124,10 +118,9 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
max_microvolts. This holds the maximum safe working regulator
output voltage setting for this domain measured in microvolts,
for regulators which support voltage constraints.
output voltage setting for this domain measured in microvolts.

NOTE: this will return the string 'constraint not defined' if
the power domain has no max microvolts constraint defined by
Expand All @@ -139,10 +132,10 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
min_microamps. This holds the minimum safe working regulator
output current limit setting for this domain measured in
microamps, for regulators which support current constraints.
microamps.

NOTE: this will return the string 'constraint not defined' if
the power domain has no min microamps constraint defined by
Expand All @@ -154,10 +147,10 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
max_microamps. This holds the maximum safe working regulator
output current limit setting for this domain measured in
microamps, for regulators which support current constraints.
microamps.

NOTE: this will return the string 'constraint not defined' if
the power domain has no max microamps constraint defined by
Expand Down Expand Up @@ -192,7 +185,7 @@ Date: April 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
requested_microamps. This holds the total requested load
current in microamps for this regulator from all its consumer
devices.
Expand All @@ -211,102 +204,125 @@ Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_mem_microvolts. This holds the regulator output
voltage setting for this domain measured in microvolts when
the system is suspended to memory, for voltage regulators
implementing suspend voltage configuration constraints.
the system is suspended to memory.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to memory voltage defined by
platform code.

What: /sys/class/regulator/.../suspend_disk_microvolts
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_disk_microvolts. This holds the regulator output
voltage setting for this domain measured in microvolts when
the system is suspended to disk, for voltage regulators
implementing suspend voltage configuration constraints.
the system is suspended to disk.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to disk voltage defined by
platform code.

What: /sys/class/regulator/.../suspend_standby_microvolts
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_standby_microvolts. This holds the regulator output
voltage setting for this domain measured in microvolts when
the system is suspended to standby, for voltage regulators
implementing suspend voltage configuration constraints.
the system is suspended to standby.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to standby voltage defined by
platform code.

What: /sys/class/regulator/.../suspend_mem_mode
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_mem_mode. This holds the regulator operating mode
setting for this domain when the system is suspended to
memory, for regulators implementing suspend mode
configuration constraints.
memory.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to memory mode defined by
platform code.

What: /sys/class/regulator/.../suspend_disk_mode
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_disk_mode. This holds the regulator operating mode
setting for this domain when the system is suspended to disk,
for regulators implementing suspend mode configuration
constraints.
setting for this domain when the system is suspended to disk.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to disk mode defined by
platform code.

What: /sys/class/regulator/.../suspend_standby_mode
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_standby_mode. This holds the regulator operating mode
setting for this domain when the system is suspended to
standby, for regulators implementing suspend mode
configuration constraints.
standby.

NOTE: this will return the string 'not defined' if
the power domain has no suspend to standby mode defined by
platform code.

What: /sys/class/regulator/.../suspend_mem_state
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_mem_state. This holds the regulator operating state
when suspended to memory, for regulators implementing suspend
configuration constraints.
when suspended to memory.

This will be one of the following strings:

This will be one of the same strings reported by
the "state" attribute.
'enabled'
'disabled'
'not defined'

What: /sys/class/regulator/.../suspend_disk_state
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_disk_state. This holds the regulator operating state
when suspended to disk, for regulators implementing
suspend configuration constraints.
when suspended to disk.

This will be one of the following strings:

This will be one of the same strings reported by
the "state" attribute.
'enabled'
'disabled'
'not defined'

What: /sys/class/regulator/.../suspend_standby_state
Date: May 2008
KernelVersion: 2.6.26
Contact: Liam Girdwood <lrg@slimlogic.co.uk>
Description:
Some regulator directories will contain a field called
Each regulator directory will contain a field called
suspend_standby_state. This holds the regulator operating
state when suspended to standby, for regulators implementing
suspend configuration constraints.
state when suspended to standby.

This will be one of the following strings:

This will be one of the same strings reported by
the "state" attribute.
'enabled'
'disabled'
'not defined'
14 changes: 6 additions & 8 deletions trunk/Documentation/ABI/testing/sysfs-class-uwb_rc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,16 +32,14 @@ Contact: linux-usb@vger.kernel.org
Description:
Write:

<channel>
<channel> [<bpst offset>]

to force a specific channel to be used when beaconing,
or, if <channel> is -1, to prohibit beaconing. If
<channel> is 0, then the default channel selection
algorithm will be used. Valid channels depends on the
radio controller's supported band groups.
to start beaconing on a specific channel, or stop
beaconing if <channel> is -1. Valid channels depends
on the radio controller's supported band groups.

Reading returns the currently active channel, or -1 if
the radio controller is not beaconing.
<bpst offset> may be used to try and join a specific
beacon group if more than one was found during a scan.

What: /sys/class/uwb_rc/uwbN/scan
Date: July 2008
Expand Down
Loading

0 comments on commit 262e8f9

Please sign in to comment.