* [PATCH 8/8] docs: use misc-devices/ dir for drivers
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 0:04 ` [PATCH 4/8] docbook: signal_pending has an argument Randy Dunlap
` (5 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Jean Delvare
From: Jean Delvare <khali@linux-fr.org>
Subject: Doc: use misc-devices/ dir for drivers
We have a directory for misc drivers documentation, let's use it.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Rodolfo Giometti <giometti@linux.it>
---
Resending with proper name quoting, sorry for the noise.
Documentation/c2port.txt | 90 ------------------------
Documentation/ics932s401 | 31 --------
Documentation/misc-devices/c2port.txt | 90 ++++++++++++++++++++++++
Documentation/misc-devices/ics932s401 | 31 ++++++++
4 files changed, 121 insertions(+), 121 deletions(-)
--- lnx-2632-rc6.orig/Documentation/c2port.txt
+++ /dev/null
@@ -1,90 +0,0 @@
- C2 port support
- ---------------
-
-(C) Copyright 2007 Rodolfo Giometti <giometti@enneenne.com>
-
-This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or
-(at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-
-
-Overview
---------
-
-This driver implements the support for Linux of Silicon Labs (Silabs)
-C2 Interface used for in-system programming of micro controllers.
-
-By using this driver you can reprogram the in-system flash without EC2
-or EC3 debug adapter. This solution is also useful in those systems
-where the micro controller is connected via special GPIOs pins.
-
-References
-----------
-
-The C2 Interface main references are at (http://www.silabs.com)
-Silicon Laboratories site], see:
-
-- AN127: FLASH Programming via the C2 Interface at
-http://www.silabs.com/public/documents/tpub_doc/anote/Microcontrollers/Small_Form_Factor/en/an127.pdf, and
-
-- C2 Specification at
-http://www.silabs.com/public/documents/tpub_doc/spec/Microcontrollers/en/C2spec.pdf,
-
-however it implements a two wire serial communication protocol (bit
-banging) designed to enable in-system programming, debugging, and
-boundary-scan testing on low pin-count Silicon Labs devices. Currently
-this code supports only flash programming but extensions are easy to
-add.
-
-Using the driver
-----------------
-
-Once the driver is loaded you can use sysfs support to get C2port's
-info or read/write in-system flash.
-
-# ls /sys/class/c2port/c2port0/
-access flash_block_size flash_erase rev_id
-dev_id flash_blocks_num flash_size subsystem/
-flash_access flash_data reset uevent
-
-Initially the C2port access is disabled since you hardware may have
-such lines multiplexed with other devices so, to get access to the
-C2port, you need the command:
-
-# echo 1 > /sys/class/c2port/c2port0/access
-
-after that you should read the device ID and revision ID of the
-connected micro controller:
-
-# cat /sys/class/c2port/c2port0/dev_id
-8
-# cat /sys/class/c2port/c2port0/rev_id
-1
-
-However, for security reasons, the in-system flash access in not
-enabled yet, to do so you need the command:
-
-# echo 1 > /sys/class/c2port/c2port0/flash_access
-
-After that you can read the whole flash:
-
-# cat /sys/class/c2port/c2port0/flash_data > image
-
-erase it:
-
-# echo 1 > /sys/class/c2port/c2port0/flash_erase
-
-and write it:
-
-# cat image > /sys/class/c2port/c2port0/flash_data
-
-after writing you have to reset the device to execute the new code:
-
-# echo 1 > /sys/class/c2port/c2port0/reset
--- lnx-2632-rc6.orig/Documentation/ics932s401
+++ /dev/null
@@ -1,31 +0,0 @@
-Kernel driver ics932s401
-======================
-
-Supported chips:
- * IDT ICS932S401
- Prefix: 'ics932s401'
- Addresses scanned: I2C 0x69
- Datasheet: Publically available at the IDT website
-
-Author: Darrick J. Wong
-
-Description
------------
-
-This driver implements support for the IDT ICS932S401 chip family.
-
-This chip has 4 clock outputs--a base clock for the CPU (which is likely
-multiplied to get the real CPU clock), a system clock, a PCI clock, a USB
-clock, and a reference clock. The driver reports selected and actual
-frequency. If spread spectrum mode is enabled, the driver also reports by what
-percent the clock signal is being spread, which should be between 0 and -0.5%.
-All frequencies are reported in KHz.
-
-The ICS932S401 monitors all inputs continuously. The driver will not read
-the registers more often than once every other second.
-
-Special Features
-----------------
-
-The clocks could be reprogrammed to increase system speed. I will not help you
-do this, as you risk damaging your system!
--- /dev/null
+++ lnx-2632-rc6/Documentation/misc-devices/c2port.txt
@@ -0,0 +1,90 @@
+ C2 port support
+ ---------------
+
+(C) Copyright 2007 Rodolfo Giometti <giometti@enneenne.com>
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+
+
+Overview
+--------
+
+This driver implements the support for Linux of Silicon Labs (Silabs)
+C2 Interface used for in-system programming of micro controllers.
+
+By using this driver you can reprogram the in-system flash without EC2
+or EC3 debug adapter. This solution is also useful in those systems
+where the micro controller is connected via special GPIOs pins.
+
+References
+----------
+
+The C2 Interface main references are at (http://www.silabs.com)
+Silicon Laboratories site], see:
+
+- AN127: FLASH Programming via the C2 Interface at
+http://www.silabs.com/public/documents/tpub_doc/anote/Microcontrollers/Small_Form_Factor/en/an127.pdf, and
+
+- C2 Specification at
+http://www.silabs.com/public/documents/tpub_doc/spec/Microcontrollers/en/C2spec.pdf,
+
+however it implements a two wire serial communication protocol (bit
+banging) designed to enable in-system programming, debugging, and
+boundary-scan testing on low pin-count Silicon Labs devices. Currently
+this code supports only flash programming but extensions are easy to
+add.
+
+Using the driver
+----------------
+
+Once the driver is loaded you can use sysfs support to get C2port's
+info or read/write in-system flash.
+
+# ls /sys/class/c2port/c2port0/
+access flash_block_size flash_erase rev_id
+dev_id flash_blocks_num flash_size subsystem/
+flash_access flash_data reset uevent
+
+Initially the C2port access is disabled since you hardware may have
+such lines multiplexed with other devices so, to get access to the
+C2port, you need the command:
+
+# echo 1 > /sys/class/c2port/c2port0/access
+
+after that you should read the device ID and revision ID of the
+connected micro controller:
+
+# cat /sys/class/c2port/c2port0/dev_id
+8
+# cat /sys/class/c2port/c2port0/rev_id
+1
+
+However, for security reasons, the in-system flash access in not
+enabled yet, to do so you need the command:
+
+# echo 1 > /sys/class/c2port/c2port0/flash_access
+
+After that you can read the whole flash:
+
+# cat /sys/class/c2port/c2port0/flash_data > image
+
+erase it:
+
+# echo 1 > /sys/class/c2port/c2port0/flash_erase
+
+and write it:
+
+# cat image > /sys/class/c2port/c2port0/flash_data
+
+after writing you have to reset the device to execute the new code:
+
+# echo 1 > /sys/class/c2port/c2port0/reset
--- /dev/null
+++ lnx-2632-rc6/Documentation/misc-devices/ics932s401
@@ -0,0 +1,31 @@
+Kernel driver ics932s401
+======================
+
+Supported chips:
+ * IDT ICS932S401
+ Prefix: 'ics932s401'
+ Addresses scanned: I2C 0x69
+ Datasheet: Publically available at the IDT website
+
+Author: Darrick J. Wong
+
+Description
+-----------
+
+This driver implements support for the IDT ICS932S401 chip family.
+
+This chip has 4 clock outputs--a base clock for the CPU (which is likely
+multiplied to get the real CPU clock), a system clock, a PCI clock, a USB
+clock, and a reference clock. The driver reports selected and actual
+frequency. If spread spectrum mode is enabled, the driver also reports by what
+percent the clock signal is being spread, which should be between 0 and -0.5%.
+All frequencies are reported in KHz.
+
+The ICS932S401 monitors all inputs continuously. The driver will not read
+the registers more often than once every other second.
+
+Special Features
+----------------
+
+The clocks could be reprogrammed to increase system speed. I will not help you
+do this, as you risk damaging your system!
--
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 4/8] docbook: signal_pending has an argument
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 8/8] docs: use misc-devices/ dir for drivers Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 0:04 ` [PATCH 2/8] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
` (4 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Shawn Bohrer
From: Shawn Bohrer <shawn.bohrer@gmail.com>
Subject: docbook: fix signal_pending() argument
Since signal_pending() takes a task_struct pointer as an argument, update
the example to pass in 'current'.
Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DocBook/kernel-hacking.tmpl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- lnx-2632-rc6.orig/Documentation/DocBook/kernel-hacking.tmpl
+++ lnx-2632-rc6/Documentation/DocBook/kernel-hacking.tmpl
@@ -352,7 +352,7 @@ asmlinkage long sys_mycall(int arg)
</para>
<programlisting>
-if (signal_pending())
+if (signal_pending(current))
return -ERESTARTSYS;
</programlisting>
--
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 2/8] docs: use KERN_WARNING, not KERN_WARN
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 8/8] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-11-05 0:04 ` [PATCH 4/8] docbook: signal_pending has an argument Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 0:04 ` [PATCH 3/8] docs: use DMA_BIT_MASK Randy Dunlap
` (3 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Andrew Lyon
From: Randy Dunlap <randy.dunlap@oracle.com>
Subject: Use KERN_WARNING instead of KERN_WARN, which does not exist
Reported-by: Andrew Lyon <andrew.lyon@gmail.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DMA-mapping.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- lnx-2632-rc6.orig/Documentation/DMA-mapping.txt
+++ lnx-2632-rc6/Documentation/DMA-mapping.txt
@@ -224,14 +224,14 @@ Here is pseudo-code showing how this mig
card->playback_enabled = 1;
} else {
card->playback_enabled = 0;
- printk(KERN_WARN "%s: Playback disabled due to DMA limitations.\n",
+ printk(KERN_WARNING "%s: Playback disabled due to DMA limitations.\n",
card->name);
}
if (!pci_set_dma_mask(pdev, RECORD_ADDRESS_BITS)) {
card->record_enabled = 1;
} else {
card->record_enabled = 0;
- printk(KERN_WARN "%s: Record disabled due to DMA limitations.\n",
+ printk(KERN_WARNING "%s: Record disabled due to DMA limitations.\n",
card->name);
}
--
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 3/8] docs: use DMA_BIT_MASK
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
` (2 preceding siblings ...)
2009-11-05 0:04 ` [PATCH 2/8] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 0:04 ` [PATCH 7/8] docs: serial/tty, add to ldisc methods Randy Dunlap
` (2 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Marin Mitov
From: Marin Mitov <mitov@issp.bas.bg>
Subject: use DMA_BIT_MASK instead of inline constant
Use DMA_BIT_MASK(24) instead of 0x00ffffff in DMA-mapping.txt
Signed-off-by: Marin Mitov <mitov@issp.bas.bg>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DMA-mapping.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- lnx-2632-rc6.orig/Documentation/DMA-mapping.txt
+++ lnx-2632-rc6/Documentation/DMA-mapping.txt
@@ -214,7 +214,7 @@ most specific mask.
Here is pseudo-code showing how this might be done:
#define PLAYBACK_ADDRESS_BITS DMA_BIT_MASK(32)
- #define RECORD_ADDRESS_BITS 0x00ffffff
+ #define RECORD_ADDRESS_BITS DMA_BIT_MASK(24)
struct my_sound_card *card;
struct pci_dev *pdev;
--
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 7/8] docs: serial/tty, add to ldisc methods
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
` (3 preceding siblings ...)
2009-11-05 0:04 ` [PATCH 3/8] docs: use DMA_BIT_MASK Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 0:16 ` Alan Cox
2009-11-05 0:04 ` [PATCH 6/8] docs: explain procs_running better Randy Dunlap
2009-11-05 8:10 ` [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Takashi Iwai
6 siblings, 1 reply; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Tilman Schmidt, Greg Kroah-Hartman
From: Tilman Schmidt <tilman@imap.cc>
Subject: Doc: update serial/tty.txt ldisc methods
A small addition to the ldisc method descriptions.
Impact: Documentation
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
---
Documentation/serial/tty.txt | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--- lnx-2632-rc6.orig/Documentation/serial/tty.txt
+++ lnx-2632-rc6/Documentation/serial/tty.txt
@@ -42,7 +42,8 @@ TTY side interfaces:
open() - Called when the line discipline is attached to
the terminal. No other call into the line
discipline for this tty will occur until it
- completes successfully. Can sleep.
+ completes successfully. Returning an error will
+ prevent the ldisc from being attached. Can sleep.
close() - This is called on a terminal when the line
discipline is being unplugged. At the point of
@@ -52,7 +53,7 @@ close() - This is called on a terminal
hangup() - Called when the tty line is hung up.
The line discipline should cease I/O to the tty.
No further calls into the ldisc code will occur.
- Can sleep.
+ The return value is ignored. Can sleep.
write() - A process is writing data through the line
discipline. Multiple write calls are serialized
@@ -83,6 +84,10 @@ ioctl() - Called when an ioctl is hande
that might be for the ldisc. Multiple ioctl calls
may occur in parallel. May sleep.
+compat_ioctl() - Called when a 32 bit ioctl is handed to the tty layer
+ that might be for the ldisc. Multiple ioctl calls
+ may occur in parallel. May sleep.
+
Driver Side Interfaces:
receive_buf() - Hand buffers of bytes from the driver to the ldisc
--
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 6/8] docs: explain procs_running better
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
` (4 preceding siblings ...)
2009-11-05 0:04 ` [PATCH 7/8] docs: serial/tty, add to ldisc methods Randy Dunlap
@ 2009-11-05 0:04 ` Randy Dunlap
2009-11-05 8:10 ` [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Takashi Iwai
6 siblings, 0 replies; 9+ messages in thread
From: Randy Dunlap @ 2009-11-05 0:04 UTC (permalink / raw)
To: linux-kernel; +Cc: Luis Garces-Erice
From: Luis Garces-Erice <lge@ieee.org>
Subject: Doc: better explanation of procs_running
the description in Documentation/filesystems/proc.txt of the
procs_running entry in /proc/stat is confusing (according to that
description, it looks as if procs_running could only be a number
between 0 and the number of CPUs).
Changed it to a more accurate description in the patch attached.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/filesystems/proc.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- lnx-2632-rc6.orig/Documentation/filesystems/proc.txt
+++ lnx-2632-rc6/Documentation/filesystems/proc.txt
@@ -1088,8 +1088,8 @@ The "processes" line gives the number o
includes (but is not limited to) those created by calls to the fork() and
clone() system calls.
-The "procs_running" line gives the number of processes currently running on
-CPUs.
+The "procs_running" line gives the total number of threads that are
+running or ready to run (i.e., the total number of runnable threads).
The "procs_blocked" line gives the number of processes currently blocked,
waiting for I/O to complete.
--
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
` (5 preceding siblings ...)
2009-11-05 0:04 ` [PATCH 6/8] docs: explain procs_running better Randy Dunlap
@ 2009-11-05 8:10 ` Takashi Iwai
6 siblings, 0 replies; 9+ messages in thread
From: Takashi Iwai @ 2009-11-05 8:10 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-kernel, Jaroslav Kysela, Takashi Iwai
At Wed, 04 Nov 2009 16:04:52 -0800,
Randy Dunlap wrote:
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
> Subject: Use KERN_WARNING instead of KERN_WARN, which does not exist
>
> Reported-by: Andrew Lyon <andrew.lyon@gmail.com>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.de>
Applied now. Thanks.
Takashi
> ---
> sound/oss/sb_common.c | 4 ++--
> sound/oss/sb_ess.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> --- lnx-2632-rc6.orig/sound/oss/sb_common.c
> +++ lnx-2632-rc6/sound/oss/sb_common.c
> @@ -157,7 +157,7 @@ static void sb_intr (sb_devc *devc)
> break;
>
> default:
> - /* printk(KERN_WARN "Sound Blaster: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "Sound Blaster: Unexpected interrupt\n"); */
> ;
> }
> }
> @@ -177,7 +177,7 @@ static void sb_intr (sb_devc *devc)
> break;
>
> default:
> - /* printk(KERN_WARN "Sound Blaster: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "Sound Blaster: Unexpected interrupt\n"); */
> ;
> }
> }
> --- lnx-2632-rc6.orig/sound/oss/sb_ess.c
> +++ lnx-2632-rc6/sound/oss/sb_ess.c
> @@ -782,7 +782,7 @@ printk(KERN_INFO "FKS: ess_handle_channe
> break;
>
> default:;
> - /* printk(KERN_WARN "ESS: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "ESS: Unexpected interrupt\n"); */
> }
> }
>
>
>
> --
>
^ permalink raw reply [flat|nested] 9+ messages in thread