diff options
| author | Simon Glass <sjg@chromium.org> | 2020-07-16 21:22:30 -0600 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2020-07-17 14:32:24 +0800 |
| commit | b95611f67e709f8c98c1a31714dc941d436c0d5c (patch) | |
| tree | e83c7d924f0f22e3d2e5c4feee61442b0f23435c /drivers | |
| parent | a8c2789c09681660bfdbda489e504d12b0ab74b5 (diff) | |
| download | u-boot-b95611f67e709f8c98c1a31714dc941d436c0d5c.zip u-boot-b95611f67e709f8c98c1a31714dc941d436c0d5c.tar.gz u-boot-b95611f67e709f8c98c1a31714dc941d436c0d5c.tar.bz2 | |
x86: apl: Fix save/restore of ITSS priorities
The FSP-S changes the ITSS priorities. The code that tries to save it
before running FSP-S and restore it afterwards does not work as U-Boot
relocates in between the save and restore. This means that the driver
data saved before relocation is lost and the new driver just sees zeroes.
Fix this by allocating space in the relocated memory for the ITSS data.
Save it there and access it from the driver after relocation.
This fixes interrupt handling on coral.
Also drop the log_msg_ret() in irq_first_device_type() since this function
can be called speculatively in places where we are not sure if there is
an interrupt controller of that type. The resulting log errors are
confusing when there is no error.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/misc/irq-uclass.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/misc/irq-uclass.c b/drivers/misc/irq-uclass.c index 8727a33..94fa233 100644 --- a/drivers/misc/irq-uclass.c +++ b/drivers/misc/irq-uclass.c @@ -168,7 +168,7 @@ int irq_first_device_type(enum irq_dev_t type, struct udevice **devp) ret = uclass_first_device_drvdata(UCLASS_IRQ, type, devp); if (ret) - return log_msg_ret("find", ret); + return ret; return 0; } |