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

[Edgecore][AS9716]Provide psu_fan_dir sysfs #12016

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jostar-yang
Copy link
Contributor

Signed-off-by: jostar-yang jostar_yang@edge-core.com

Why I did it

  1. Provide psu_fan_dir sysfs from accton psu drv
  2. Modify accton_i2c_psu for PSU plug out and set 0 to all data
  3. port index start from 1

How I did it

  1. Modify acctonas9716_psu.c
  2. Modify accton_i2c_psu.c
  3. Modify port_config.ini

How to verify it

Test psu_fan_dir is correct for each PSU.
root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_fan_dir
F2B
root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_model_name
YESM1300AM-2A01P10
root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_serial_num
S0A000X601825000096

root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_model_name
FSH082-610G
root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_serial_num
FSH082191000048104
root@as9716-32d-1:/sys/bus/i2c/drivers/psu/10-0051# cat psu_fan_dir
F2B

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: jostar-yang <jostar_yang@edge-core.com>
@jostar-yang jostar-yang changed the title [Edge-Core][AS9716]Provide psu_fan_dir sysfs [Edgecore][AS9716]Provide psu_fan_dir sysfs Nov 24, 2022
@lguohan lguohan added the device label Sep 23, 2023
@jostar-yang
Copy link
Contributor Author

I see "device" label is added to this PR. What does it mean? Do we need to do something to let this PR can be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants