History log of /openbsd-src/sys/arch/arm/cortex/files.cortex (Results 1 – 7 of 7)
Revision Date Author Comments
# 23a4b636 09-Jul-2018 patrick <patrick@openbsd.org>

Implement ampintcmsi(4) in ampintc(4) to support MSI. The GICv2M is an
extension to the GIC controller, which is represented as subnode in the
device tree. There can be multiple GICv2Ms, so it make

Implement ampintcmsi(4) in ampintc(4) to support MSI. The GICv2M is an
extension to the GIC controller, which is represented as subnode in the
device tree. There can be multiple GICv2Ms, so it makes sense to attach
those to ampintc(4) as some kind of simplebus. The GICv2M is simply an
interrupt generator that can be used by PCIe devices to ring the door
bell. There is no need for further configuration, we only need to find
out which SPIs we are allowed to use for MSI and to register an edge
triggered interrupt on a (randomly) allocated SPI.

Implement support for interrupt types. The GIC only seems to support
level triggered active-high or egdge triggered low-to-high interrupts.
We currently always configure them to be level triggered, which is a
sane default for most controllers. Since MSI interupts on the GIC are
edge triggered, we need to be able to parse the type information and to
configure the interrupt correspondingly.

ok kettenis@

show more ...


# 24e5cb75 10-Aug-2016 kettenis <kettenis@openbsd.org>

Dynamically attach agtimer(4). Since agtimer(4) also provides the delay()
function for platforms that have it, rework the code a bit such that it can
be used before agtimer(4) attaches. Introduce a

Dynamically attach agtimer(4). Since agtimer(4) also provides the delay()
function for platforms that have it, rework the code a bit such that it can
be used before agtimer(4) attaches. Introduce a new agtimer_init()
function that checks whether the CPU implements the Generic Timer feature
and switches to agtimer_delay() if that feature is present. Call this
function from the generic platform initialization code.

ok jsg@

show more ...


# 6fc522b1 04-Aug-2016 kettenis <kettenis@openbsd.org>

Dynamically attach ampintc(4) and make it register itself as an interrupt
controller. Switch all i.MX6 devices over to the new FDT-aware interrupt
establish API and enable imxgpc(4).

This may break

Dynamically attach ampintc(4) and make it register itself as an interrupt
controller. Switch all i.MX6 devices over to the new FDT-aware interrupt
establish API and enable imxgpc(4).

This may break other platforms that use ampintc(4) as their interrupt
controller. We will fix this as soon as possible by switching them over
to the new interrupt establish API as well.

This also removes the hack in fec(4) to avoid the gpio-based interrupt
workaround. This commit is an essential step on the road to fix that
issue properly.

ok patrick@, jsg@

show more ...


# 79645871 02-May-2016 patrick <patrick@openbsd.org>

Rework mainbus and implement simplebus to be able to span a tree-like
topology based on device tree information. Introduce a common attach
args structure to be used for all fdt-capable bus devices.

Rework mainbus and implement simplebus to be able to span a tree-like
topology based on device tree information. Introduce a common attach
args structure to be used for all fdt-capable bus devices.

ok jsg@ kettenis@

show more ...


# 466195a2 09-Sep-2013 patrick <patrick@openbsd.org>

Support for the ARM Generic Timer used in the Cortex-A7 and Cortex-A15.


# d1433e4a 02-May-2013 patrick <patrick@openbsd.org>

Add a driver for the secondary cache controller on the PandaBoard and
other ARM Cortex based boards. Disabled for now, until proper
secondary cache flushing is done where it's needed.

ok miod@


# 027018ef 01-May-2013 patrick <patrick@openbsd.org>

Add a cortex bus which represents the ARM MPCore Complex.
It will attach only to ARM Cortex A9 and A15 SoCs.
The generic interrupt controller and timer will attach to this bus,
later a secondary cach

Add a cortex bus which represents the ARM MPCore Complex.
It will attach only to ARM Cortex A9 and A15 SoCs.
The generic interrupt controller and timer will attach to this bus,
later a secondary cache controller can be added.
The base address for those controllers are figured out using
the periphbase register.

ok bmercer@

show more ...