- 30 Jan, 2013 8 commits
-
-
James Smart authored
Signed-off-by:
James Smart <james.smart@emulex.com> Signed-off-by:
James Bottomley <JBottomley@Parallels.com>
-
James Smart authored
Signed-off-by:
-
James Smart authored
Signed-off-by:
-
James Smart authored
Fixed no-context ABTS received on unsolicited receive queue failed with BA_RJT Signed-off-by:
-
James Smart authored
Removed use of NOP mailboxes for interrupt verification in pci_probe_one_s4 Signed-off-by:
-
James Smart authored
Signed-off-by:
-
James Smart authored
Signed-off-by:
-
James Smart authored
Signed-off-by:
-
- 29 Jan, 2013 32 commits
-
-
wenxiong@linux.vnet.ibm.com authored
This patch fixes the following sparse error: CHECK drivers/scsi/ipr.c spinlock.h:147:9: warning: context imbalance in 'ipr_reset_reload' - unexpected unlock Signed-off-by:
Wen Xiong <wenxiong@linux.vnet.ibm.com> Acked-by:
Brian King <brking@linux.vnet.ibm.com> Signed-off-by:
-
wenxiong@linux.vnet.ibm.com authored
Signed-off-by:
-
wenxiong@linux.vnet.ibm.com authored
This patch implements blk iopoll in ipr driver for performance improvement. Signed-off-by:
-
wenxiong@linux.vnet.ibm.com authored
This patch reduces lock contention while implementing distributed completion processing. Signed-off-by:
-
wenxiong@linux.vnet.ibm.com authored
The new generation IBM SAS Controllers will support MSI-X interrupts and Distributed Completion Processing features. This patch add these support in ipr device driver. Signed-off-by:
-
Brian King authored
The resource path as displayed by the ipr driver is the location string identifying a location on the SAS fabric. This patch adds the SCSI host number such that error logs can be more easily correlated in multiple adapter configurations. Signed-off-by:
-
Brian King authored
Reported-by:
Fengguang Wu <fengguang.wu@intel.com> Signed-off-by:
-
wenxiong@linux.vnet.ibm.com authored
Add the appropriate definitions and table entries for new adapter support. Signed-off-by:
-
Jesper Juhl authored
If kzalloc() or csio_hw_check_fwconfig() fail we may leave the csio_hw_flash_config() function without freeing allocated memory or firmware. This should take care of the leaks. Signed-off-by:
Jesper Juhl <jj@chaosbits.net> Acked-by:
Naresh Kumar Inna <naresh@chelsio.com> Signed-off-by:
-
Bhanu Prakash Gollapudi authored
Signed-off-by:
Bhanu Prakash Gollapudi <bprakash@broadcom.com> Signed-off-by:
-
Bhanu Prakash Gollapudi authored
Increase max_sectors from 512 to 1024 in order to support max IO size of 512KB. Signed-off-by:
-
Bhanu Prakash Gollapudi authored
Since the FW counters are 32-bit, accumulate the stats in the driver. [jejb: fix checkpatch warning] Signed-off-by:
-
Bhanu Prakash Gollapudi authored
We used to map doorbell register after FW enable request is complete. This causes a race condition when unsolicited event is received, and FW sends a CQE for it. Since the doorbell is not mapped, driver does not arm CQ, which means FW will not notify the driver for further CQ completions. To resolve this, map the doorbell between offload and enable, so that driver is ready to receive the unsolicited packets and arm the CQ as soon as FW enable is performed. Signed-off-by:
-
Bhanu Prakash Gollapudi authored
Moved the 'waiting for upload/offload completion' logic to respective functions as it is called in multiple places. Also this is done in preperation for the next patch. Signed-off-by:
-
Bhanu Prakash Gollapudi authored
Software FCoE target always advertises RETRY bit even when there are no tape LUNs behind the target. This causes the driver to enable FW support for sequence level error recovery and perform REC/SRR. This patch arrests the behavior by not enabling SLER feature for this target. Signed-off-by:
-
Julia Lawall authored
If the NULL test is necessary, the initialization involving a dereference of the tested value should be moved after the NULL test. The sematic patch that fixes this problem is as follows: (http://coccinelle.lip6.fr/) // <smpl> @@ type T; expression E; identifier i,fld; statement S; @@ - T i = E->fld; + T i; ... when != E when != i if (E == NULL) S + i = E->fld; // </smpl> Signed-off-by:
Julia Lawall <Julia.Lawall@lip6.fr> Signed-off-by:
-
Cyril Roelandt authored
These calls are followed by calls to memcpy() on the same memory area, so they can be safely removed. Signed-off-by:
Cyril Roelandt <tipecaml@gmail.com> Signed-off-by:
-
Sreekanth Reddy authored
This patch stops the driver to invoke kthread (which remove the dead ioc) for some time while EEH recovery has started. [thenzl: add a 'non_operational_loop' reset.] Signed-off-by:
Sreekanth Reddy <Sreekanth.Reddy@lsi.com> Signed-off-by:
Tomas Henzl <thenzl@redhat.com> Signed-off-by:
-
Wei Yongjun authored
The variable 'chain_flags' and 'phy_number' are initialized but never used otherwise, So remove those unused variables. Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Signed-off-by:
-
Sachin Kamat authored
linux/version.h is not necessary as detected by checkversion.pl script. Signed-off-by:
Sachin Kamat <sachin.kamat@linaro.org> Acked-by:
-
Tomas Henzl authored
The intention in bnx2i_send_fw_iscsi_init_msg was to zero out only the lower 32bits, but instead the whole mask64 is zeroed. This patch fixes it. Signed-off-by:
Eddie Wai <eddie.wai@broadcom.com> Signed-off-by:
-
Hiral Patel authored
Modified fnic driver to let hardware insert the COS value. Set bit in descriptor to 0 telling hardware to use its lif COS configurations to insert the COS value in the frames. Signed-off-by:
Narsimhulu Musini <nmusini@cisco.com> Signed-off-by:
Hiral Patel <hiralpat@cisco.com> Signed-off-by:
-
Hiral Patel authored
Updated MAINTAINERS list for fnic driver with appropriate names and email ids. Signed-off-by:
Brian Uchino <buchino@cisco.com> Signed-off-by:
-
Vijaya Mohan Guvva authored
Signed-off-by:
Vijaya Mohan Guvva <vmohan@brocade.com> Signed-off-by:
-
Dan Carpenter authored
ioc->diag_trigger_mpi is an SL_WH_MPI_TRIGGERS_T struct. There is a cut and paste error here and SL_WH_EVENT_TRIGGERS_T is used instead of SL_WH_MPI_TRIGGERS_T. Since the SL_WH_EVENT_TRIGGERS_T is smaller than SL_WH_MPI_TRIGGERS_T, it means we only clear part of the buffer. I've changed it to use sizeof(ioc->diag_trigger_mpi) which is a bit simpler. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Acked-by:
-
Wei Yongjun authored
This removes an open coded simple_open() function and replaces file operations references to the function with simple_open() instead. Signed-off-by:
-
Vikas Chaudhary authored
Signed-off-by:
Vikas Chaudhary <vikas.chaudhary@qlogic.com> Signed-off-by:
-
Manish Rangankar authored
Signed-off-by:
Manish Rangankar <manish.rangankar@qlogic.com> Signed-off-by:
-
Manish Rangankar authored
In qla4xxx_get_ep_fwdb(), dst_addr is of type struct sockaddr. We are copying sizeof(struct sockaddr_in6) bytes to dst_addr which is 12 bytes larger. This will cause memory corruption. So we change dst_addr to struct sockaddr_storage which is of 128 byte, large enough to hold sizeof(struct sockaddr_in6). Reported-by:
-
Harish Zunjarrao authored
Issue: Reset operation fails if port is in Link Down state Fix: Do not wait till HBA comes online after reset command is invoked. Signed-off-by:
Harish Zunjarrao <harish.zunjarrao@qlogic.com> Signed-off-by:
-
Vikas Chaudhary authored
Issue: Mailbox command timed out after switching from polling mode to interrupt mode. Events:- 1. Mailbox interrupts are disabled 2. FW generates AEN and at same time driver enables Mailbox Interrupt 3. Driver issues new mailbox to Firmware In above case driver will not get AEN interrupts generated by FW in step #2 as FW generated this AEN when interrupts are disabled. During the same time driver enabled the mailbox interrupt, so driver will not poll for interrupt. Driver will never process AENs generated in step #2 and issues new mailbox to FW, but now FW is not able to post mailbox completion as AENs generated before are not processed by driver. Fix: Enable Mailbox / AEN interrupts before initializing FW in case of ISP83XX. This will make sure we process all Mailbox and AENs in interrupt mode. Signed-off-by:
-
Bjorn Helgaas authored
The ROM address handling in gdth_init_pci() is useless and possibly dangerous. This patch removes it. "pci_resource_start(pdev, 8)" is not well-defined. PCI resources 0-5 are standard PCI BARs and 6 is the expansion ROM. Resource 8 is either an SR-IOV BAR (if CONFIG_PCI_IOV=y, resources 7-12 are SR-IOV BARs) or a bridge window (resources 7-10). The GDT device is neither an SR-IOV device nor a bridge, so in either case resource 8 should be zero since struct pci_dev is allocated with kzalloc(). It is illegal for a driver to write an arbitrary address to the ROM BAR because it has no way of knowing whether the ROM will conflict with another device. I think the only effect of the code being removed was to: 1) Enable the ROM at 0xFEFF0000 (possibly causing a conflict with another device) 2) Delay one millisecond 3) Write zero to the ROM BAR, disabling it I doubt the delay is needed, but I left it since it seems innocuous. Signed-off-by:Bjorn Helgaas <bhelgaas@google.com> Signed-off-by:
-
