Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 064f4835e4f5e06cc88dec0c61b38a40273677fa
commit064f4835e4f5e06cc88dec0c61b38a40273677fa[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Thu Sep 16 18:15:03 2021 +0930
committerJoel Stanley <joel@jms.id.au>Thu Sep 16 18:15:04 2021 +0930
treeab4f1a75c6390db4394296b69c45790aa2fdf1b5
parent3370c7630d6e64dde53ea30fb4a89155f937ffa4 [diff]
linux-aspeed: AST2600 ADC, P10 GPIO, EEPROM and LED updates

The clk patch is a prerequisite for the backport of the ADC patches.

The ADC patches are not yet merged, but are under active review and are
expected to be merged in v5.16. Version 6 of the patchset was merged.

Billy Tsai (14):
      iio: adc: aspeed: set driver data when adc probe.
      dt-bindings: iio: adc: Add ast2600-adc bindings
      iio: adc: aspeed: completes the bitfield declare.
      iio: adc: aspeed: Keep model data to driver data.
      iio: adc: aspeed: Restructure the model data
      iio: adc: aspeed: Add vref config function
      iio: adc: aspeed: Use model_data to set clk scaler.
      iio: adc: aspeed: Use devm_add_action_or_reset.
      iio: adc: aspeed: Support ast2600 adc.
      iio: adc: aspeed: Fix the calculate error of clock.
      iio: adc: aspeed: Add func to set sampling rate.
      iio: adc: aspeed: Add compensation phase.
      iio: adc: aspeed: Support battery sensing.
      iio: adc: aspeed: Get and set trimming data.

Dmitry Baryshkov (1):
      clk: divider: add devm_clk_hw_register_divider

Eddie James (4):
      ARM: dts: aspeed: everest: Add I2C bus 15 muxes
      ARM: dts: aspeed: rainier: Add system LEDs
      ARM: dts: aspeed: rainier: Add eeprom on bus 12
      ARM: dts: aspeed: rainier: Remove gpio hog for GPIOP7

Joel Stanley (1):
      Revert "block: nbd: add sanity check for first_minor"

Michael Walle (1):
      clk: divider: add devm_clk_hw_register_divider_table()

Change-Id: I120d78fa77df01e239eeb67b3209cebfe2973491
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: ab4f1a75c6390db4394296b69c45790aa2fdf1b5
  1. .github/
  2. meta-alibaba/
  3. meta-amd/
  4. meta-ampere/
  5. meta-arm/
  6. meta-aspeed/
  7. meta-asrock/
  8. meta-bytedance/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-hxt/
  15. meta-ibm/
  16. meta-ingrasys/
  17. meta-inspur/
  18. meta-intel-openbmc/
  19. meta-inventec/
  20. meta-lenovo/
  21. meta-microsoft/
  22. meta-nuvoton/
  23. meta-openembedded/
  24. meta-openpower/
  25. meta-phosphor/
  26. meta-portwell/
  27. meta-qualcomm/
  28. meta-quanta/
  29. meta-raspberrypi/
  30. meta-security/
  31. meta-supermicro/
  32. meta-wistron/
  33. meta-x86/
  34. meta-xilinx/
  35. meta-yadro/
  36. poky/
  37. bitbake ⇨ poky/bitbake/
  38. LICENSE ⇨ poky/LICENSE
  39. meta ⇨ poky/meta
  40. meta-poky ⇨ poky/meta-poky/
  41. meta-skeleton ⇨ poky/meta-skeleton
  42. oe-init-build-env ⇨ poky/oe-init-build-env
  43. scripts ⇨ poky/scripts/
  44. .gitignore
  45. .gitreview
  46. .templateconf
  47. MAINTAINERS
  48. openbmc-env
  49. OWNERS
  50. README.md
  51. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 28
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
    rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         f0b                     fp5280g2
gsj                     hr630                   hr855xg2
lanyang                 mihawk                  msn
neptune                 nicole                  olympus
olympus-nuvoton         on5263m5                p10bmc
palmetto                qemuarm                 quanta-q71l
romulus                 s2600wf                 stardragon4800-rep2
swift                   tiogapass               vesnin
witherspoon             witherspoon-tacoma      yosemitev2
zaius

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing
  • User management
  • Virtual media

Features In Progress

  • OpenCompute Redfish Compliance
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm

Contact