i2c-howto.txt 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. How to port a serial driver to driver model
  2. ===========================================
  3. Over half of the I2C drivers have been converted as at November 2016. These
  4. ones remain:
  5. adi_i2c
  6. davinci_i2c
  7. fti2c010
  8. ihs_i2c
  9. kona_i2c
  10. lpc32xx_i2c
  11. pca9564_i2c
  12. ppc4xx_i2c
  13. rcar_i2c
  14. sh_i2c
  15. sh_sh7734_i2c
  16. soft_i2c
  17. tsi108_i2c
  18. zynq_i2c
  19. The deadline for this work is the end of June 2017. If no one steps
  20. forward to convert these, at some point there may come a patch to remove them!
  21. Here is a suggested approach for converting your I2C driver over to driver
  22. model. Please feel free to update this file with your ideas and suggestions.
  23. - #ifdef out all your own I2C driver code (#ifndef CONFIG_DM_I2C)
  24. - Define CONFIG_DM_I2C for your board, vendor or architecture
  25. - If the board does not already use driver model, you need CONFIG_DM also
  26. - Your board should then build, but will not work fully since there will be
  27. no I2C driver
  28. - Add the U_BOOT_DRIVER piece at the end (e.g. copy tegra_i2c.c for example)
  29. - Add a private struct for the driver data - avoid using static variables
  30. - Implement each of the driver methods, perhaps by calling your old methods
  31. - You may need to adjust the function parameters so that the old and new
  32. implementations can share most of the existing code
  33. - If you convert all existing users of the driver, remove the pre-driver-model
  34. code
  35. In terms of patches a conversion series typically has these patches:
  36. - clean up / prepare the driver for conversion
  37. - add driver model code
  38. - convert at least one existing board to use driver model serial
  39. - (if no boards remain that don't use driver model) remove the old code
  40. This may be a good time to move your board to use device tree also. Mostly
  41. this involves these steps:
  42. - define CONFIG_OF_CONTROL and CONFIG_OF_SEPARATE
  43. - add your device tree files to arch/<arch>/dts
  44. - update the Makefile there
  45. - Add stdout-path to your /chosen device tree node if it is not already there
  46. - build and get u-boot-dtb.bin so you can test it
  47. - Your drivers can now use device tree
  48. - For device tree in SPL, define CONFIG_SPL_OF_CONTROL