i2c-boardinfo.c 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. /*
  2. * i2c-boardinfo.h - collect pre-declarations of I2C devices
  3. *
  4. * This program is free software; you can redistribute it and/or modify
  5. * it under the terms of the GNU General Public License as published by
  6. * the Free Software Foundation; either version 2 of the License, or
  7. * (at your option) any later version.
  8. *
  9. * This program is distributed in the hope that it will be useful,
  10. * but WITHOUT ANY WARRANTY; without even the implied warranty of
  11. * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  12. * GNU General Public License for more details.
  13. *
  14. * You should have received a copy of the GNU General Public License
  15. * along with this program; if not, write to the Free Software
  16. * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
  17. */
  18. #include <linux/kernel.h>
  19. #include <linux/i2c.h>
  20. #include "i2c-core.h"
  21. /* These symbols are exported ONLY FOR the i2c core.
  22. * No other users will be supported.
  23. */
  24. DEFINE_MUTEX(__i2c_board_lock);
  25. EXPORT_SYMBOL_GPL(__i2c_board_lock);
  26. LIST_HEAD(__i2c_board_list);
  27. EXPORT_SYMBOL_GPL(__i2c_board_list);
  28. int __i2c_first_dynamic_bus_num;
  29. EXPORT_SYMBOL_GPL(__i2c_first_dynamic_bus_num);
  30. /**
  31. * i2c_register_board_info - statically declare I2C devices
  32. * @busnum: identifies the bus to which these devices belong
  33. * @info: vector of i2c device descriptors
  34. * @len: how many descriptors in the vector; may be zero to reserve
  35. * the specified bus number.
  36. *
  37. * Systems using the Linux I2C driver stack can declare tables of board info
  38. * while they initialize. This should be done in board-specific init code
  39. * near arch_initcall() time, or equivalent, before any I2C adapter driver is
  40. * registered. For example, mainboard init code could define several devices,
  41. * as could the init code for each daughtercard in a board stack.
  42. *
  43. * The I2C devices will be created later, after the adapter for the relevant
  44. * bus has been registered. After that moment, standard driver model tools
  45. * are used to bind "new style" I2C drivers to the devices. The bus number
  46. * for any device declared using this routine is not available for dynamic
  47. * allocation.
  48. *
  49. * The board info passed can safely be __initdata, but be careful of embedded
  50. * pointers (for platform_data, functions, etc) since that won't be copied.
  51. */
  52. int __init
  53. i2c_register_board_info(int busnum,
  54. struct i2c_board_info const *info, unsigned len)
  55. {
  56. int status;
  57. mutex_lock(&__i2c_board_lock);
  58. /* dynamic bus numbers will be assigned after the last static one */
  59. if (busnum >= __i2c_first_dynamic_bus_num)
  60. __i2c_first_dynamic_bus_num = busnum + 1;
  61. for (status = 0; len; len--, info++) {
  62. struct i2c_devinfo *devinfo;
  63. devinfo = kzalloc(sizeof(*devinfo), GFP_KERNEL);
  64. if (!devinfo) {
  65. pr_debug("i2c-core: can't register boardinfo!\n");
  66. status = -ENOMEM;
  67. break;
  68. }
  69. devinfo->busnum = busnum;
  70. devinfo->board_info = *info;
  71. list_add_tail(&devinfo->list, &__i2c_board_list);
  72. }
  73. mutex_unlock(&__i2c_board_lock);
  74. return status;
  75. }