Rename dbus_to_host_effecter* to dbus_to_terminus_effecter*

Some `dbus_to_host_effecter*` files still are not changed to
`dbus_to_terminus_effecter*` in commit `a34a64b: Support numeric
effecters in

Rename dbus_to_host_effecter* to dbus_to_terminus_effecter*

Some `dbus_to_host_effecter*` files still are not changed to
`dbus_to_terminus_effecter*` in commit `a34a64b: Support numeric
effecters in dbus-to-host-effecter`. Rename those files.

Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com>
Change-Id: I923083c5b1bda7b63969b28598189721a42899ad

show more ...

Fix spelling mistakes using codespell

This commit corrects various spelling mistakes throughout the
repository. The corrections were made automatically using `codespell`[1]
tool.

[1]: https://githu

Fix spelling mistakes using codespell

This commit corrects various spelling mistakes throughout the
repository. The corrections were made automatically using `codespell`[1]
tool.

[1]: https://github.com/codespell-project/codespell

Change-Id: I539a0c5baa63be240fc1c76367c0af338dd89c7b
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>

show more ...

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: I0d25f27a5e449578967915d9f570cc29246927d7
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Fix json files

I accidentally tested pldm with a json linter and found a lot
of json issues in pldm, this commit would try to fix all of them.

The issues that are fixed in this commit are
1. As per

Fix json files

I accidentally tested pldm with a json linter and found a lot
of json issues in pldm, this commit would try to fix all of them.

The issues that are fixed in this commit are
1. As per nlohmann json, it only support // & /**/ for comments
and those can be treated as spaces when we pass "true" for the
skipcomments argument for the json::parse() function. Most of
the places we used # for commenting.
2. RFC 7159 does not support hexadecimal numbers in json,so replacing
it with its decimal equivalent.

3. This commit also adds the configuration files for eslint json linting
as well the eslintignore configuration.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I909fae9ded93f47273276593fdf758449252f52f

show more ...

dos2unix conversion

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I78a4c2f28285ea30d66895b352402bfd12f95c00

pldm host-effecter transation: change enity type

The entity type 33 corresponds to Virtual Memory Manager.
Phyp will actually use value 32801 for entity type 33. This is
because the MSB will be set

pldm host-effecter transation: change enity type

The entity type 33 corresponds to Virtual Memory Manager.
Phyp will actually use value 32801 for entity type 33. This is
because the MSB will be set to indicate a virtual entity.

Change-Id: I573a08d5795bb00711e6597fd16bf946d26fde2f
Signed-off-by: Sampa Misra <sampmisr@in.ibm.com>

show more ...

Mechanism to associate sensor/effecter to FRU entity

The "entity_path" key is defined in PDR JSONs and will have an FRU D-Bus object
path as the value, if this is present, the entity type, instance,

Mechanism to associate sensor/effecter to FRU entity

The "entity_path" key is defined in PDR JSONs and will have an FRU D-Bus object
path as the value, if this is present, the entity type, instance, and container
id should be associate with the FRU entity.

Tested: test JSON with https://gist.github.com/lxwinspur/7225a9301ccfcbff1f6549203405b4fa
after executing the following command, get the entity information from FruHandler
entity_type = 120
entity_instance_num = 1
entity_container_id = 0

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I019f9a0b9d4dbec20a71dfd797f30ac8f57f67b8

show more ...

Add state sensor configuration to the sensor_pdr.json

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I239d482f95a66be711952e628ef0b0f27f78bdd7

pldmd: D-Bus to host effecter translation

This commit implements a mechanism to move the Host's boot state
from 'not started' to 'boot complete' by setting the relevant
Host effecter when the associ

pldmd: D-Bus to host effecter translation

This commit implements a mechanism to move the Host's boot state
from 'not started' to 'boot complete' by setting the relevant
Host effecter when the associated D-Bus property is set in the BMC.

Also added an example JSON to match D-Bus to host effecters

Change-Id: I41025d99d2b4b3452d4c51b03efe3750e159328b
Signed-off-by: Sampa Misra <sampmisr@in.ibm.com>

show more ...

fru: Fix typo in a json example

The root path of PIM is /xyz/openbmc_project/inventory

Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: I15fe343c2e9e49b756a8f7ff77fd34eb7ae62e95

pldm_events: Implement support for state sensorEvents

PLDM supports platform event message by which events can be generated
by a PLDM entity and can be processed by event receiver like BMC. This
pat

pldm_events: Implement support for state sensorEvents

PLDM supports platform event message by which events can be generated
by a PLDM entity and can be processed by event receiver like BMC. This
patch adds support for remote state sensors which sends PlatformEventMessage
command with sensorEvent type. The sensor is mapped to a D-Bus property
and the eventState is mapped to a D-Bus property value.

Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
Change-Id: I50dea23eccbdf29ad1b4cf2c9ab5700d74c12c68

show more ...

pldm: Add numeric effecter configuration to the effecter_pdr.json

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: Ic8ecd052001e52b855872c27e7e11f21679ddb7c
Signed-off-by: George Liu

pldm: Add numeric effecter configuration to the effecter_pdr.json

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: Ic8ecd052001e52b855872c27e7e11f21679ddb7c
Signed-off-by: George Liu <liuxiwei@inspur.com>

show more ...

pldm: rename state_effecter_pdr.json to effecter_pdr.json

state_effecter_pdr.json represents PDR state effecter, and the PDR
numeric effecter is added after it, so it is renamed effecter_pdr.json.

pldm: rename state_effecter_pdr.json to effecter_pdr.json

state_effecter_pdr.json represents PDR state effecter, and the PDR
numeric effecter is added after it, so it is renamed effecter_pdr.json.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ia6a1b54787cada3146dfc108874ea406d436c6f0

show more ...

Merge entity association PDRs

This commit enables merging entity association PDRs from the host into
the BMC's PDR repo. Entities from the host are inserted into the
appropriate location in the enti

Merge entity association PDRs

This commit enables merging entity association PDRs from the host into
the BMC's PDR repo. Entities from the host are inserted into the
appropriate location in the entity tree maintained by the BMC.

Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Change-Id: Ie9fa46d9f8512fad6c04069e4fc65785972fbf64

show more ...

docs: Update documentation for FRU_Master.json

Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
Change-Id: I0e9dba265e00f54342bd6e228f7b013135e6eb90

pdr: Update D-Bus mapping structure

For most PDR types, the D-Bus object structure(paths, interfaces, and
properties) should be defined in the JSON file instead of hard-coded.

Tested with JSON file

pdr: Update D-Bus mapping structure

For most PDR types, the D-Bus object structure(paths, interfaces, and
properties) should be defined in the JSON file instead of hard-coded.

Tested with JSON files:
https://gist.github.com/lxwinspur/2c3fd68cdb35e06480c4a5f7890e3a06#file-effecter_pdr-json.

pldmtool platform GetPDR -d 1
Encode request successfully
Request Message:
08 01 80 02 51 01 00 00 00 00 00 00 00 01 80 00 00 00
Success in creating the socket : RC = 3
Success in connecting to socket : RC = 0
Success in sending message type as pldm to mctp : RC = 0
Write to socket successful : RC = 18
Total length:18
Loopback response message:
08 01 80 02 51 01 00 00 00 00 00 00 00 01 80 00 00 00
On first recv(),response == request : RC = 0
Total length: 46
Shutdown Socket successful : RC = 0
Response Message:
08 01 00 02 51 00 02 00 00 00 00 00 00 00 01 1d 00 01 00 00 00 01 0b 00 00 13 00 00 00 01 00 21 00 00 00 00 00 00 00 00 00 01 c4 00 01 06
Parsed Response Msg:
nextRecordHandle: 2
responseCount: 29
recordHandle: 1
PDRHeaderVersion: 1
PDRType: 11
recordChangeNumber: 0
dataLength: 19
PLDMTerminusHandle: 0
effecterID: 1
entityType: 33
entityInstanceNumber: 0
containerID: 0
effecterSemanticID: 0
effecterInit: 0
effecterDescriptionPDR: false
compositeEffecterCount: 1
stateSetID: 196
possibleStatesSize: 1
possibleStates: 6

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ifc0cd1540b08e9b73e03d99d71a0980ef6353e72

show more ...

libpldmresponder: FRU: construct PDRs

Construct FRU record set and entity association PDRs for the FRUs for
which the BMC collects VPD (FRU information off of an EEPROM).

These PDRs are structured

libpldmresponder: FRU: construct PDRs

Construct FRU record set and entity association PDRs for the FRUs for
which the BMC collects VPD (FRU information off of an EEPROM).

These PDRs are structured as per PLDM spec DSP0248 v1.2.0.

Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Change-Id: I2c72d74dad449561b26c74482e00d1606546c5a2

show more ...

pldm: improve PDR config JSON files

Add the PDR type to the JOSN files so that the PDR type in the code is
unassociated with the JSON file name.
Rename 11.json become state_effecter_pdr.json.

Signe

pldm: improve PDR config JSON files

Add the PDR type to the JOSN files so that the PDR type in the code is
unassociated with the JSON file name.
Rename 11.json become state_effecter_pdr.json.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I3194989ecd80ea0d8befa91971bd58ff851dd375

show more ...

pldm_fru: Add example config JSON for PLDM FRU

Change-Id: Icb2cbe096b54eba5bdfa3411b6ac7cc0d84129b9
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>

bios: Define json structure for integer attribute

Define json structure for "Specific BIOS Attribute Table
Fields for BIOSInteger and BIOSIntegerReadOnly Types",
see DSP0247 Version 1.0.0 Table 9.

bios: Define json structure for integer attribute

Define json structure for "Specific BIOS Attribute Table
Fields for BIOSInteger and BIOSIntegerReadOnly Types",
see DSP0247 Version 1.0.0 Table 9.

In the json, VDD_AVSBUS_RAIL is an example for BIOSInteger
type and SBE_IMAGE_MINIMUM_VALID_ECS is an exmaple for
BIOSIntegerReadOnly Type

Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: I08190923df2c100062194ccb2e266407bc63ef31

show more ...

bios: fix bugs in PLDM BIOS

1. Correct json file example for enum type.
2. Enhance conditions for getBIOSAttributeValueTable.

Change-Id: Iba99a2aa0315623baeedec30170739030a6ebb4c
Signed-off-by: Car

bios: fix bugs in PLDM BIOS

1. Correct json file example for enum type.
2. Enhance conditions for getBIOSAttributeValueTable.

Change-Id: Iba99a2aa0315623baeedec30170739030a6ebb4c
Signed-off-by: Carol Wang <wangkair@cn.ibm.com>

show more ...

BIOS: Define JSON structure for BIOS String type

Give a sample of JSON configuration file for BIOS string type.
Take one entry for example:
{
"attribute_name" : "str_example1",

BIOS: Define JSON structure for BIOS String type

Give a sample of JSON configuration file for BIOS string type.
Take one entry for example:
{
"attribute_name" : "str_example1",
"string_type" : "ASCII",
"minimum_string_length" : 1,
"maximum_string_length" : 100,
"default_string_length" : 3,
"default_string" : "abc",
"dbus":
{
"object_path" : "/xyz/abc/def",
"interface" : "xyz.openbmc_project.str_example1.value",
"property_name" : "Str_example1",
"property_type" : "string"
}
}

Signed-off-by: Carol Wang <wangkair@cn.ibm.com>
Change-Id: I6217ddf75aa60dfb46e4384f81f2ff39c922d3bb

show more ...

Add APIs for parsing BIOS configuration JSON

1) Add API to get the BIOS strings from the JSON configuration files.
2) Add API to parse the config file and setup the lookup data structures
for the

Add APIs for parsing BIOS configuration JSON

1) Add API to get the BIOS strings from the JSON configuration files.
2) Add API to parse the config file and setup the lookup data structures
for the BIOS attribute table and BIOS attribute value table.
3) Add API to get the possible values and the default values for the BIOS
enumeration type.
4) Add API to get the current value of the BIOS enumeration attribute.
5) BIOS attributes can be configured by JSON configuration files which have
information to build the BIOS string table, attribute table and attribute
value table.

Change-Id: I747dd3cfc0801f8262ffafe2d516ae7f4ddeb7a2
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>

show more ...

Map state effecter id to D-Bus object path

Add a way to map state effecter ids to D-Bus object paths (multiple
paths in case the effecter is composite).

The mapping is specified in the state effect

Map state effecter id to D-Bus object path

Add a way to map state effecter ids to D-Bus object paths (multiple
paths in case the effecter is composite).

The mapping is specified in the state effecter PDR JSON (because the
mapping is system specific), and is stored in a map in memory. This will
be used by the get/set state effecter commands to route effecter ids to
D-Bus.

Change-Id: Ic79fae2445fd257302dd1298830f58b91fed9a1f
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

PDR: implement generation framework

This commit implements a framework that allows describing
platform/system specific PDR information in JSON files, which the PLDM
responder library parses and buil

PDR: implement generation framework

This commit implements a framework that allows describing
platform/system specific PDR information in JSON files, which the PLDM
responder library parses and builds a PDR out of.

Separate JSON files are expected per PDR type. This commit also adds the
code to build a state effecter PDR. PDR record handles are implemented
as incrementing indices, starting at 1, but this commit enables
implementing other type of record handles (for eg offset based).

This commit doesn't handle merging of PDRs received from other terminii,
so the PDR that's generated now is for the BMC. Merging of PDRs will be
implemented in future commits.

Change-Id: I005b08c5d29d12fc2459ca8d6e18547107a3da7d
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...