Skip to content
Snippets Groups Projects
Select Git revision
20 results
Search by author
  • Any Author
  • Alessandro Pecugi Alessandro Pecugi alessandro.pecugi
  • Andrea Da Col Andrea Da Col andrea.dacol
  • Andrii Sosiuk Andrii Sosiuk andrii.sosiuk
  • Carlo Ferriolo Carlo Ferriolo carlo.ferriolo
  • Christian Stimming Christian Stimming christian.stimming
  • Christos Christos Karampeazis
  • CI Variables Management Service Account CI Variables Management Service Account service_account_ci_vars_management
  • Costanza Vasai Costanza Vasai costanza.vasai
  • Daniel Rinaldi Daniel Rinaldi daniel.rinaldi
  • Davide Cardillo Davide Cardillo davide.cardillo
  • Dietmar Muscholik Dietmar Muscholik dietmar.muscholik
  • Dmitry Petrov Dmitry Petrov dmitry.petrov
  • Elias Radi Elias Radi elias.radi
  • Ettore Chimenti Ettore Chimenti ektor5
  • Fabio Falsini Fabio Falsini fabio.falsini
  • Fabrizio Benvenuti Fabrizio Benvenuti fabrizio.benvenuti
  • Felix Gerking Felix Gerking felix.gerking
  • Gianfranco Mariotti Gianfranco Mariotti gianfranco.mariotti
  • GitBot GitBot gitbot
  • Git Bot Service Account Git Bot Service Account service_account_gitbot
20 authors
  1. Jul 11, 2018
  3. Apr 19, 2018
    • Michael Schmitz's avatar
      scsi: zorro_esp: New driver for Amiga Zorro NCR53C9x boards · 3109e5ae
      Michael Schmitz authored 
      
New combined SCSI driver for all ESP based Zorro SCSI boards for m68k Amiga.

Code largely based on board specific parts of the old drivers (blz1230.c,
blz2060.c, cyberstorm.c, cyberstormII.c, fastlane.c which were removed after
the 2.6 kernel series for lack of maintenance) with contributions by Tuomas
Vainikka (TCQ bug tests and workaround) and Finn Thain (TCQ bugfix by use of
PIO in extended message in transfer).

New Kconfig option and Makefile entries for new Amiga Zorro ESP SCSI driver
included in this patch.

Use DMA transfers wherever possible, with board-specific DMA set-up functions
copied from the old driver code. Three byte reselection messages do appear to
cause DMA timeouts. So wire up a PIO transfer routine for these
instead. esp_reselect_with_tag explicitly sets
esp->cmd_block_dma as target address for the message bytes but PIO
requires a virtual address.  Substiute kernel virtual address
esp->cmd_block in PIO transfer call if DMA address is esp->cmd_block_dma
and phase is message in.

PIO code taken from mac_esp.c where the reselection timeout issue was debugged
and fixed first, with minor macro and function rename.

Signed-off-by: default avatarMichael Schmitz <schmitzmic@gmail.com>
Reviewed-by: default avatarFinn Thain <fthain@telegraphics.com.au>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
Tested-by: default avatarChristian T. Steigies <cts@debian.org>
Tested-by: default avatarJohn Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      3109e5ae
  5. Mar 20, 2018
  7. Mar 15, 2018
  9. Feb 14, 2018
  11. Nov 02, 2017
    • Arnd Bergmann's avatar
      block: fix CDROM dependency on BLK_DEV · c091fbe9
      Arnd Bergmann authored 
      
After the cdrom cleanup, I get randconfig warnings for some configurations:

warning: (BLK_DEV_IDECD && BLK_DEV_SR) selects CDROM which has unmet direct dependencies (BLK_DEV)

This adds an explicit BLK_DEV dependency for both drivers. The other
drivers that select 'CDROM' already have this and don't need a change.

Fixes: 2a750166 ("block: Rework drivers/cdrom/Makefile")
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      c091fbe9
  13. Nov 01, 2017
  15. Oct 12, 2017
  17. Sep 05, 2017
    • Arnd Bergmann's avatar
      scsi: scsi_transport_sas: select BLK_DEV_BSGLIB · 580b71e9
      Arnd Bergmann authored 
      
Without CONFIG_BLK_DEV_BSGLIB, we get a link error here:

drivers/scsi/scsi_transport_sas.o: In function `sas_bsg_initialize':
scsi_transport_sas.c:(.text+0xcc0): undefined reference to `bsg_setup_queue'
scsi_transport_sas.c:(.text+0xd10): undefined reference to `bsg_setup_queue'
drivers/scsi/scsi_transport_sas.o: In function `sas_smp_dispatch':
scsi_transport_sas.c:(.text+0xe8c): undefined reference to `bsg_job_done'

This modifies the Kconfig 'select' statement accordingly, and matching
what we do for the other two scsi_transport implementations that use
bsglib.

Fixes: 651a0136 ("scsi: scsi_transport_sas: switch to bsg-lib for SMP passthrough")
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      580b71e9
  19. Aug 17, 2017
  21. Jul 25, 2017
  23. Jun 28, 2017
  25. Mar 15, 2017
    • James Smart's avatar
      scsi: lpfc: Finalize Kconfig options for nvme · 7d708033
      James Smart authored 
      
Reviewing the result of what was just added for Kconfig, we made a poor
choice. It worked well for full kernel builds, but not so much for how
it would be deployed on a distro.

Here's the final result:
- lpfc will compile in NVME initiator and/or NVME target support based
  on whether the kernel has the corresponding subsystem support.
  Kconfig is not used to drive this specifically for lpfc.
- There is a module parameter, lpfc_enable_fc4_type, that indicates
  whether the ports will do FCP-only or FCP & NVME (NVME-only not yet
  possible due to dependency on fc transport). As FCP & NVME divvys up
  exchange resources, and given NVME will not be often initially, the
  default is changed to FCP only.

Signed-off-by: default avatarDick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: default avatarJames Smart <james.smart@broadcom.com>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      7d708033
  27. Mar 07, 2017
  29. Feb 23, 2017
  31. Feb 22, 2017
  33. Jan 31, 2017
  35. Dec 14, 2016
  37. Nov 18, 2016
  39. Nov 08, 2016
  41. Sep 27, 2016
  43. Aug 12, 2016
  45. Jul 20, 2016
  47. Jul 13, 2016
    • Randy Dunlap's avatar
      scsi: ultrastor.c depends on ISA_DMA_API · 7e1ee441
      Randy Dunlap authored 
      
Fix build when CONFIG_ISA_DMA_API is not enabled. Fixes these build
errors (on x86_64):

../drivers/scsi/ultrastor.c: In function 'ultrastor_14f_detect':
../drivers/scsi/ultrastor.c:519:5: error: implicit declaration of function 'request_dma' [-Werror=implicit-function-declaration]
     if (config.dma_channel && request_dma(config.dma_channel,"Ultrastor")) {
     ^
../drivers/scsi/ultrastor.c: In function 'ultrastor_release':
../drivers/scsi/ultrastor.c:658:3: error: implicit declaration of function 'free_dma' [-Werror=implicit-function-declaration]
   free_dma(shost->dma_channel);
   ^

Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      7e1ee441
  49. Apr 15, 2016
  51. Apr 11, 2016
    • Finn Thain's avatar
      g_ncr5380: Remove CONFIG_SCSI_GENERIC_NCR53C400 · 9d376402
      Finn Thain authored 
      
This change brings a number of improvements: fewer macros, better test
coverage, simpler code and sane Kconfig options. The downside is a small
chance of incompatibility (which seems unavoidable).

CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA
transfers when the driver is used with 53C400-compatible cards. Thanks to
Ondrej Zary's patches, PDMA now works which means it can be enabled
unconditionally.

Due to bad design, CONFIG_SCSI_GENERIC_NCR53C400 ties together unrelated
functionality as it sets both PSEUDO_DMA and BIOSPARAM macros. This patch
effectively enables PSEUDO_DMA and disables BIOSPARAM.

The defconfigs and the Kconfig default leave CONFIG_SCSI_GENERIC_NCR53C400
undefined. Red Hat 9 and CentOS 2.1 were the same. This leaves both
PSEUDO_DMA and BIOSPARAM disabled. The effect of this patch should be
better performance from enabling PSEUDO_DMA.

On the other hand, Debian 4 and SLES 10 had CONFIG_SCSI_GENERIC_NCR53C400
enabled, so both PSEUDO_DMA and BIOSPARAM were enabled. This patch might
affect configurations like this by disabling BIOSPARAM. My best guess is
that this could be a problem only in the vanishingly rare case that
1) the CHS values stored in the boot device partition table are wrong and
2) a 5380 card is in use (because PDMA on 53C400 used to be broken).

Signed-off-by: default avatarFinn Thain <fthain@telegraphics.com.au>
Reviewed-by: default avatarHannes Reinecke <hare@suse.com>
Tested-by: default avatarOndrej Zary <linux@rainbow-software.org>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      9d376402
    • Rasmus Villemoes's avatar
      scsi: reduce CONFIG_SCSI_CONSTANTS=y impact by 8k · e1f0bce3
      Rasmus Villemoes authored 
      
On 64 bit, struct error_info has 6 bytes of padding, which amounts to
over 4k of wasted space in the additional[] array. We could easily get
rid of that by instead using separate arrays for the codes and the
pointers. However, we can do even better than that and save an
additional 6 bytes per entry: In the table, just store the sizeof()
the corresponding string literal. The cumulative sum of these is then
the appropriate offset into additional_text, which is built from the
concatenation (with '\0's inbetween) of the strings.

$ scripts/bloat-o-meter /tmp/vmlinux vmlinux
add/remove: 0/0 grow/shrink: 1/1 up/down: 24/-8488 (-8464)
function                                     old     new   delta
scsi_extd_sense_format                       136     160     +24
additional                                 11312    2824   -8488

The Kconfig help text used to say that CONFIG_SCSI_CONSTANTS=y costs
around 75 KB, but that was a little exaggerated. The actual number was
closer to 44K, and 36K with this patch.

Signed-off-by: default avatarRasmus Villemoes <linux@rasmusvillemoes.dk>
Reviewed-by: default avatarHannes Reinecke <hare@suse.com>
Tested-by: default avatarDouglas Gilbert <dgilbert@interlog.com>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      e1f0bce3
  53. Mar 05, 2016