07 Feb, 2020
2 commits
-
At present driver model supports the IRQ uclass but there is no way to
request a particular interrupt for a driver.Add a mechanism, similar to clock and reset, to read the interrupts
required by a device from the device tree and to request those interrupts.U-Boot itself does not have interrupt-driven handlers, so just provide a
means to read and clear an interrupt. This can be useful to handle
peripherals which must use an interrupt to determine when data is
available, for example.Bring over the basic binding file as well, from Linux v5.4. Note that the
older binding is not supported in U-Boot; the newer 'special form' must be
used.Add a simple test of the new functionality.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng -
There can be different types of interrupt controllers in a system and some
drivers may need to distinguish between these. In general this can be
handled using the device tree by adding the interrupt information to
device nodes.However on x86 devices we have interrupt controllers which are not tied
to any particular device and not really used in U-Boot. These still need
to be inited, so a convenient method is to give each controller a type
and allow a particular controller type to be probed.Add support for this in sandbox along with a test.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
[bmeng: remove the new bland line at EOF of test/dm/irq.c]
Signed-off-by: Bin Meng
15 Dec, 2019
1 commit
-
Update this uclass to support the needs of the Apollo Lake ITSS. It
supports four operations.Move the uclass into a separate directory so that sandbox can use it too.
Add a new Kconfig to control it and enable this on x86.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng