Merge branches 'x86/apic', 'x86/cpu', 'x86/fixmap', 'x86/mm', 'x86/sched',... (8b0e5860) · Commits · e / devices / android_kernel_oneplus_sm8150

Documentation/ABI/testing/sysfs-bus-pci

+43 −0

Original line number	Diff line number	Diff line
		What: /sys/bus/pci/drivers/.../bind
		Date: December 2003
		Contact: linux-pci@vger.kernel.org
		Description:
		Writing a device location to this file will cause
		the driver to attempt to bind to the device found at
		this location. This is useful for overriding default
		bindings. The format for the location is: DDDD:BB:DD.F.
		That is Domain:Bus:Device.Function and is the same as
		found in /sys/bus/pci/devices/. For example:
		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
		(Note: kernels before 2.6.28 may require echo -n).

		What: /sys/bus/pci/drivers/.../unbind
		Date: December 2003
		Contact: linux-pci@vger.kernel.org
		Description:
		Writing a device location to this file will cause the
		driver to attempt to unbind from the device found at
		this location. This may be useful when overriding default
		bindings. The format for the location is: DDDD:BB:DD.F.
		That is Domain:Bus:Device.Function and is the same as
		found in /sys/bus/pci/devices/. For example:
		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
		(Note: kernels before 2.6.28 may require echo -n).

		What: /sys/bus/pci/drivers/.../new_id
		Date: December 2003
		Contact: linux-pci@vger.kernel.org
		Description:
		Writing a device ID to this file will attempt to
		dynamically add a new device ID to a PCI device driver.
		This may allow the driver to support more hardware than
		was included in the driver's static device ID support
		table at compile time. The format for the device ID is:
		VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID,
		Device ID, Subsystem Vendor ID, Subsystem Device ID,
		Class, Class Mask, and Private Driver Data. The Vendor ID
		and Device ID fields are required, the rest are optional.
		Upon successfully adding an ID, the driver will probe
		for the device and attempt to bind to it. For example:
		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id

		What: /sys/bus/pci/devices/.../vpd
		Date: February 2008
		Contact: Ben Hutchings <bhutchings@solarflare.com>

Documentation/dvb/README.flexcop

deleted100644 → 0

+0 −205

Original line number	Diff line number	Diff line
		This README escorted the skystar2-driver rewriting procedure. It describes the
		state of the new flexcop-driver set and some internals are written down here
		too.

		This document hopefully describes things about the flexcop and its
		device-offsprings. Goal was to write an easy-to-write and easy-to-read set of
		drivers based on the skystar2.c and other information.

		Remark: flexcop-pci.c was a copy of skystar2.c, but every line has been
		touched and rewritten.

		History & News
		==============
		2005-04-01 - correct USB ISOC transfers (thanks to Vadim Catana)




		General coding processing
		=========================

		We should proceed as follows (as long as no one complains):

		0) Think before start writing code!

		1) rewriting the skystar2.c with the help of the flexcop register descriptions
		and splitting up the files to a pci-bus-part and a flexcop-part.
		The new driver will be called b2c2-flexcop-pci.ko/b2c2-flexcop-usb.ko for the
		device-specific part and b2c2-flexcop.ko for the common flexcop-functions.

		2) Search for errors in the leftover of flexcop-pci.c (compare with pluto2.c
		and other pci drivers)

		3) make some beautification (see 'Improvements when rewriting (refactoring) is
		done')

		4) Testing the new driver and maybe substitute the skystar2.c with it, to reach
		a wider tester audience.

		5) creating an usb-bus-part using the already written flexcop code for the pci
		card.

		Idea: create a kernel-object for the flexcop and export all important
		functions. This option saves kernel-memory, but maybe a lot of functions have
		to be exported to kernel namespace.


		Current situation
		=================

		0) Done :)
		1) Done (some minor issues left)
		2) Done
		3) Not ready yet, more information is necessary
		4) next to be done (see the table below)
		5) USB driver is working (yes, there are some minor issues)

		What seems to be ready?
		-----------------------

		1) Rewriting
		1a) i2c is cut off from the flexcop-pci.c and seems to work
		1b) moved tuner and demod stuff from flexcop-pci.c to flexcop-tuner-fe.c
		1c) moved lnb and diseqc stuff from flexcop-pci.c to flexcop-tuner-fe.c
		1e) eeprom (reading MAC address)
		1d) sram (no dynamic sll size detection (commented out) (using default as JJ told me))
		1f) misc. register accesses for reading parameters (e.g. resetting, revision)
		1g) pid/mac filter (flexcop-hw-filter.c)
		1i) dvb-stuff initialization in flexcop.c (done)
		1h) dma stuff (now just using the size-irq, instead of all-together, to be done)
		1j) remove flexcop initialization from flexcop-pci.c completely (done)
		1l) use a well working dma IRQ method (done, see 'Known bugs and problems and TODO')
		1k) cleanup flexcop-files (remove unused EXPORT_SYMBOLs, make static from
		non-static where possible, moved code to proper places)

		2) Search for errors in the leftover of flexcop-pci.c (partially done)
		5a) add MAC address reading
		5c) feeding of ISOC data to the software demux (format of the isochronous data
		and speed optimization, no real error) (thanks to Vadim Catana)

		What to do in the near future?
		--------------------------------------
		(no special order here)

		5) USB driver
		5b) optimize isoc-transfer (submitting/killing isoc URBs when transfer is starting)

		Testing changes
		---------------

		O = item is working
		P = item is partially working
		X = item is not working
		N = item does not apply here
		<empty field> = item need to be examined

		\| PCI \| USB
		item \| mt352 \| nxt2002 \| stv0299 \| mt312 \| mt352 \| nxt2002 \| stv0299 \| mt312
		-------+-------+---------+---------+-------+-------+---------+---------+-------
		1a) \| O \| \| \| \| N \| N \| N \| N
		1b) \| O \| \| \| \| \| \| O \|
		1c) \| N \| N \| \| \| N \| N \| O \|
		1d) \| O \| O
		1e) \| O \| O
		1f) \| P
		1g) \| O
		1h) \| P \|
		1i) \| O \| N
		1j) \| O \| N
		1l) \| O \| N
		2) \| O \| N
		5a) \| N \| O
		5b)* \| N \|
		5c) \| N \| O

		* - not done yet

		Known bugs and problems and TODO
		--------------------------------

		1g/h/l) when pid filtering is enabled on the pci card

		DMA usage currently:
		The DMA is splitted in 2 equal-sized subbuffers. The Flexcop writes to first
		address and triggers an IRQ when it's full and starts writing to the second
		address. When the second address is full, the IRQ is triggered again, and
		the flexcop writes to first address again, and so on.
		The buffersize of each address is currently 640*188 bytes.

		Problem is, when using hw-pid-filtering and doing some low-bandwidth
		operation (like scanning) the buffers won't be filled enough to trigger
		the IRQ. That's why:

		When PID filtering is activated, the timer IRQ is used. Every 1.97 ms the IRQ
		is triggered. Is the current write address of DMA1 different to the one
		during the last IRQ, then the data is passed to the demuxer.

		There is an additional DMA-IRQ-method: packet count IRQ. This isn't
		implemented correctly yet.

		The solution is to disable HW PID filtering, but I don't know how the DVB
		API software demux behaves on slow systems with 45MBit/s TS.

		Solved bugs :)
		--------------
		1g) pid-filtering (somehow pid index 4 and 5 (EMM_PID and ECM_PID) aren't
		working)
		SOLUTION: also index 0 was affected, because net_translation is done for
		these indexes by default

		5b) isochronous transfer does only work in the first attempt (for the Sky2PC
		USB, Air2PC is working) SOLUTION: the flexcop was going asleep and never really
		woke up again (don't know if this need fixes, see
		flexcop-fe-tuner.c:flexcop_sleep)

		NEWS: when the driver is loaded and unloaded and loaded again (w/o doing
		anything in the while the driver is loaded the first time), no transfers take
		place anymore.

		Improvements when rewriting (refactoring) is done
		=================================================

		- split sleeping of the flexcop (misc_204.ACPI3_sig = 1;) from lnb_control
		(enable sleeping for other demods than dvb-s)
		- add support for CableStar (stv0297 Microtune 203x/ALPS) (almost done, incompatibilities with the Nexus-CA)

		Debugging
		---------
		- add verbose debugging to skystar2.c (dump the reg_dw_data) and compare it
		with this flexcop, this is important, because i2c is now using the
		flexcop_ibi_value union from flexcop-reg.h (do you have a better idea for
		that, please tell us so).

		Everything which is identical in the following table, can be put into a common
		flexcop-module.

		PCI USB
		-------------------------------------------------------------------------------
		Different:
		Register access: accessing IO memory USB control message
		I2C bus: I2C bus of the FC USB control message
		Data transfer: DMA isochronous transfer
		EEPROM transfer: through i2c bus not clear yet

		Identical:
		Streaming: accessing registers
		PID Filtering: accessing registers
		Sram destinations: accessing registers
		Tuner/Demod: I2C bus
		DVB-stuff: can be written for common use

		Acknowledgements (just for the rewriting part)
		================

		Bjarne Steinsbo thought a lot in the first place of the pci part for this code
		sharing idea.

		Andreas Oberritter for providing a recent PCI initialization template
		(pluto2.c).

		Boleslaw Ciesielski for pointing out a problem with firmware loader.

		Vadim Catana for correcting the USB transfer.

		comments, critics and ideas to linux-dvb@linuxtv.org.

Documentation/dvb/technisat.txt

+20 −14

Original line number	Diff line number	Diff line
		How to set up the Technisat devices
		===================================
		How to set up the Technisat/B2C2 Flexcop devices
		================================================

		1) Find out what device you have
		================================
		@@ -16,54 +16,60 @@ DVB: registering frontend 0 (Conexant CX24123/CX24109)...

		If the Technisat is the only TV device in your box get rid of unnecessary modules and check this one:
		"Multimedia devices" => "Customise analog and hybrid tuner modules to build"
		In this directory uncheck every driver which is activated there.
		In this directory uncheck every driver which is activated there (except "Simple tuner support" for case 9 only).

		Then please activate:
		2a) Main module part:

		a.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters"
		b.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC PCI" in case of a PCI card OR
		b.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC PCI" in case of a PCI card
		OR
		c.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC USB" in case of an USB 1.1 adapter
		d.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Enable debug for the B2C2 FlexCop drivers"
		Notice: d.) is helpful for troubleshooting

		2b) Frontend module part:

		1.) Revision 2.3:
		1.) SkyStar DVB-S Revision 2.3:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink VP310/MT312/ZL10313 based"

		2.) Revision 2.6:
		2.) SkyStar DVB-S Revision 2.6:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0299 based"

		3.) Revision 2.7:
		3.) SkyStar DVB-S Revision 2.7:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "Samsung S5H1420 based"
		c.)"Multimedia devices" => "Customise DVB frontends" => "Integrant ITD1000 Zero IF tuner for DVB-S/DSS"
		d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller"

		4.) Revision 2.8:
		4.) SkyStar DVB-S Revision 2.8:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24113/CX24128 tuner for DVB-S/DSS"
		c.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24123 based"
		d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller"

		5.) DVB-T card:
		5.) AirStar DVB-T card:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink MT352 based"

		6.) DVB-C card:
		6.) CableStar DVB-C card:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0297 based"

		7.) ATSC card 1st generation:
		7.) AirStar ATSC card 1st generation:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "Broadcom BCM3510"

		8.) ATSC card 2nd generation:
		8.) AirStar ATSC card 2nd generation:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "NxtWave Communications NXT2002/NXT2004 based"
		c.)"Multimedia devices" => "Customise DVB frontends" => "LG Electronics LGDT3302/LGDT3303 based"
		c.)"Multimedia devices" => "Customise DVB frontends" => "Generic I2C PLL based tuners"

		Author: Uwe Bugla <uwe.bugla@gmx.de> December 2008
		9.) AirStar ATSC card 3rd generation:
		a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
		b.)"Multimedia devices" => "Customise DVB frontends" => "LG Electronics LGDT3302/LGDT3303 based"
		c.)"Multimedia devices" => "Customise analog and hybrid tuner modules to build" => "Simple tuner support"

		Author: Uwe Bugla <uwe.bugla@gmx.de> February 2009

Documentation/kernel-parameters.txt

+4 −2

Original line number	Diff line number	Diff line
		@@ -868,8 +868,10 @@ and is between 256 and 4096 characters. It is defined in the file
		icn= [HW,ISDN]
		Format: <io>[,<membase>[,<icn_id>[,<icn_id2>]]]

		ide= [HW] (E)IDE subsystem
		Format: ide=nodma or ide=doubler
		ide-core.nodma= [HW] (E)IDE subsystem
		Format: =0.0 to prevent dma on hda, =0.1 hdb =1.0 hdc
		.vlb_clock .pci_clock .noflush .noprobe .nowerr .cdrom
		.chs .ignore_cable are additional options
		See Documentation/ide/ide.txt.

		idebus= [HW] (E)IDE subsystem - VLB/PCI bus speed

Documentation/scsi/cxgb3i.txt

+5 −6

Original line number	Diff line number	Diff line
		@@ -4,7 +4,7 @@ Introduction
		============

		The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc.
		series of products) supports iSCSI acceleration and iSCSI Direct Data Placement
		series of products) support iSCSI acceleration and iSCSI Direct Data Placement
		(DDP) where the hardware handles the expensive byte touching operations, such
		as CRC computation and verification, and direct DMA to the final host memory
		destination:
		@@ -31,9 +31,9 @@ destination:
		the TCP segments onto the wire. It handles TCP retransmission if
		needed.

		On receving, S3 h/w recovers the iSCSI PDU by reassembling TCP
		On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
		segments, separating the header and data, calculating and verifying
		the digests, then forwards the header to the host. The payload data,
		the digests, then forwarding the header to the host. The payload data,
		if possible, will be directly placed into the pre-posted host DDP
		buffer. Otherwise, the payload data will be sent to the host too.

		@@ -68,9 +68,8 @@ The following steps need to be taken to accelerates the open-iscsi initiator:
		sure the ip address is unique in the network.

		3. edit /etc/iscsi/iscsid.conf
		The default setting for MaxRecvDataSegmentLength (131072) is too big,
		replace "node.conn[0].iscsi.MaxRecvDataSegmentLength" to be a value no
		bigger than 15360 (for example 8192):
		The default setting for MaxRecvDataSegmentLength (131072) is too big;
		replace with a value no bigger than 15360 (for example 8192):

		node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192