From: Leonid Moiseichuk <leonid.moiseichuk@gmail.com>
To: yuxiangl@marvell.com, James.Bottomley@suse.de
Cc: debian-kernel@lists.debian.org, linux-scsi@vger.kernel.org,
Leonid Moiseichuk <leonid.moiseichuk@gmail.com>
Subject: [PATCH] [SCSI] mvsas: generalize Marvell 88SE9485 declaration
Date: Sun, 3 Apr 2016 09:53:38 +0300 [thread overview]
Message-ID: <1459666418-8996-1-git-send-email-leonid.moiseichuk@gmail.com> (raw)
In case of specifying any subvendor has sense to use generic subdevice
and switch to PCI_VDEVICE() macro.
My ASUS P9A-I/C2550/SAS/4L publishes 1b4b:9485 as vendor-specific 1043:8635
and it prevents initialization of mvsas.
Signed-off-by: Leonid Moiseichuk <leonid.moiseichuk@gmail.com>
---
drivers/scsi/mvsas/mv_init.c | 19 +------------------
1 file changed, 1 insertion(+), 18 deletions(-)
diff --git a/drivers/scsi/mvsas/mv_init.c b/drivers/scsi/mvsas/mv_init.c
index c7c250519c4b..a6a4f09df0be 100644
--- a/drivers/scsi/mvsas/mv_init.c
+++ b/drivers/scsi/mvsas/mv_init.c
@@ -704,24 +704,7 @@ static struct pci_device_id mvs_pci_table[] = {
.class_mask = 0,
.driver_data = chip_9445,
},
- {
- .vendor = PCI_VENDOR_ID_MARVELL_EXT,
- .device = 0x9485,
- .subvendor = PCI_ANY_ID,
- .subdevice = 0x9480,
- .class = 0,
- .class_mask = 0,
- .driver_data = chip_9485,
- },
- {
- .vendor = PCI_VENDOR_ID_MARVELL_EXT,
- .device = 0x9485,
- .subvendor = PCI_ANY_ID,
- .subdevice = 0x9485,
- .class = 0,
- .class_mask = 0,
- .driver_data = chip_9485,
- },
+ { PCI_VDEVICE(MARVELL_EXT, 0x9485), chip_9485 },
{ PCI_VDEVICE(OCZ, 0x1021), chip_9485}, /* OCZ RevoDrive3 */
{ PCI_VDEVICE(OCZ, 0x1022), chip_9485}, /* OCZ RevoDrive3/zDriveR4 (exact model unknown) */
{ PCI_VDEVICE(OCZ, 0x1040), chip_9485}, /* OCZ RevoDrive3/zDriveR4 (exact model unknown) */
--
2.8.0.rc3
reply other threads:[~2016-04-03 6:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1459666418-8996-1-git-send-email-leonid.moiseichuk@gmail.com \
--to=leonid.moiseichuk@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=debian-kernel@lists.debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yuxiangl@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).