Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 17 5月, 2013 1 次提交
  3. 16 5月, 2013 1 次提交
    • D
      mfd: tps65912: Select MFD_CORE · c972c128
      由 David Rientjes 提交于 
      CONFIG_MFD_CORE must be selected for TPS65912 to properly buid.
Otherwise it results in a link error:

	drivers/built-in.o: In function `tps65912_device_init':
	(.text+0x587e4): undefined reference to `mfd_add_devices'
	drivers/built-in.o: In function `tps65912_device_init':
	(.text+0x5884c): undefined reference to `mfd_remove_devices'
	drivers/built-in.o: In function `tps65912_device_exit':
	(.text+0x58878): undefined reference to `mfd_remove_devices'
Signed-off-by: NDavid Rientjes <rientjes@google.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      c972c128
  5. 20 4月, 2013 1 次提交
  7. 19 4月, 2013 1 次提交
  9. 17 4月, 2013 1 次提交
  11. 09 4月, 2013 4 次提交
  13. 06 4月, 2013 1 次提交
  15. 05 4月, 2013 5 次提交
  17. 31 3月, 2013 1 次提交
  19. 29 3月, 2013 1 次提交
  21. 27 3月, 2013 1 次提交
  23. 26 3月, 2013 1 次提交
  25. 12 3月, 2013 1 次提交
  27. 14 2月, 2013 1 次提交
  29. 22 1月, 2013 1 次提交
    • A
      mfd: tps65910: Select REGMAP_IRQ in Kconfig to fix build error · ee487114
      由 AnilKumar Ch 提交于 
      TPS65910 mfd driver uses functions that are only avaiable when
REGMAP_IRQ is enabled. So "select REGMAP_IRQ" is added to mfd
Kconfig to fix below build error:

drivers/built-in.o: In function `tps65910_irq_exit':
/media/anil/kernel/drivers/mfd/tps65910.c:265: undefined reference to `regmap_del_irq_chip'
drivers/built-in.o: In function `tps65910_irq_init':
/media/anil/kernel/drivers/mfd/tps65910.c:254: undefined reference to `regmap_add_irq_chip'
drivers/built-in.o: In function `tps65910_i2c_probe':
/media/anil/kernel/drivers/mfd/tps65910.c:509: undefined reference to `regmap_irq_get_domain'
make: *** [vmlinux] Error 1
Signed-off-by: NAnilKumar Ch <anilkumar@ti.com>
Tested-by: NMatt Porter <mporter@ti.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      ee487114
  31. 17 1月, 2013 1 次提交
  33. 09 12月, 2012 1 次提交
    • A
      mfd: tps80031: MFD_TPS80031 needs to select REGMAP_IRQ · c2ace4fd
      由 Axel Lin 提交于 
      This driver uses regmap_irq APIs, thus need to select REGMAP_IRQ.
IRQ_DOMAIN will be selected if select REGMAP_IRQ, thus remove it here.

This fixes below build errors:

drivers/built-in.o: In function `tps80031_remove':
drivers/mfd/tps80031.c:534: undefined reference to `regmap_del_irq_chip'
drivers/built-in.o: In function `tps80031_irq_init':
drivers/mfd/tps80031.c:305: undefined reference to `regmap_add_irq_chip'
drivers/built-in.o: In function `tps80031_probe':
drivers/mfd/tps80031.c:496: undefined reference to `regmap_irq_get_domain'
drivers/mfd/tps80031.c:512: undefined reference to `regmap_del_irq_chip'
make: *** [vmlinux] Error 1
Signed-off-by: NAxel Lin <axel.lin@ingics.com>
Acked-by: NLaxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      c2ace4fd
  35. 27 11月, 2012 1 次提交
    • A
      mfd: tps65090: MFD_TPS65090 needs to select REGMAP_IRQ · 64cdfe25
      由 Axel Lin 提交于 
      This fixes below build error:

drivers/built-in.o: In function `tps65090_i2c_probe':
drivers/mfd/tps65090.c:180: undefined reference to `regmap_add_irq_chip'
drivers/mfd/tps65090.c:190: undefined reference to `regmap_irq_chip_get_base'
drivers/mfd/tps65090.c:203: undefined reference to `regmap_del_irq_chip'
drivers/built-in.o: In function `tps65090_i2c_remove':
drivers/mfd/tps65090.c:213: undefined reference to `regmap_del_irq_chip'
make: *** [vmlinux] Error 1
Signed-off-by: NAxel Lin <axel.lin@ingics.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      64cdfe25
  37. 23 11月, 2012 1 次提交
  39. 21 11月, 2012 2 次提交
  41. 20 11月, 2012 2 次提交
  43. 16 11月, 2012 2 次提交
  45. 15 11月, 2012 1 次提交
    • L
      mfd: tps6586x: move regulator dt parsing to regulator driver · 64e48160
      由 Laxman Dewangan 提交于 
      Moving regulator node parsing to regulator driver in place
of parsing it on mfd driver.
The motivation for this change are:
- MFD core driver should not depends on regulator and able
  to instantiate device without regulator.
- The API for matching regulators are in regulator core and
  it is good that regulator driver only calls this API.
- Regulator specific support should be in regulator driver only
  to ease any enhancement/modification for regulators.
- The regulator driver is now registered as mfd sub device and
  all regulator registration is done from single probe call.
Signed-off-by: NLaxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      64e48160
  47. 14 11月, 2012 1 次提交
  49. 08 11月, 2012 2 次提交
  51. 06 11月, 2012 2 次提交
    • P
      mfd: ti_tscadc: Add support for TI's TSC/ADC MFDevice · 01636eb9
      由 Patil, Rachna 提交于 
      Add the mfd core driver which supports touchscreen
and ADC.
With this patch we are only adding infrastructure to
support the MFD clients.
Signed-off-by: NPatil, Rachna <rachna@ti.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      01636eb9
    • P
      mfd: Versatile Express config infrastructure · 3ecbf05b
      由 Pawel Moll 提交于 
      Versatile Express platform has an elaborated configuration system,
consisting of microcontrollers residing on the mother- and
daughterboards known as Motherboard/Daughterboard Configuration
Controller (MCC and DCC). The controllers are responsible for
the platform initialization (reset generation, flash programming,
FPGA bitfiles loading etc.) but also control clock generators,
voltage regulators, gather environmental data like temperature,
power consumption etc. Even the video output switch (FPGA) is
controlled that way.

Those devices are _not_ visible in the main address space and
the usual communication channel uses some kind of a bridge in
the peripheral block sending commands (requests) to the
controllers and receiving responses. It can take up to
500 microseconds for a transaction to be completed, therefore
it is important to provide a non-blocking interface to it.

This patch adds an abstraction of this infrastructure. Bridge
drivers can register themselves with the framework. Then,
a driver of a device can request an abstract "function" - the
request will be redirected to a bridge referred by thedd
"arm,vexpress,config-bridge" property of the device tree node.
Signed-off-by: NPawel Moll <pawel.moll@arm.com>
      3ecbf05b
  53. 01 10月, 2012 1 次提交
  55. 29 9月, 2012 1 次提交