Searched hist:"70997 d88c40b4d74c4eac80c85f3a2676aa15d82" (Results 1 – 4 of 4) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/mach-bcm283x/ |
| H A D | msg.c | 70997d88c40b4d74c4eac80c85f3a2676aa15d82 Wed Apr 05 22:23:36 UTC 2017 Simon Glass <sjg@chromium.org> arm: rpi: Add a file to handle messages
The bcm283x chips provide a way for the ARM core to communicate with the
graphics processor, which is in charge of many things. This is handled by
way of a message prototcol.
At present the code for sending message (and receiving a reply) is spread
around U-Boot, primarily in the board file. This means that sending a
message from a driver requires duplicating the code.
Create a new message implementation with a function to support powering on
a subsystem as a starting point.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| H A D | Makefile | 70997d88c40b4d74c4eac80c85f3a2676aa15d82 Wed Apr 05 22:23:36 UTC 2017 Simon Glass <sjg@chromium.org> arm: rpi: Add a file to handle messages
The bcm283x chips provide a way for the ARM core to communicate with the
graphics processor, which is in charge of many things. This is handled by
way of a message prototcol.
At present the code for sending message (and receiving a reply) is spread
around U-Boot, primarily in the board file. This means that sending a
message from a driver requires duplicating the code.
Create a new message implementation with a function to support powering on
a subsystem as a starting point.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/arch/arm/mach-bcm283x/include/mach/ |
| H A D | msg.h | 70997d88c40b4d74c4eac80c85f3a2676aa15d82 Wed Apr 05 22:23:36 UTC 2017 Simon Glass <sjg@chromium.org> arm: rpi: Add a file to handle messages
The bcm283x chips provide a way for the ARM core to communicate with the
graphics processor, which is in charge of many things. This is handled by
way of a message prototcol.
At present the code for sending message (and receiving a reply) is spread
around U-Boot, primarily in the board file. This means that sending a
message from a driver requires duplicating the code.
Create a new message implementation with a function to support powering on
a subsystem as a starting point.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/board/raspberrypi/rpi/ |
| H A D | rpi.c | 70997d88c40b4d74c4eac80c85f3a2676aa15d82 Wed Apr 05 22:23:36 UTC 2017 Simon Glass <sjg@chromium.org> arm: rpi: Add a file to handle messages
The bcm283x chips provide a way for the ARM core to communicate with the
graphics processor, which is in charge of many things. This is handled by
way of a message prototcol.
At present the code for sending message (and receiving a reply) is spread
around U-Boot, primarily in the board file. This means that sending a
message from a driver requires duplicating the code.
Create a new message implementation with a function to support powering on
a subsystem as a starting point.
Signed-off-by: Simon Glass <sjg@chromium.org>
|