Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • early-display
  • variant-emmc-nvme-boot
  • 2023-01-25
  • v3
  • variant-emmc-nvme-boot
  • 2020-06-01
7 results

lpc32xx_i2c.c

Blame
  • Forked from Reform / reform-boundary-uboot
    Source project has a limited visibility.
    • Liam Beguin's avatar
      0f5b461b
      i2c: lpc32xx: Force consistent bus numbering · 0f5b461b
      Liam Beguin authored
      
      Normally, this would probably be done by adding devicetree aliases
      to the main dtsi file for the lpc32xx and using bus->req_seq instead.
      
      Since we want to have consistent i2c numbering, we cannot force the
      bus->req_seq because. If for instance we have 3 buses numbered
      from 0 to 2 with i2c0 enabled, i2c1 disabled and i2c2 enabled;
      i2c2 can be selected using 'i2c dev 1' and 'i2c dev 2' commands
      because a bus can be probed using req_seq or seq interchangeably.
      
      Signed-off-by: default avatarLiam Beguin <lbeguin@tycoint.com>
      Signed-off-by: default avatarSylvain Lemieux <slemieux@tycoint.com>
      0f5b461b
      History
      i2c: lpc32xx: Force consistent bus numbering
      Liam Beguin authored
      
      Normally, this would probably be done by adding devicetree aliases
      to the main dtsi file for the lpc32xx and using bus->req_seq instead.
      
      Since we want to have consistent i2c numbering, we cannot force the
      bus->req_seq because. If for instance we have 3 buses numbered
      from 0 to 2 with i2c0 enabled, i2c1 disabled and i2c2 enabled;
      i2c2 can be selected using 'i2c dev 1' and 'i2c dev 2' commands
      because a bus can be probed using req_seq or seq interchangeably.
      
      Signed-off-by: default avatarLiam Beguin <lbeguin@tycoint.com>
      Signed-off-by: default avatarSylvain Lemieux <slemieux@tycoint.com>