In summary, there is no easy way for device_* interface to know who called. So
registering a notification port is a simple and sane way, We only need to move
device_intr_register/ack to irq_register/ack into something like irq.defs, so
that other devices are freed from having to implement these
Junling Ma, le mar. 04 août 2020 14:47:09 -0700, a ecrit:
> The tot_num_intr field is a count of how many deliverable interrupts across
> all lines. When we move
> to the scheme of blocking read for request and write for acking, it is
> possible that an interrupt
> can happen during a small perio
Hi Jess,
> On Aug 4, 2020, at 3:22 PM, Jessica Clarke wrote:
>
> On 4 Aug 2020, at 22:47, Junling Ma wrote:
>>
>> The tot_num_intr field is a count of how many deliverable interrupts across
>> all lines. When we move
>> to the scheme of blocking read for request and write for acking, it is
>
On 4 Aug 2020, at 22:47, Junling Ma wrote:
>
> The tot_num_intr field is a count of how many deliverable interrupts across
> all lines. When we move
> to the scheme of blocking read for request and write for acking, it is
> possible that an interrupt
> can happen during a small period that the
The tot_num_intr field is a count of how many deliverable interrupts across all
lines. When we move
to the scheme of blocking read for request and write for acking, it is possible
that an interrupt
can happen during a small period that the interrupt is acked, but the read has
not happended yet.
