License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 08:07:57 -06:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2010-07-27 02:28:30 -06:00
|
|
|
/*
|
|
|
|
|
* Chip register definitions for PCILynx chipset. Based on pcilynx.h
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
* from the Linux 1394 drivers, but modified a bit so the names here
|
|
|
|
|
* match the specification exactly (even though they have weird names,
|
|
|
|
|
* like xxx_OVER_FLOW, or arbitrary abbreviations like SNTRJ for "sent
|
|
|
|
|
* reject" etc.)
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#define PCILYNX_MAX_REGISTER 0xfff
|
|
|
|
|
#define PCILYNX_MAX_MEMORY 0xffff
|
|
|
|
|
|
|
|
|
|
#define PCI_LATENCY_CACHELINE 0x0c
|
|
|
|
|
|
|
|
|
|
#define MISC_CONTROL 0x40
|
|
|
|
|
#define MISC_CONTROL_SWRESET (1<<0)
|
|
|
|
|
|
|
|
|
|
#define SERIAL_EEPROM_CONTROL 0x44
|
|
|
|
|
|
|
|
|
|
#define PCI_INT_STATUS 0x48
|
2010-07-27 02:28:30 -06:00
|
|
|
#define PCI_INT_ENABLE 0x4c
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
/* status and enable have identical bit numbers */
|
|
|
|
|
#define PCI_INT_INT_PEND (1<<31)
|
|
|
|
|
#define PCI_INT_FRC_INT (1<<30)
|
|
|
|
|
#define PCI_INT_SLV_ADR_PERR (1<<28)
|
|
|
|
|
#define PCI_INT_SLV_DAT_PERR (1<<27)
|
|
|
|
|
#define PCI_INT_MST_DAT_PERR (1<<26)
|
|
|
|
|
#define PCI_INT_MST_DEV_TO (1<<25)
|
|
|
|
|
#define PCI_INT_INT_SLV_TO (1<<23)
|
|
|
|
|
#define PCI_INT_AUX_TO (1<<18)
|
|
|
|
|
#define PCI_INT_AUX_INT (1<<17)
|
|
|
|
|
#define PCI_INT_P1394_INT (1<<16)
|
|
|
|
|
#define PCI_INT_DMA4_PCL (1<<9)
|
|
|
|
|
#define PCI_INT_DMA4_HLT (1<<8)
|
|
|
|
|
#define PCI_INT_DMA3_PCL (1<<7)
|
|
|
|
|
#define PCI_INT_DMA3_HLT (1<<6)
|
|
|
|
|
#define PCI_INT_DMA2_PCL (1<<5)
|
|
|
|
|
#define PCI_INT_DMA2_HLT (1<<4)
|
|
|
|
|
#define PCI_INT_DMA1_PCL (1<<3)
|
|
|
|
|
#define PCI_INT_DMA1_HLT (1<<2)
|
|
|
|
|
#define PCI_INT_DMA0_PCL (1<<1)
|
|
|
|
|
#define PCI_INT_DMA0_HLT (1<<0)
|
|
|
|
|
/* all DMA interrupts combined: */
|
|
|
|
|
#define PCI_INT_DMA_ALL 0x3ff
|
|
|
|
|
|
|
|
|
|
#define PCI_INT_DMA_HLT(chan) (1 << (chan * 2))
|
|
|
|
|
#define PCI_INT_DMA_PCL(chan) (1 << (chan * 2 + 1))
|
|
|
|
|
|
|
|
|
|
#define LBUS_ADDR 0xb4
|
|
|
|
|
#define LBUS_ADDR_SEL_RAM (0x0<<16)
|
|
|
|
|
#define LBUS_ADDR_SEL_ROM (0x1<<16)
|
|
|
|
|
#define LBUS_ADDR_SEL_AUX (0x2<<16)
|
2010-07-27 02:28:30 -06:00
|
|
|
#define LBUS_ADDR_SEL_ZV (0x3<<16)
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
|
|
|
|
|
#define GPIO_CTRL_A 0xb8
|
|
|
|
|
#define GPIO_CTRL_B 0xbc
|
|
|
|
|
#define GPIO_DATA_BASE 0xc0
|
|
|
|
|
|
|
|
|
|
#define DMA_BREG(base, chan) (base + chan * 0x20)
|
|
|
|
|
#define DMA_SREG(base, chan) (base + chan * 0x10)
|
|
|
|
|
|
|
|
|
|
#define PCL_NEXT_INVALID (1<<0)
|
|
|
|
|
|
|
|
|
|
/* transfer commands */
|
|
|
|
|
#define PCL_CMD_RCV (0x1<<24)
|
|
|
|
|
#define PCL_CMD_RCV_AND_UPDATE (0xa<<24)
|
|
|
|
|
#define PCL_CMD_XMT (0x2<<24)
|
|
|
|
|
#define PCL_CMD_UNFXMT (0xc<<24)
|
|
|
|
|
#define PCL_CMD_PCI_TO_LBUS (0x8<<24)
|
|
|
|
|
#define PCL_CMD_LBUS_TO_PCI (0x9<<24)
|
|
|
|
|
|
|
|
|
|
/* aux commands */
|
|
|
|
|
#define PCL_CMD_NOP (0x0<<24)
|
|
|
|
|
#define PCL_CMD_LOAD (0x3<<24)
|
|
|
|
|
#define PCL_CMD_STOREQ (0x4<<24)
|
|
|
|
|
#define PCL_CMD_STORED (0xb<<24)
|
|
|
|
|
#define PCL_CMD_STORE0 (0x5<<24)
|
|
|
|
|
#define PCL_CMD_STORE1 (0x6<<24)
|
|
|
|
|
#define PCL_CMD_COMPARE (0xe<<24)
|
|
|
|
|
#define PCL_CMD_SWAP_COMPARE (0xf<<24)
|
|
|
|
|
#define PCL_CMD_ADD (0xd<<24)
|
|
|
|
|
#define PCL_CMD_BRANCH (0x7<<24)
|
|
|
|
|
|
|
|
|
|
/* BRANCH condition codes */
|
|
|
|
|
#define PCL_COND_DMARDY_SET (0x1<<20)
|
|
|
|
|
#define PCL_COND_DMARDY_CLEAR (0x2<<20)
|
|
|
|
|
|
|
|
|
|
#define PCL_GEN_INTR (1<<19)
|
|
|
|
|
#define PCL_LAST_BUFF (1<<18)
|
|
|
|
|
#define PCL_LAST_CMD (PCL_LAST_BUFF)
|
|
|
|
|
#define PCL_WAITSTAT (1<<17)
|
|
|
|
|
#define PCL_BIGENDIAN (1<<16)
|
|
|
|
|
#define PCL_ISOMODE (1<<12)
|
|
|
|
|
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA0_PREV_PCL 0x100
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
#define DMA1_PREV_PCL 0x120
|
|
|
|
|
#define DMA2_PREV_PCL 0x140
|
|
|
|
|
#define DMA3_PREV_PCL 0x160
|
|
|
|
|
#define DMA4_PREV_PCL 0x180
|
|
|
|
|
#define DMA_PREV_PCL(chan) (DMA_BREG(DMA0_PREV_PCL, chan))
|
|
|
|
|
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA0_CURRENT_PCL 0x104
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
#define DMA1_CURRENT_PCL 0x124
|
|
|
|
|
#define DMA2_CURRENT_PCL 0x144
|
|
|
|
|
#define DMA3_CURRENT_PCL 0x164
|
|
|
|
|
#define DMA4_CURRENT_PCL 0x184
|
|
|
|
|
#define DMA_CURRENT_PCL(chan) (DMA_BREG(DMA0_CURRENT_PCL, chan))
|
|
|
|
|
|
|
|
|
|
#define DMA0_CHAN_STAT 0x10c
|
|
|
|
|
#define DMA1_CHAN_STAT 0x12c
|
|
|
|
|
#define DMA2_CHAN_STAT 0x14c
|
|
|
|
|
#define DMA3_CHAN_STAT 0x16c
|
|
|
|
|
#define DMA4_CHAN_STAT 0x18c
|
|
|
|
|
#define DMA_CHAN_STAT(chan) (DMA_BREG(DMA0_CHAN_STAT, chan))
|
|
|
|
|
/* CHAN_STATUS registers share bits */
|
|
|
|
|
#define DMA_CHAN_STAT_SELFID (1<<31)
|
|
|
|
|
#define DMA_CHAN_STAT_ISOPKT (1<<30)
|
|
|
|
|
#define DMA_CHAN_STAT_PCIERR (1<<29)
|
|
|
|
|
#define DMA_CHAN_STAT_PKTERR (1<<28)
|
|
|
|
|
#define DMA_CHAN_STAT_PKTCMPL (1<<27)
|
|
|
|
|
#define DMA_CHAN_STAT_SPECIALACK (1<<14)
|
|
|
|
|
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA0_CHAN_CTRL 0x110
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
#define DMA1_CHAN_CTRL 0x130
|
|
|
|
|
#define DMA2_CHAN_CTRL 0x150
|
|
|
|
|
#define DMA3_CHAN_CTRL 0x170
|
|
|
|
|
#define DMA4_CHAN_CTRL 0x190
|
|
|
|
|
#define DMA_CHAN_CTRL(chan) (DMA_BREG(DMA0_CHAN_CTRL, chan))
|
|
|
|
|
/* CHAN_CTRL registers share bits */
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA_CHAN_CTRL_ENABLE (1<<31)
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
#define DMA_CHAN_CTRL_BUSY (1<<30)
|
|
|
|
|
#define DMA_CHAN_CTRL_LINK (1<<29)
|
|
|
|
|
|
|
|
|
|
#define DMA0_READY 0x114
|
|
|
|
|
#define DMA1_READY 0x134
|
|
|
|
|
#define DMA2_READY 0x154
|
|
|
|
|
#define DMA3_READY 0x174
|
|
|
|
|
#define DMA4_READY 0x194
|
|
|
|
|
#define DMA_READY(chan) (DMA_BREG(DMA0_READY, chan))
|
|
|
|
|
|
|
|
|
|
#define DMA_GLOBAL_REGISTER 0x908
|
|
|
|
|
|
|
|
|
|
#define FIFO_SIZES 0xa00
|
|
|
|
|
|
|
|
|
|
#define FIFO_CONTROL 0xa10
|
|
|
|
|
#define FIFO_CONTROL_GRF_FLUSH (1<<4)
|
|
|
|
|
#define FIFO_CONTROL_ITF_FLUSH (1<<3)
|
|
|
|
|
#define FIFO_CONTROL_ATF_FLUSH (1<<2)
|
|
|
|
|
|
|
|
|
|
#define FIFO_XMIT_THRESHOLD 0xa14
|
|
|
|
|
|
|
|
|
|
#define DMA0_WORD0_CMP_VALUE 0xb00
|
|
|
|
|
#define DMA1_WORD0_CMP_VALUE 0xb10
|
|
|
|
|
#define DMA2_WORD0_CMP_VALUE 0xb20
|
|
|
|
|
#define DMA3_WORD0_CMP_VALUE 0xb30
|
|
|
|
|
#define DMA4_WORD0_CMP_VALUE 0xb40
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA_WORD0_CMP_VALUE(chan) (DMA_SREG(DMA0_WORD0_CMP_VALUE, chan))
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
|
|
|
|
|
#define DMA0_WORD0_CMP_ENABLE 0xb04
|
|
|
|
|
#define DMA1_WORD0_CMP_ENABLE 0xb14
|
|
|
|
|
#define DMA2_WORD0_CMP_ENABLE 0xb24
|
|
|
|
|
#define DMA3_WORD0_CMP_ENABLE 0xb34
|
|
|
|
|
#define DMA4_WORD0_CMP_ENABLE 0xb44
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA_WORD0_CMP_ENABLE(chan) (DMA_SREG(DMA0_WORD0_CMP_ENABLE, chan))
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
|
|
|
|
|
#define DMA0_WORD1_CMP_VALUE 0xb08
|
|
|
|
|
#define DMA1_WORD1_CMP_VALUE 0xb18
|
|
|
|
|
#define DMA2_WORD1_CMP_VALUE 0xb28
|
|
|
|
|
#define DMA3_WORD1_CMP_VALUE 0xb38
|
|
|
|
|
#define DMA4_WORD1_CMP_VALUE 0xb48
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA_WORD1_CMP_VALUE(chan) (DMA_SREG(DMA0_WORD1_CMP_VALUE, chan))
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
|
|
|
|
|
#define DMA0_WORD1_CMP_ENABLE 0xb0c
|
|
|
|
|
#define DMA1_WORD1_CMP_ENABLE 0xb1c
|
|
|
|
|
#define DMA2_WORD1_CMP_ENABLE 0xb2c
|
|
|
|
|
#define DMA3_WORD1_CMP_ENABLE 0xb3c
|
|
|
|
|
#define DMA4_WORD1_CMP_ENABLE 0xb4c
|
2010-07-27 02:28:30 -06:00
|
|
|
#define DMA_WORD1_CMP_ENABLE(chan) (DMA_SREG(DMA0_WORD1_CMP_ENABLE, chan))
|
firewire: new driver: nosy - IEEE 1394 traffic sniffer
This adds the traffic sniffer driver for Texas Instruments PCILynx/
PCILynx2 based cards. The use cases for nosy are analysis of
nonstandard protocols and as an aid in development of drivers,
applications, or firmwares.
Author of the driver is Kristian Høgsberg. Known contributers are
Jody McIntyre and Jonathan Woithe.
Nosy programs PCILynx chips to operate in promiscuous mode, which is a
feature that is not found in OHCI-1394 controllers. Hence, only special
hardware as mentioned in the Kconfig help text is suitable for nosy.
This is only the kernelspace part of nosy. There is a userspace
interface to it, called nosy-dump, proposed to be added into the tools/
subdirectory of the kernel sources in a subsequent change. Kernelspace
and userspave component of nosy communicate via a 'misc' character
device file called /dev/nosy with a simple ioctl() and read() based
protocol, as described by nosy-user.h.
The files added here are taken from
git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
with the following changes by Stefan Richter:
- Kconfig and Makefile hunks are written from scratch.
- Commented out version printk in nosy.c.
- Included missing <linux/sched.h>, reported by Stephen Rothwell.
"git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:
Jonathan Woithe (2):
Nosy updates for recent kernels
Fix uninitialised memory (needed for 2.6.31 kernel)
Kristian Høgsberg (5):
Pull over nosy from mercurial repo.
Use a misc device instead.
Add simple AV/C decoder.
Don't break down on big payloads.
Set parent device for misc device.
As a low-level IEEE 1394 driver, its files are placed into
drivers/firewire/ although nosy is not part of the firewire driver
stack.
I am aware of the following literature from Texas Instruments about
PCILynx programming:
SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
Functional Specification
SLLA023 - Initialization and Asynchronous Programming of the
TSB12LV21A 1394 Device
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Kristian Høgsberg <krh@bitplanet.net>
2010-07-27 02:26:33 -06:00
|
|
|
/* word 1 compare enable flags */
|
|
|
|
|
#define DMA_WORD1_CMP_MATCH_OTHERBUS (1<<15)
|
|
|
|
|
#define DMA_WORD1_CMP_MATCH_BROADCAST (1<<14)
|
|
|
|
|
#define DMA_WORD1_CMP_MATCH_BUS_BCAST (1<<13)
|
|
|
|
|
#define DMA_WORD1_CMP_MATCH_LOCAL_NODE (1<<12)
|
|
|
|
|
#define DMA_WORD1_CMP_MATCH_EXACT (1<<11)
|
|
|
|
|
#define DMA_WORD1_CMP_ENABLE_SELF_ID (1<<10)
|
|
|
|
|
#define DMA_WORD1_CMP_ENABLE_MASTER (1<<8)
|
|
|
|
|
|
|
|
|
|
#define LINK_ID 0xf00
|
|
|
|
|
#define LINK_ID_BUS(id) (id<<22)
|
|
|
|
|
#define LINK_ID_NODE(id) (id<<16)
|
|
|
|
|
|
|
|
|
|
#define LINK_CONTROL 0xf04
|
|
|
|
|
#define LINK_CONTROL_BUSY (1<<29)
|
|
|
|
|
#define LINK_CONTROL_TX_ISO_EN (1<<26)
|
|
|
|
|
#define LINK_CONTROL_RX_ISO_EN (1<<25)
|
|
|
|
|
#define LINK_CONTROL_TX_ASYNC_EN (1<<24)
|
|
|
|
|
#define LINK_CONTROL_RX_ASYNC_EN (1<<23)
|
|
|
|
|
#define LINK_CONTROL_RESET_TX (1<<21)
|
|
|
|
|
#define LINK_CONTROL_RESET_RX (1<<20)
|
|
|
|
|
#define LINK_CONTROL_CYCMASTER (1<<11)
|
|
|
|
|
#define LINK_CONTROL_CYCSOURCE (1<<10)
|
|
|
|
|
#define LINK_CONTROL_CYCTIMEREN (1<<9)
|
|
|
|
|
#define LINK_CONTROL_RCV_CMP_VALID (1<<7)
|
|
|
|
|
#define LINK_CONTROL_SNOOP_ENABLE (1<<6)
|
|
|
|
|
|
|
|
|
|
#define CYCLE_TIMER 0xf08
|
|
|
|
|
|
|
|
|
|
#define LINK_PHY 0xf0c
|
|
|
|
|
#define LINK_PHY_READ (1<<31)
|
|
|
|
|
#define LINK_PHY_WRITE (1<<30)
|
|
|
|
|
#define LINK_PHY_ADDR(addr) (addr<<24)
|
|
|
|
|
#define LINK_PHY_WDATA(data) (data<<16)
|
|
|
|
|
#define LINK_PHY_RADDR(addr) (addr<<8)
|
|
|
|
|
|
|
|
|
|
#define LINK_INT_STATUS 0xf14
|
|
|
|
|
#define LINK_INT_ENABLE 0xf18
|
|
|
|
|
/* status and enable have identical bit numbers */
|
|
|
|
|
#define LINK_INT_LINK_INT (1<<31)
|
|
|
|
|
#define LINK_INT_PHY_TIME_OUT (1<<30)
|
|
|
|
|
#define LINK_INT_PHY_REG_RCVD (1<<29)
|
|
|
|
|
#define LINK_INT_PHY_BUSRESET (1<<28)
|
|
|
|
|
#define LINK_INT_TX_RDY (1<<26)
|
|
|
|
|
#define LINK_INT_RX_DATA_RDY (1<<25)
|
|
|
|
|
#define LINK_INT_IT_STUCK (1<<20)
|
|
|
|
|
#define LINK_INT_AT_STUCK (1<<19)
|
|
|
|
|
#define LINK_INT_SNTRJ (1<<17)
|
|
|
|
|
#define LINK_INT_HDR_ERR (1<<16)
|
|
|
|
|
#define LINK_INT_TC_ERR (1<<15)
|
|
|
|
|
#define LINK_INT_CYC_SEC (1<<11)
|
|
|
|
|
#define LINK_INT_CYC_STRT (1<<10)
|
|
|
|
|
#define LINK_INT_CYC_DONE (1<<9)
|
|
|
|
|
#define LINK_INT_CYC_PEND (1<<8)
|
|
|
|
|
#define LINK_INT_CYC_LOST (1<<7)
|
|
|
|
|
#define LINK_INT_CYC_ARB_FAILED (1<<6)
|
|
|
|
|
#define LINK_INT_GRF_OVER_FLOW (1<<5)
|
|
|
|
|
#define LINK_INT_ITF_UNDER_FLOW (1<<4)
|
|
|
|
|
#define LINK_INT_ATF_UNDER_FLOW (1<<3)
|
2010-07-27 02:28:30 -06:00
|
|
|
#define LINK_INT_IARB_FAILED (1<<0)
|