Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi

    below.

    The block library can be found on GitHub:

    http://www.github.com/mikehollinger/ibmcapikv

    http://github.com/open-power/capiflash

CXL Flash Driver IOCTLs

          destroyed, the tokens are to be considered stale and subsequent

          usage will result in errors.

	- A valid adapter file descriptor (fd2 >= 0) is only returned on

	  the initial attach for a context. Subsequent attaches to an

	  existing context (DK_CXLFLASH_ATTACH_REUSE_CONTEXT flag present)

	  do not provide the adapter file descriptor as it was previously

	  made known to the application.

        - When a context is no longer needed, the user shall detach from

          the context via the DK_CXLFLASH_DETACH ioctl.

          the context via the DK_CXLFLASH_DETACH ioctl. When this ioctl

	  returns with a valid adapter file descriptor and the return flag

	  DK_CXLFLASH_APP_CLOSE_ADAP_FD is present, the application _must_

	  close the adapter file descriptor following a successful detach.

	- When this ioctl returns with a valid fd2 and the return flag

	  DK_CXLFLASH_APP_CLOSE_ADAP_FD is present, the application _must_

	  close fd2 in the following circumstances:

		+ Following a successful detach of the last user of the context

		+ Following a successful recovery on the context's original fd2

		+ In the child process of a fork(), following a clone ioctl,

		  on the fd2 associated with the source context

        - A close on fd2 will invalidate the tokens. This operation is not

          required by the user.

        - At any time, a close on fd2 will invalidate the tokens. Applications

	  should exercise caution to only close fd2 when appropriate (outlined

	  in the previous bullet) to avoid premature loss of I/O.

DK_CXLFLASH_USER_DIRECT

-----------------------

    success, all "tokens" which had been provided to the user from the

    DK_CXLFLASH_ATTACH onward are no longer valid.

    When the DK_CXLFLASH_APP_CLOSE_ADAP_FD flag was returned on a successful

    attach, the application _must_ close the fd2 associated with the context

    following the detach of the final user of the context.

DK_CXLFLASH_VLUN_CLONE

----------------------

    This ioctl is responsible for cloning a previously created

    support maintaining user space access to storage after a process

    forks. Upon success, the child process (which invoked the ioctl)

    will have access to the same LUNs via the same resource handle(s)

    and fd2 as the parent, but under a different context.

    as the parent, but under a different context.

    Context sharing across processes is not supported with CXL and

    therefore each fork must be met with establishing a new context

    translation tables are copied from the parent context to the child's

    and then synced with the AFU.

    When the DK_CXLFLASH_APP_CLOSE_ADAP_FD flag was returned on a successful

    attach, the application _must_ close the fd2 associated with the source

    context (still resident/accessible in the parent process) following the

    clone. This is to avoid a stale entry in the file descriptor table of the

    child process.

DK_CXLFLASH_VERIFY

------------------

    This ioctl is used to detect various changes such as the capacity of

    at which time the context/resources they held will be freed as part of

    the release fop.

    When the DK_CXLFLASH_APP_CLOSE_ADAP_FD flag was returned on a successful

    attach, the application _must_ unmap and close the fd2 associated with the

    original context following this ioctl returning success and indicating that

    the context was recovered (DK_CXLFLASH_RECOVER_AFU_CONTEXT_RESET).

DK_CXLFLASH_MANAGE_LUN

----------------------

    This ioctl is used to switch a LUN from a mode where it is available

	- HP Smart Array Controller SCSI driver.

hptiop.txt

	- HIGHPOINT ROCKETRAID 3xxx RAID DRIVER

in2000.txt

	- info on in2000 driver

libsas.txt

	- Serial Attached SCSI management layer.

link_power_management_policy.txt

README file for the Linux DTC3180/3280 scsi driver.

by Ray Van Tassle (rayvt@comm.mot.com)  March 1996

Based on the generic & core NCR5380 code by Drew Eckhard

SCSI device driver for the DTC 3180/3280.

Data Technology Corp---a division of Qume.

The 3280 has a standard floppy interface.

The 3180 does not.  Otherwise, they are identical.

The DTC3x80 does not support DMA but it does have Pseudo-DMA which is

supported by the driver.

Its DTC406 scsi chip is supposedly compatible with the NCR 53C400.

It is memory mapped, uses an IRQ, but no dma or io-port.  There is

internal DMA, between SCSI bus and an on-chip 128-byte buffer.  Double

buffering is done automagically by the chip.  Data is transferred

between the on-chip buffer and CPU/RAM via memory moves.

The driver detects the possible memory addresses (jumper selectable):

	CC00, DC00, C800, and D800

The possible IRQ's (jumper selectable) are:

	IRQ 10, 11, 12, 15

Parity is supported by the chip, but not by this driver.

Information can be obtained from /proc/scsi/dtc3c80/N.

Note on interrupts:

The documentation says that it can be set to interrupt whenever the

on-chip buffer needs CPU attention.  I couldn't get this to work.  So

the driver polls for data-ready in the pseudo-DMA transfer routine.

The interrupt support routines in the NCR3280.c core modules handle

scsi disconnect/reconnect, and this (mostly) works.  However.....  I

have tested it with 4 totally different hard drives (both SCSI-1 and

SCSI-2), and one CDROM drive.  Interrupts works great for all but one

specific hard drive.  For this one, the driver will eventually hang in

the transfer state.  I have tested with: "dd bs=4k count=2k

of=/dev/null if=/dev/sdb".  It reads ok for a while, then hangs.

After beating my head against this for a couple of weeks, getting

nowhere, I give up.  So.....This driver does NOT use interrupts, even

if you have the card jumpered to an IRQ.  Probably nobody will ever

care.

UPDATE NEWS: version 1.33 - 26 Aug 98

   Interrupt management in this driver has become, over

   time, increasingly odd and difficult to explain - this

   has been mostly due to my own mental inadequacies. In

   recent kernels, it has failed to function at all when

   compiled for SMP. I've fixed that problem, and after

   taking a fresh look at interrupts in general, greatly

   reduced the number of places where they're fiddled

   with. Done some heavy testing and it looks very good.

   The driver now makes use of the __initfunc() and

   __initdata macros to save about 4k of kernel memory.

   Once again, the same code works for both 2.0.xx and

   2.1.xx kernels.

UPDATE NEWS: version 1.32 - 28 Mar 98

   Removed the check for legal IN2000 hardware versions:

   It appears that the driver works fine with serial

   EPROMs (the 8-pin chip that defines hardware rev) as

   old as 2.1, so we'll assume that all cards are OK.

UPDATE NEWS: version 1.31 - 6 Jul 97

   Fixed a bug that caused incorrect SCSI status bytes to be

   returned from commands sent to LUNs greater than 0. This

   means that CDROM changers work now! Fixed a bug in the

   handling of command-line arguments when loaded as a module.

   Also put all the header data in in2000.h where it belongs.

   There are no longer any differences between this driver in

   the 2.1.xx source tree and the 2.0.xx tree, as of 2.0.31

   and 2.1.45 (or is it .46?) - this makes things much easier

   for me...

UPDATE NEWS: version 1.30 - 14 Oct 96

   Fixed a bug in the code that sets the transfer direction

   bit (DESTID_DPD in the WD_DESTINATION_ID register). There

   are quite a few SCSI commands that do a write-to-device;

   now we deal with all of them correctly. Thanks to Joerg

   Dorchain for catching this one.

UPDATE NEWS: version 1.29 - 24 Sep 96

   The memory-mapped hardware on the card is now accessed via

   the 'readb()' and 'readl()' macros - required by the new

   memory management scheme in the 2.1.x kernel series.

   As suggested by Andries Brouwer, 'bios_param()' no longer

   forces an artificial 1023 track limit on drives. Also

   removed some kludge-code left over from struggles with

   older (buggy) compilers.

UPDATE NEWS: version 1.28 - 07 May 96

   Tightened up the "interrupts enabled/disabled" discipline

   in 'in2000_queuecommand()' and maybe 1 or 2 other places.

   I _think_ it may have been a little too lax, causing an

   occasional crash during full moon. A fully functional

   /proc interface is now in place - if you want to play

   with it, start by doing 'cat /proc/scsi/in2000/0'. You

   can also use it to change a few run-time parameters on

   the fly, but it's mostly for debugging. The curious

   should take a good look at 'in2000_proc_info()' in the

   in2000.c file to get an understanding of what it's all

   about; I figure that people who are really into it will

   want to add features suited to their own needs...

   Also, sync is now DISABLED by default.

UPDATE NEWS: version 1.27 - 10 Apr 96

   Fixed a well-hidden bug in the adaptive-disconnect code

   that would show up every now and then during extreme

   heavy loads involving 2 or more simultaneously active

   devices. Thanks to Joe Mack for keeping my nose to the

   grindstone on this one.

UPDATE NEWS: version 1.26 - 07 Mar 96

   1.25 had a nasty bug that bit people with swap partitions

   and tape drives. Also, in my attempt to guess my way

   through Intel assembly language, I made an error in the

   inline code for IO writes. Made a few other changes and

   repairs - this version (fingers crossed) should work well.

UPDATE NEWS: version 1.25 - 05 Mar 96

   Kernel 1.3.70 interrupt mods added; old kernels still OK.

   Big help from Bill Earnest and David Willmore on speed

   testing and optimizing: I think there's a real improvement

   in this area.

   New! User-friendly command-line interface for LILO and

   module loading - the old method is gone, so you'll need

   to read the comments for 'setup_strings' near the top

   of in2000.c. For people with CDROM's or other devices

   that have a tough time with sync negotiation, you can

   now selectively disable sync on individual devices -

   search for the 'nosync' keyword in the command-line

   comments. Some of you disable the BIOS on the card, which

   caused the auto-detect function to fail; there is now a

   command-line option to force detection of a ROM-less card.

UPDATE NEWS: version 1.24a - 24 Feb 96

   There was a bug in the synchronous transfer code. Only

   a few people downloaded before I caught it - could have

   been worse.

UPDATE NEWS: version 1.24 - 23 Feb 96

   Lots of good changes. Advice from Bill Earnest resulted

   in much better detection of cards, more efficient usage

   of the fifo, and (hopefully) faster data transfers. The

   jury is still out on speed - I hope it's improved some.

   One nifty new feature is a cool way of doing disconnect/

   reselect. The driver defaults to what I'm calling

   'adaptive disconnect' - meaning that each command is

   evaluated individually as to whether or not it should be

   run with the option to disconnect/reselect (if the device

   chooses), or as a "SCSI-bus-hog". When several devices

   are operating simultaneously, disconnects are usually an

   advantage. In a single device system, or if only 1 device

   is being accessed, transfers usually go faster if disconnects

   are not allowed.

The default arguments (you get these when you don't give an 'in2000'

command-line argument, or you give a blank argument) will cause

the driver to do adaptive disconnect, synchronous transfers, and a

minimum of debug messages. If you want to fool with the options,

search for 'setup_strings' near the top of the in2000.c file and

check the 'hostdata->args' section in in2000.h - but be warned! Not

everything is working yet (some things will never work, probably).

I believe that disabling disconnects (DIS_NEVER) will allow you

to choose a LEVEL2 value higher than 'L2_BASIC', but I haven't

spent a lot of time testing this. You might try 'ENABLE_CLUSTERING'

to see what happens: my tests showed little difference either way.

There's also a define called 'DEFAULT_SX_PER'; this sets the data

transfer speed for the asynchronous mode. I've put it at 500 ns

despite the fact that the card could handle settings of 376 or

252, because higher speeds may be a problem with poor quality

cables or improper termination; 500 ns is a compromise. You can

choose your own default through the command-line with the

'period' keyword.

------------------------------------------------

***********  DIP switch settings  **************

------------------------------------------------

   sw1-1 sw1-2    BIOS address (hex)

   -----------------------------------------

    off   off     C8000 - CBFF0

    on    off     D8000 - DBFF0

    off   on      D0000 - D3FF0

    on    on      BIOS disabled

   sw1-3 sw1-4    IO port address (hex)

   ------------------------------------

    off   off     220 - 22F

    on    off     200 - 20F

    off   on      110 - 11F

    on    on      100 - 10F

   sw1-5 sw1-6 sw1-7    Interrupt

   ------------------------------

    off   off   off     15

    off   on    off     14

    off   off   on      11

    off   on    on      10

    on    -     -       disabled

   sw1-8 function depends on BIOS version. In earlier versions this

   controlled synchronous data transfer support for MSDOS:

      off = disabled

      on  = enabled

   In later ROMs (starting with 01.3 in April 1994) sw1-8 controls

   the "greater than 2 disk drive" feature that first appeared in

   MSDOS 5.0 (ignored by Linux):

      off = 2 drives maximum

      on  = 7 drives maximum

   sw1-9    Floppy controller

   --------------------------

    off     disabled

    on      enabled

------------------------------------------------

   I should mention that Drew Eckhardt's 'Generic NCR5380' sources

   were my main inspiration, with lots of reference to the IN2000

   driver currently distributed in the kernel source. I also owe

   much to a driver written by Hamish Macdonald for Linux-m68k(!).

   And to Eric Wright for being an ALPHA guinea pig. And to Bill

   Earnest for 2 tons of great input and information. And to David

   Willmore for extensive 'bonnie' testing. And to Joe Mack for

   continual testing and feedback.

            John Shifflett    jshiffle@netcom.com

			See drivers/scsi/BusLogic.c, comment before function

			BusLogic_ParseDriverOptions().

	dtc3181e=	[HW,SCSI]

			See Documentation/scsi/g_NCR5380.txt.

	eata=		[HW,SCSI]

	fdomain=	[HW,SCSI]

	gvp11=		[HW,SCSI]

	in2000=		[HW,SCSI]

			See header of drivers/scsi/in2000.c.

	ips=		[HW,SCSI] Adaptec / IBM ServeRAID controller

			See header of drivers/scsi/ips.c.

			Format: <buffer_size>,<write_threshold>

			See also Documentation/scsi/st.txt.

	pas16=		[HW,SCSI]

			See header of drivers/scsi/pas16.c.

	scsi_debug_*=	[SCSI]

			See drivers/scsi/scsi_debug.c.

	sym53c416=	[HW,SCSI]

			See header of drivers/scsi/sym53c416.c.

	t128=		[HW,SCSI]

			See header of drivers/scsi/t128.c.

	tmscsim=	[HW,SCSI]

			See comment before function dc390_setup() in

			drivers/scsi/tmscsim.c.

	u14-34f=	[HW,SCSI] UltraStor 14F/34F SCSI host adapter

			See header of drivers/scsi/u14-34f.c.

	wd33c93=	[HW,SCSI]

			See header of drivers/scsi/wd33c93.c.

	wd7000=		[HW,SCSI]

			See header of drivers/scsi/wd7000.c.