1. 25 11月, 2016 1 次提交
    • P
      mfd: syscon: Support native-endian regmaps · d29ccdb3
      Paul Burton 提交于
      The regmap devicetree binding documentation states that a native-endian
      property should be supported as well as big-endian & little-endian,
      however syscon in its duplication of the parsing of these properties
      omits support for native-endian. Fix this by setting
      REGMAP_ENDIAN_NATIVE when a native-endian property is found.
      Signed-off-by: NPaul Burton <paul.burton@imgtec.com>
      Cc: Lee Jones <lee.jones@linaro.org>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: linux-mips@linux-mips.org
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      d29ccdb3
  2. 16 3月, 2016 2 次提交
  3. 11 1月, 2016 1 次提交
  4. 26 11月, 2014 1 次提交
    • P
      mfd: syscon: Decouple syscon interface from platform devices · bdb0066d
      Pankaj Dubey 提交于
      Currently a syscon entity can be only registered directly through a
      platform device that binds to a dedicated syscon driver. However in
      certain use cases it is desirable to make a device used with another
      driver a syscon interface provider.
      
      For example, certain SoCs (e.g. Exynos) contain system controller
      blocks which perform various functions such as power domain control,
      CPU power management, low power mode control, but in addition contain
      certain IP integration glue, such as various signal masks,
      coprocessor power control, etc. In such case, there is a need to have
      a dedicated driver for such system controller but also share registers
      with other drivers. The latter is where the syscon interface is helpful.
      
      In case of DT based platforms, this patch decouples syscon object from
      syscon platform driver, and allows to create syscon objects first time
      when it is required by calling of syscon_regmap_lookup_by APIs and keep
      a list of such syscon objects along with syscon provider device_nodes
      and regmap handles.
      
      For non-DT based platforms, this patch keeps syscon platform driver
      structure so that syscon can be probed and such non-DT based drivers
      can use syscon_regmap_lookup_by_pdev API and access regmap handles.
      Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based,
      we can completely remove platform driver of syscon, and keep only helper
      functions to get regmap handles.
      Suggested-by: NArnd Bergmann <arnd@arndb.de>
      Suggested-by: NTomasz Figa <tomasz.figa@gmail.com>
      Tested-by: NVivek Gautam <gautam.vivek@samsung.com>
      Tested-by: NJavier Martinez Canillas <javier.martinez@collabora.co.uk>
      Signed-off-by: NPankaj Dubey <pankaj.dubey@samsung.com>
      Reviewed-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NHeiko Stuebner <heiko@sntech.de>
      Reviewed-by: NHeiko Stuebner <heiko@sntech.de>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      bdb0066d
  5. 20 10月, 2014 1 次提交
  6. 03 6月, 2014 1 次提交
  7. 16 5月, 2014 1 次提交
  8. 19 3月, 2014 2 次提交
  9. 14 8月, 2013 1 次提交
  10. 31 7月, 2013 1 次提交
  11. 12 6月, 2013 1 次提交
  12. 10 4月, 2013 1 次提交
  13. 05 4月, 2013 2 次提交
  14. 14 2月, 2013 1 次提交
    • F
      mfd: syscon: Fix sparse warning · 75177dee
      Fabio Estevam 提交于
      Fix the following sparse warnings:
      
      drivers/mfd/syscon.c:40:15: warning: symbol 'syscon_node_to_regmap' was not declared. Should it be static?
      drivers/mfd/syscon.c:56:15: warning: symbol 'syscon_regmap_lookup_by_compatible' was not declared. Should it be static?
      drivers/mfd/syscon.c:72:15: warning: symbol 'syscon_regmap_lookup_by_phandle' was not declared. Should it be static?
      
      Cc: Dong Aisheng <dong.aisheng@linaro.org>
      Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      75177dee
  15. 29 11月, 2012 3 次提交
  16. 17 9月, 2012 1 次提交