On Tue, Apr 12, 2022 at 03:51:24PM +0900, Chan Kim wrote:
> Hi Greg KH and all,
>
> I found how to find the irq number in my case! (char driver kernel module)
> I want to share it for reference to others.
>
> add these two header files for this.
> #include
> #include
>
> extern struct
y, April 12, 2022 4:15 PM
> *To:* Chan Kim
> *Cc:* Greg KH ; kernelnewbies@kernelnewbies.org;
> qemu-discuss
> *Subject:* Re: Can't understand /proc/interrupts output for GICv3 case
>
>
>
>
>
> On Tue, Apr 12, 2022 at 6:44 AM Chan Kim wrote:
>
> Hi Ozgur,
be reading the references again soon)
Chan
From: Ozgur Karatas
Sent: Tuesday, April 12, 2022 4:15 PM
To: Chan Kim
Cc: Greg KH ; kernelnewbies@kernelnewbies.org; qemu-discuss
Subject: Re: Can't understand /proc/interrupts output for GICv3 case
On Tue, Apr 12, 2022 at 6:44 AM Chan Kim
over a kernel api, kernel would
handle it in the get interrupt part.
Regards
Ozgur
>
> *From:* Ozgur Karatas
> *Sent:* Monday, April 11, 2022 11:53 PM
> *To:* Chan Kim
> *Cc:* Greg KH ; kernelnewbies@kernelnewbies.org;
> qemu-discuss
> *Subject:* Re
an Kim
> -Original Message-
> From: Chan Kim
> Sent: Tuesday, April 12, 2022 1:55 PM
> To: 'Greg KH'
> Cc: kernelnewbies@kernelnewbies.org; 'qemu-discuss' disc...@nongnu.org>
> Subject: RE: Can't understand /proc/interrupts output for GICv3 case
>
> Hi Gr
: 'qemu-discuss' ;
> kernelnewbies@kernelnewbies.org
> Subject: Re: Can't understand /proc/interrupts output for GICv3 case
>
> On Tue, Apr 12, 2022 at 11:18:03AM +0900, Chan Kim wrote:
> > > You can replace all of the above code by just using the miscdevice
> > > interface inst
On Tue, Apr 12, 2022 at 11:18:03AM +0900, Chan Kim wrote:
> > You can replace all of the above code by just using the miscdevice
> > interface instead. Please use that, it ensures that you do everything
> > properly and simplifies it all.
Again, use the misc device api please.
> > > vaddr =
Hi Ozgur,
My replies in-line.
Thanks!
From: Ozgur Karatas
Sent: Monday, April 11, 2022 11:53 PM
To: Chan Kim
Cc: Greg KH ; kernelnewbies@kernelnewbies.org; qemu-discuss
Subject: Re: Can't understand /proc/interrupts output for GICv3 case
Re-hi,
On Mon, Apr 11, 2022 at 6:16
Hi, Greg KH,
Thanks for the advices.
Some questions inline.
> -Original Message-
> From: 'Greg KH'
> Sent: Monday, April 11, 2022 11:26 PM
> To: Chan Kim
> Cc: 'qemu-discuss' ;
> kernelnewbies@kernelnewbies.org
> Subject: Re: Can't understand /proc/interrupts
On Mon, Apr 11, 2022 at 6:49 PM Greg KH wrote:
> On Mon, Apr 11, 2022 at 03:32:23PM +0100, Peter Maydell wrote:
> > On Mon, 11 Apr 2022 at 15:22, Chan Kim wrote:
> > >
> > >
> > > > > > What bus type is your driver written for?
> > > > > >
> > > > > That sounds very logical. In my case I added
On Mon, 11 Apr 2022 at 15:49, Greg KH wrote:
>
> On Mon, Apr 11, 2022 at 03:32:23PM +0100, Peter Maydell wrote:
> > On Mon, 11 Apr 2022 at 15:22, Chan Kim wrote:
> > >
> > >
> > > > > > What bus type is your driver written for?
> > > > > >
> > > > > That sounds very logical. In my case I added
Re-hi,
On Mon, Apr 11, 2022 at 6:16 PM Chan Kim 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
On Mon, Apr 11, 2022 at 03:32:23PM +0100, Peter Maydell wrote:
> On Mon, 11 Apr 2022 at 15:22, Chan Kim 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
On Mon, 11 Apr 2022 at 15:22, Chan Kim 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.
>
On Mon, Apr 11, 2022 at 11:15:57PM +0900, Chan Kim 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
> > > 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.
>
> Where is your kernel code?
On Mon, Apr 11, 2022 at 10:13:42PM +0900, Chan Kim wrote:
> Hi, Greg K-H,
> Thanks for replyaing.
> >
> > You ask the system for it. It depends on the bus type your driver is
> > written for for how to do this.
> >
> > For example, if you have a platform driver, you would call
> >
g with SPI (serial peripheral interface) later :).Thank you.Chan From: Ozgur Kara <oz...@goosey.org>Sent: Monday, April 11, 2022 10:10 PMTo: Chan Kim <c...@etri.re.kr>; 'qemu-discuss' <qemu-disc...@nongnu.org>; kernelnewbies@kernelnewbies.orgSubject: Re: Can't understand /proc/inte
Kara
Sent: Monday, April 11, 2022 10:10 PM
To: Chan Kim ; 'qemu-discuss' ;
kernelnewbies@kernelnewbies.org
Subject: Re: Can't understand /proc/interrupts output for GICv3 case
Hello,
firstly when you say SPI so can you give some more information about your
hardware?
I think you are doing
Hi, Greg K-H,
Thanks for replyaing.
>
> You ask the system for it. It depends on the bus type your driver is
> written for for how to do this.
>
> For example, if you have a platform driver, you would call
> platform_get_irq(). If you are a pci driver, the irq for your device is
> already
esc number)in kernel driver module?I'll appreciate it if you could tell me how to do it.Thank you!Chan Kim -Original Message- From: Chan Kim <c...@etri.re.kr> Sent: Friday, April 8, 2022 1:53 PM To: 'qemu-discuss' <qemu-disc...@nongnu.org>; kernelnewbies@kernelnewbies.org Subject:
On Mon, Apr 11, 2022 at 09:36:14PM +0900, Chan Kim wrote:
> Hi,
> nobody's replying to my question.. so sad..
> I found the kernel makes an array (actually a radix tree) of 'irq_desc's.
> And my hwirq (SPI 15) is assigned to one of these irq_descs while processing
> device tree.
> In my case it
an Kim
> Sent: Friday, April 8, 2022 1:53 PM
> To: 'qemu-discuss' ;
> kernelnewbies@kernelnewbies.org
> Subject: Can't understand /proc/interrupts output for GICv3 case
>
> Hello all
>
> I think I'm asking too many question recently but sometimes I get very big
> help from he
Hello all
I think I'm asking too many question recently but sometimes I get very big
help from here so please forgive me.
(and I think someone else can get help from this email thread)
I'm doing experiment for interrupt of a device called axpu on an arm64
virtual machine.
In QEMU virtual machine,
24 matches
Mail list logo
