Can't understand /proc/interrupts output for GICv3 case

[Ozgur Karatas]

On Mon, Apr 11, 2022 at 6:49 PM Greg KH <greg at kroah.com> wrote:

> On Mon, Apr 11, 2022 at 03:32:23PM +0100, Peter Maydell wrote:
> > On Mon, 11 Apr 2022 at 15:22, Chan Kim <ckim at etri.re.kr> wrote:
> > >
> > >
> > > > > > What bus type is your driver written for?
> > > > > >
> > > > > That sounds very logical. In my case I added it to system bus.
> > > >
> > > > What exactly do you mean by "system bus"?
> > > >
> > > I meant 'sysbus' in qemu code that I showed in the qemu code.
> > > And I think it's the CPU bus.
> >
> > The 'sysbus' is just QEMU's abstraction for "devices mapped into
> > memory at a fixed physical address", ie simple MMIO devices that
> > aren't on a complex bus like PCI or USB or SPI.
>
> So, a platform_device in Linux kernel terms, right?
>
>
Hello, yes thats correct because it uses platform_device.h
but *dev in platform_device is not called this code, already defined in a
device struct header file.
this *dev and *resource will be able to return for resource IRQ and
interrupt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20220411/86ab3b63/attachment.html>