phosphor-bittware repository
Hello Patrick
Quoted 1 line · Ben_Pai at wistron.com
Could you please help to create a new repository for phosphor-bittware?
Out of curiousity for others who aren't aware of what 'bittware' is,
could you describe a little about this repository? It seems to be a
hardware vendor, so it would be interesting to know what the BMC will be
doing with it.
Examples:
* What is the overall purpose of the code in this repository?
* Is there an existing architecture that this code will be following
or is there some new design that you are persuing (and needs to be
document)?
* Are there existing phosphor-dbus-interfaces that you will be
implementing? Are there new dbus interfaces you are proposing to
implement the functionality you want from this repository?
--
I want to implement related functions for the bittware 250-SoC card.
For example: Sensor reading, VPD information, led control and Brick Protection mechanism.
We don't need to modify phosphor-dbus-interfaces.
Best Regards,
Ben
---------------------------------------------------------------------------------------------------------------------------------------------------------------
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or distribution of this email or the content of this email is strictly prohibited. If you are not the intended recipient, you may reply to the sender and should delete this e-mail immediately.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Hello Ben,
Quoted 3 lines · On Tue, May 12, 2020 at 09:09:50AM +0000, [email protected] wrote:
I want to implement related functions for the bittware 250-SoC card. For example: Sensor reading, VPD information, led control and Brick Protection mechanism.
I looked briefly at the datasheet for this hardware [1]. It appears to expose an SMBus interface for the features you mentioned. The most straight-forward way to get this implemented is to create a kernel driver for most of the features you mentioned. If you implement a driver for this hardware that interacts with the hwmon, eeprom, and LED/GPIO subsystems in the kernel(*), you'll be able to reuse a lot of existing OpenBMC functionality without rewriting any userspace code.
- Sensor
- Kernel: hwmon
- Userspace: phosphor-hwmon or dbus-sensors
- VPD
- Kernel: eeprom
- Userspace: entity-manager (I think)
- LED control
- Kernel: LED / GPIO
- Userspace: phosphor-led-manager
The only part that wouldn't be covered would be the "Brick Protection". We'd need to see some more information on how this is exposed but you might be able to work it into the existing phosphor-bmc-code-mgmt repository. For power supplies, they did create a separate repository (phosphor-psu-code-mgmt) but I think they relied on some kernel APIs for doing part of the work.
(*) Depending on how the bittware hardware is implemented at an SMBus
level you may end up with multiple smaller drivers (this is better). If there is a single SMBus address for all these functions, you'll likely end up with one big driver.
1. https://www.bittware.com/wp-content/uploads/datasheets/ds-250-soc.pdf
Signature · 1 line
Patrick Williams