1. 18 Nov, 2015 3 commits
    • Malcolm Priestley's avatar
      [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode · c9d57de6
      Malcolm Priestley authored
      When in FE_TUNE_MODE_ONESHOT the frontend must report
      the actual capabilities so user can take appropriate
      action.
      
      With frontends that can't do auto inversion this is done
      by dvb-core automatically so CAN_INVERSION_AUTO is valid.
      
      However, when in FE_TUNE_MODE_ONESHOT this is not true.
      
      So only set FE_CAN_INVERSION_AUTO in modes other than
      FE_TUNE_MODE_ONESHOT
      Signed-off-by: default avatarMalcolm Priestley <tvboxspy@gmail.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
      c9d57de6
    • Javier Martinez Canillas's avatar
      [media] s5c73m3: Export OF module alias information · f934a94b
      Javier Martinez Canillas authored
      The SPI core always reports the MODALIAS uevent as "spi:<modalias>"
      regardless of the mechanism that was used to register the device
      (i.e: OF or board code) and the table that is used later to match
      the driver with the device (i.e: SPI id table or OF match table).
      
      So drivers needs to export the SPI id table and this be built into
      the module or udev won't have the necessary information to autoload
      the needed driver module when the device is added.
      
      But this means that OF-only drivers needs to have both OF and SPI id
      tables that have to be kept in sync and also the dev node compatible
      manufacturer prefix is stripped when reporting the MODALIAS. Which can
      lead to issues if two vendors use the same SPI device name for example.
      
      To avoid the above, the SPI core behavior may be changed in the future
      to not require an SPI device table for OF-only drivers and report the
      OF module alias. So, it's better to also export the OF table even when
      is unused now to prevent breaking module loading when the core changes.
      Signed-off-by: default avatarJavier Martinez Canillas <javier@osg.samsung.com>
      Reviewed-by: default avatarAndrzej Hajda <a.hajda@samsung.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
      f934a94b
    • Nicholas Mc Guire's avatar
      [media] ddbridge: fix wait_event_timeout return handling · 4bdbcb31
      Nicholas Mc Guire authored
      API conformance testing for completions with coccinelle spatches are being
      used to locate API usage inconsistencies:
      ./drivers/media/pci/ddbridge/ddbridge-core.c:89
              incorrect check for negative return
      
      Return type of wait_event_timeout is signed long not int and the
      return type is >=0 always thus the negative check is unnecessary..
      As stat is used here exclusively its type is simply changed and the
      negative return check dropped.
      Signed-off-by: default avatarNicholas Mc Guire <hofrat@osadl.org>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
      4bdbcb31
  2. 17 Nov, 2015 37 commits