Lijian Zhao has uploaded a new change for review. ( https://review.coreboot.org/19684 )
Change subject: soc/intel/common: Add sanity check of PCR_BASE_ADDRESS
......................................................................
soc/intel/common: Add sanity check of PCR_BASE_ADDRESS
PCR_BASE_ADRESS may be zero if SOC Kconfig didn't define the non zero
default value.
TEST=Remove the PCR_BASE_ADDRESS config in Apollolake Kconfig file and
build.
BUG=None
Change-Id: I396aa1a3e89507c90e17229a986de5d2c0887c9c
Signed-off-by: Lijian Zhao <lijian.zhao(a)intel.com>
---
M src/soc/intel/common/block/pcr/pcr.c
1 file changed, 3 insertions(+), 0 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/84/19684/1
diff --git a/src/soc/intel/common/block/pcr/pcr.c b/src/soc/intel/common/block/pcr/pcr.c
index 6560a4b..ccd7d4d 100644
--- a/src/soc/intel/common/block/pcr/pcr.c
+++ b/src/soc/intel/common/block/pcr/pcr.c
@@ -24,6 +24,9 @@
/* Create an address based off of port id and offset. */
reg_addr = CONFIG_PCR_BASE_ADDRESS;
+ #if(CONFIG_PCR_BASE_ADDRESS ==0)
+ #error "PCR_BASE_ADDRESS need to be non-zero!"
+ #endif
reg_addr += ((uintptr_t)pid) << PCR_PORTID_SHIFT;
reg_addr += (uintptr_t)offset;
--
To view, visit https://review.coreboot.org/19684
To unsubscribe, visit https://review.coreboot.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: I396aa1a3e89507c90e17229a986de5d2c0887c9c
Gerrit-PatchSet: 1
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Owner: Lijian Zhao <lijian.zhao(a)intel.com>
Julius Werner has posted comments on this change. ( https://review.coreboot.org/19477 )
Change subject: rockchip/rk3399: Add MIPI driver
......................................................................
Patch Set 5:
(2 comments)
https://review.coreboot.org/#/c/19477/5/src/soc/rockchip/rk3399/mipi.c
File src/soc/rockchip/rk3399/mipi.c:
Line 429: mdelay(12);
...and, actually, when I'm looking at the kernel patch mentioned below more closely it does:
1. regulator enabling [already done for us by the time we reach this function]
2. several msleep(12) [presumably waiting for the regulators, we might be able to skip that here]
3. EXIT_SLEEP_MODE
4. msleep(120)
5. SET_DISPLAY_ON
[and that's it, I'm not sure where it does the VID_MODE... probably later]
So, are you sure that you really got the delays in the right place here? Should the msleep(120) be between EXIT_SLEEP_MODE and SET_DISPLAY_ON instead, maybe? Looks to me like either the kernel code or this patch is wrong.
Line 432: mdelay(120);
> Done
You said "Done" but you didn't really answer my question... that's really the more important part. We need to know what this number represents to be able to implement it in the right way.
In https://patchwork.kernel.org/patch/9642191/ it seems that this is called "T6"... is that a number from the panel datasheet? (I don't have one unfortunately...)
If this *is* panel dependent, then the number must be in devicetree.cb like all the other panel values. You'd need to add a new field for this to chip.h, then read that in display.c and pass it into this function as an additional parameter. (If, on the other hand, it is not panel dependent and would be the same for every panel on this SoC, it's okay to hardcode it.)
--
To view, visit https://review.coreboot.org/19477
To unsubscribe, visit https://review.coreboot.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I02475eefb187c619c614b1cd20e97074bc8d917f
Gerrit-PatchSet: 5
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Owner: nickey.yang(a)rock-chips.com
Gerrit-Reviewer: Julius Werner <jwerner(a)chromium.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: Sean Paul <seanpaul(a)chromium.org>
Gerrit-Reviewer: Shunqian Zheng <zhengsq(a)rock-chips.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Reviewer: nickey.yang(a)rock-chips.com
Gerrit-HasComments: Yes
Felix Held has posted comments on this change. ( https://review.coreboot.org/17669 )
Change subject: superio/fintek: Add support for Fintek F71889A.
......................................................................
Patch Set 9:
> or for that matter, why 0x07ff signifies one byte
the leftmost '1' bit says what the highest address is that can be assigned to a peripheral in the io space. the number of zeros from the right side says how much bytes are needed to be allocated for the peripheral; the zeros on the right are basically the address mask, that masks the 2^n bytes being reserved with N being the number of zeros.
Maybe have a look at the function pnp_get_ioresource in pnp_device.c and/or diagram in f71869ad/superio.c
--
To view, visit https://review.coreboot.org/17669
To unsubscribe, visit https://review.coreboot.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I91c60a3b48cd4872ae7a27de8f49faa40e877a27
Gerrit-PatchSet: 9
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Owner: Marty Plummer <ntzrmtthihu777(a)gmail.com>
Gerrit-Reviewer: Edward O'Callaghan <edward.ocallaghan(a)koparo.com>
Gerrit-Reviewer: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Reviewer: Idwer Vollering <vidwer(a)gmail.com>
Gerrit-Reviewer: Marty Plummer <ntzrmtthihu777(a)gmail.com>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-HasComments: No
Felix Held has posted comments on this change. ( https://review.coreboot.org/17669 )
Change subject: superio/fintek: Add support for Fintek F71889A.
......................................................................
Patch Set 9: Code-Review+1
(1 comment)
https://review.coreboot.org/#/c/17669/9/src/superio/fintek/f71889a/superio.c
File src/superio/fintek/f71889a/superio.c:
PS9, Line 57: 0x07f8
After thinking a bit about the problem here, I'd say that 0x7ff is still the better option here. Both options have their downsides.
The keyboard controller uses two addresses in the io space, 0x60 and 0x64. I have no idea what the reasons were behind this decision, but that's what we have to deal with.
If a system also has an embedded controller (EC), the EC uses the io addresses 0x62 and 0x66. Again, don't ask me who thought that this is a good idea.
In this SIO chip there is only one register for setting the base io address for the keyboard controller and the second address is automatically the address of the first one plus 4 bytes.
When using 0x7ff here, only the io space for the first register will be reserved. If someone maps another peripheral to the address 0x64, you might see some weird effects. So the developers have to make sure to use sane values here, but that's something I consider acceptable.
When using 0x7f8, the io space for bot keyboard controller registers is reserved, but (and that's the problem in systems that also have an EC) the range also covers the addresses of the EC, so that will probably fail. I didn't think about this when I recommended using 0x7f8 as a mask here.
So all in all I'd use 0x7ff here, since the side effects of this are less bad.
tl;dr: I'd use 0x7ff here
--
To view, visit https://review.coreboot.org/17669
To unsubscribe, visit https://review.coreboot.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I91c60a3b48cd4872ae7a27de8f49faa40e877a27
Gerrit-PatchSet: 9
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Owner: Marty Plummer <ntzrmtthihu777(a)gmail.com>
Gerrit-Reviewer: Edward O'Callaghan <edward.ocallaghan(a)koparo.com>
Gerrit-Reviewer: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Reviewer: Idwer Vollering <vidwer(a)gmail.com>
Gerrit-Reviewer: Marty Plummer <ntzrmtthihu777(a)gmail.com>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-HasComments: Yes
Martin Roth has posted comments on this change. ( https://review.coreboot.org/19682 )
Change subject: [RFC]mb/*/*: Remove rtc nvram configurable baud rate
......................................................................
Patch Set 4:
(1 comment)
I'm good with removing this. It seems like we'd generally want to use the fastest possible speed for the serial port anyway.
https://review.coreboot.org/#/c/19682/4/src/mainboard/via/epia-m700/driving…
File src/mainboard/via/epia-m700/driving_clk_phase_data.c:
Line 22
Unrelated?
--
To view, visit https://review.coreboot.org/19682
To unsubscribe, visit https://review.coreboot.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I71698d9b188eeac73670b18b757dff5fcea0df41
Gerrit-PatchSet: 4
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Owner: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-HasComments: Yes