Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

avoid master/slave terminology #1013

Open
gen2thomas opened this issue Oct 25, 2023 · 1 comment
Open

avoid master/slave terminology #1013

gen2thomas opened this issue Oct 25, 2023 · 1 comment
Assignees
Labels
done on dev the feature or bug is solved on dev branch and wait for merge to release branch

Comments

@gen2thomas
Copy link
Collaborator

gen2thomas commented Oct 25, 2023

SPI: redefine signal names, see: https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names/

  • MOSI/MISO/SS --> SDO/SDI/CS
  • Master/Slave --> Controller/Peripheral
@gen2thomas
Copy link
Collaborator Author

gen2thomas commented Feb 13, 2024

Additionally:

  • same as above for usages in I2C, use "controller/target", following the NXP decision, i2c-bus.org
  • substitute wrong github-paths https://github.com/hybridgroup/gobot/<blob/tree>/master to the "release" path
  • master.go with manager.go, same for related types
  • search for remaining occurrences of "master" and replace e.g. by one of the following names:
    controller, default, director, host, initiator, leader, manager, primary, principal, root
  • search for remaining occurrences of "slave" and replace e.g. by one of the following names:
    agent, client, device, performer, peripheral, replica, responder, satellite, secondary, subordinate, worker

@gen2thomas gen2thomas self-assigned this Feb 13, 2024
@gen2thomas gen2thomas changed the title SPI: redefine signal names prevent master/slave terminology Feb 13, 2024
@gen2thomas gen2thomas changed the title prevent master/slave terminology avoid master/slave terminology Feb 13, 2024
@gen2thomas gen2thomas added the done on dev the feature or bug is solved on dev branch and wait for merge to release branch label Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done on dev the feature or bug is solved on dev branch and wait for merge to release branch
Projects
None yet
Development

No branches or pull requests

1 participant