Maulik V Vaghela has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vendorcode/google/chromesos/sar: Reduce severity of debug message ......................................................................
vendorcode/google/chromesos/sar: Reduce severity of debug message
Coreboot might not store wifi SAR values in VPD and may store it in CBFS. Logging the debug message with 'error' severity may interfere with automated test tool.
Lowering severity to BIOS_DEBUG to avoid this issue
BUG=b:171931401 BRANCH=None TEST=Severity of message is reduced and we don't see it as an error
Change-Id: I5c122a57cfe92b27e0291933618ca13d8e1889ba Signed-off-by: Maulik V Vaghela maulik.v.vaghela@intel.com --- M src/vendorcode/google/chromeos/sar.c 1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/42/47442/1
diff --git a/src/vendorcode/google/chromeos/sar.c b/src/vendorcode/google/chromeos/sar.c index 2f73d39..9bca423 100644 --- a/src/vendorcode/google/chromeos/sar.c +++ b/src/vendorcode/google/chromeos/sar.c @@ -71,7 +71,7 @@ /* Try to read the SAR limit entry from VPD */ if (!vpd_gets(wifi_sar_limit_key, wifi_sar_limit_str, buffer_size, VPD_RO_THEN_RW)) { - printk(BIOS_ERR, "Error: Could not locate '%s' in VPD.\n", + printk(BIOS_DEBUG, "Could not locate '%s' in VPD.\n", wifi_sar_limit_key);
if (!CONFIG(WIFI_SAR_CBFS))
Hello build bot (Jenkins),
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/47442
to look at the new patch set (#2).
Change subject: vendorcode/google/chromesos/sar: Reduce severity of debug message ......................................................................
vendorcode/google/chromesos/sar: Reduce severity of debug message
coreboot might not store wifi SAR values in VPD and may store it in CBFS. Logging the debug message with 'error' severity may interfere with automated test tool.
Lowering severity to BIOS_DEBUG to avoid this issue
BUG=b:171931401 BRANCH=None TEST=Severity of message is reduced and we don't see it as an error
Change-Id: I5c122a57cfe92b27e0291933618ca13d8e1889ba Signed-off-by: Maulik V Vaghela maulik.v.vaghela@intel.com --- M src/vendorcode/google/chromeos/sar.c 1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/42/47442/2
Paul Menzel has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vendorcode/google/chromesos/sar: Reduce severity of debug message ......................................................................
Patch Set 2:
(7 comments)
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG Commit Message:
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@7 PS2, Line 7: chromesos chromeos
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@7 PS2, Line 7: vendorcode/google/chromesos/sar: Reduce severity of debug message Maybe:
vc/google/chromeos/sar: Make SAR not found log a debug message
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@10 PS2, Line 10: debug message message
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: Lowering severity to BIOS_DEBUG to avoid this issue Please add a dot/period at the end.
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: to avoid avoids
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: BIOS_DEBUG Why not `BIOS_INFO`?
https://review.coreboot.org/c/coreboot/+/47442/2/src/vendorcode/google/chrom... File src/vendorcode/google/chromeos/sar.c:
https://review.coreboot.org/c/coreboot/+/47442/2/src/vendorcode/google/chrom... PS2, Line 71: /* Try to read the SAR limit entry from VPD */ It’d be great, if you could sent a follow-up updating this comment too.
Hello build bot (Jenkins), Justin TerAvest, Ronak Kanabar, Aamir Bohra, Karthik Ramasubramanian,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/47442
to look at the new patch set (#3).
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
vc/google/chromeos/sar: Make "SAR not found" log a debug message
coreboot might not store wifi SAR values in VPD and may store it in CBFS. Logging the message with 'error' severity may interfere with automated test tool.
Lowering severity to BIOS_DEBUG avoids this issue.
BUG=b:171931401 BRANCH=None TEST=Severity of message is reduced and we don't see it as an error
Change-Id: I5c122a57cfe92b27e0291933618ca13d8e1889ba Signed-off-by: Maulik V Vaghela maulik.v.vaghela@intel.com --- M src/vendorcode/google/chromeos/sar.c 1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/42/47442/3
Maulik V Vaghela has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
Patch Set 3:
(6 comments)
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG Commit Message:
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@7 PS2, Line 7: chromesos
chromeos
Done
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@7 PS2, Line 7: vendorcode/google/chromesos/sar: Reduce severity of debug message
Maybe: […]
Done
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@10 PS2, Line 10: debug message
message
Done
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: to avoid
avoids
Done
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: BIOS_DEBUG
Why not `BIOS_INFO`?
I wanted to keep it debug, in case there is genuine issue of VPD not found.
https://review.coreboot.org/c/coreboot/+/47442/2//COMMIT_MSG@13 PS2, Line 13: Lowering severity to BIOS_DEBUG to avoid this issue
Please add a dot/period at the end.
Done
Hello build bot (Jenkins), Justin TerAvest, Ronak Kanabar, Aamir Bohra, Karthik Ramasubramanian,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/47442
to look at the new patch set (#4).
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
vc/google/chromeos/sar: Make "SAR not found" log a debug message
coreboot might not store wifi SAR values in VPD and may store it in CBFS. Logging the message with 'error' severity may interfere with automated test tool.
Lowering severity to BIOS_DEBUG avoids this issue.
BUG=b:171931401 BRANCH=None TEST=Severity of message is reduced and we don't see it as an error
Change-Id: I5c122a57cfe92b27e0291933618ca13d8e1889ba Signed-off-by: Maulik V Vaghela maulik.v.vaghela@intel.com --- M src/drivers/wifi/generic/acpi.c M src/vendorcode/google/chromeos/sar.c 2 files changed, 2 insertions(+), 2 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/42/47442/4
Karthik Ramasubramanian has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
Patch Set 4: Code-Review+2
Furquan Shaikh has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
Patch Set 4:
(1 comment)
https://review.coreboot.org/c/coreboot/+/47442/4/src/vendorcode/google/chrom... File src/vendorcode/google/chromeos/sar.c:
https://review.coreboot.org/c/coreboot/+/47442/4/src/vendorcode/google/chrom... PS4, Line 71: /* Try to read the SAR limit entry from VPD */ Not for this change, but I think we should drop the support for SAR in VPD completely. This is not really recommended for any new platforms.
Maulik V Vaghela has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
Patch Set 4:
(1 comment)
https://review.coreboot.org/c/coreboot/+/47442/2/src/vendorcode/google/chrom... File src/vendorcode/google/chromeos/sar.c:
https://review.coreboot.org/c/coreboot/+/47442/2/src/vendorcode/google/chrom... PS2, Line 71: /* Try to read the SAR limit entry from VPD */
It’d be great, if you could sent a follow-up updating this comment too.
Ack
Subrata Banik has submitted this change. ( https://review.coreboot.org/c/coreboot/+/47442 )
Change subject: vc/google/chromeos/sar: Make "SAR not found" log a debug message ......................................................................
vc/google/chromeos/sar: Make "SAR not found" log a debug message
coreboot might not store wifi SAR values in VPD and may store it in CBFS. Logging the message with 'error' severity may interfere with automated test tool.
Lowering severity to BIOS_DEBUG avoids this issue.
BUG=b:171931401 BRANCH=None TEST=Severity of message is reduced and we don't see it as an error
Change-Id: I5c122a57cfe92b27e0291933618ca13d8e1889ba Signed-off-by: Maulik V Vaghela maulik.v.vaghela@intel.com Reviewed-on: https://review.coreboot.org/c/coreboot/+/47442 Tested-by: build bot (Jenkins) no-reply@coreboot.org Reviewed-by: Karthik Ramasubramanian kramasub@google.com --- M src/drivers/wifi/generic/acpi.c M src/vendorcode/google/chromeos/sar.c 2 files changed, 2 insertions(+), 2 deletions(-)
Approvals: build bot (Jenkins): Verified Karthik Ramasubramanian: Looks good to me, approved
diff --git a/src/drivers/wifi/generic/acpi.c b/src/drivers/wifi/generic/acpi.c index cd5af4e..4440b81 100644 --- a/src/drivers/wifi/generic/acpi.c +++ b/src/drivers/wifi/generic/acpi.c @@ -53,7 +53,7 @@
/* Retrieve the sar limits data */ if (get_wifi_sar_limits(&sar_limits) < 0) { - printk(BIOS_ERR, "Error: failed from getting SAR limits!\n"); + printk(BIOS_DEBUG, "failed from getting SAR limits!\n"); return; }
diff --git a/src/vendorcode/google/chromeos/sar.c b/src/vendorcode/google/chromeos/sar.c index 2f73d39..9bca423 100644 --- a/src/vendorcode/google/chromeos/sar.c +++ b/src/vendorcode/google/chromeos/sar.c @@ -71,7 +71,7 @@ /* Try to read the SAR limit entry from VPD */ if (!vpd_gets(wifi_sar_limit_key, wifi_sar_limit_str, buffer_size, VPD_RO_THEN_RW)) { - printk(BIOS_ERR, "Error: Could not locate '%s' in VPD.\n", + printk(BIOS_DEBUG, "Could not locate '%s' in VPD.\n", wifi_sar_limit_key);
if (!CONFIG(WIFI_SAR_CBFS))