28 Jul, 2010
1 commit
-
Smart Array controllers newer than the P600 do not honor the
PCI power state method of resetting the controllers. Instead,
in these cases we can get them to reset via the "doorbell" register.This escaped notice until we began using "performant" mode because
the fact that the controllers did not reset did not normally
impede subsequent operation, and so things generally appeared to
"work". Once the performant mode code was added, if the controller
does not reset, it remains in performant mode. The code immediately
after the reset presumes the controller is in "simple" mode
(which previously, it had remained in simple mode the whole time).
If the controller remains in performant mode any code which presumes
it is in simple mode will not work. So the reset needs to be fixed.Unfortunately there are some controllers which cannot be reset by
either method. (eg. p800). We detect these cases by noticing that
the controller seems to remain in performant mode even after a
reset has been attempted. In those case, we proceed anyway,
as if the reset has happened (and skip the step of waiting for
the controller to become ready -- which is expecting it to be in
"simple" mode.) To sum up, we try to do a better job of resetting
the controller if "reset_devices" is set, and if it doesn't work,
we print a message and try to continue anyway.Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley
02 May, 2010
1 commit
-
This patch removes unnecessary #define's from hpsa. The SCSI midlayer
handles all this for us.Signed-off-by: Mike Miller
Signed-off-by: James Bottomley
03 Mar, 2010
3 commits
-
Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley -
This uses the scatter-gather chaining feature of Smart Array
controllers. 32 scatter-gather elements are embedded in the
"command list", and the last element in the list may be marked
as a "chain pointer", and point to an additional block of
scatter gather elements. The precise number of scatter gather
elements supported is dependent on the particular kind of
Smart Array, and is determined at runtime by querying the
hardware.Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley -
Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley
18 Feb, 2010
3 commits
-
This is done by adding support for the so-called "performant mode"
(that's really what they called it). Smart Array controllers
have a mode which enables multiple command completions to be
delivered with a single interrupt, "performant" mode. We want to use
that mode, as some newer controllers will be requiring this mode.Signed-off-by: Don Brace
Signed-off-by: Stephen M. Cameron
Signed-off-by: Mike Miller
Signed-off-by: James Bottomley -
That is, use u64, u32, u16 and u8 rather than __u64, __u32, __u16 and __u8.
Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley -
Signed-off-by: Stephen M. Cameron
Signed-off-by: James Bottomley
10 Dec, 2009
1 commit
-
This driver supports a subset of HP Smart Array Controllers.
It is a SCSI alternative to the cciss driver.[akpm@linux-foundation.org: avoid helpful cleanup patches]
[achiang@hp.com: make device attrs static]
[akpm@linux-foundation.org: msleep() does set_current_state() itself]
Signed-off-by: Stephen M. Cameron
Signed-off-by: Mike Miller
Signed-off-by: Alex Chiang
Signed-off-by: Andrew Morton
Signed-off-by: James Bottomley