All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hunyue Yau <hy-gsoc@hy-research.com>
To: Denis Obrezkov <denisobrezkov@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Iain Hunter <drhunter95@gmail.com>
Subject: Re: [Xen-devel] [GSoC-2019] About the crossbar and xen
Date: Wed, 10 Jul 2019 16:20:31 -0700	[thread overview]
Message-ID: <520937670.d9P0eaHOQZ@acer0> (raw)
In-Reply-To: <e7104450-54ae-6720-9d9f-f4e8889946c8@gmail.com>

Denis,

Not sure if you gone through this - the interrupt routing is described in the 
TRM chapter on interrupt controllers. In my edition (large file, don't want to 
redownload unless needed.), this is chapter 17. Table 17-2 (in my edition)  
should address a lot of what you are asking. It shows the IRQ Input line (aka 
GIC ID number), the IRQ cross bar instance along with the config register and 
some description. Figure 17-1 shows the the layout. 

From what I can tell, the cross bar is so the interrupt can be sent to the 
other processor on the die besides the cortex-a (aka MPU in the TRM). Mapping 
the TRM names to DT names might still be bit of work but this should give you 
an idea what to look for in the Linux kernel to backout the names used.


On Wednesday, July 10, 2019 22:43:37 Denis Obrezkov wrote:
> Hi,
> 
> On 7/10/19 10:17 PM, Stefano Stabellini wrote:
> > On Wed, 10 Jul 2019, Denis Obrezkov wrote:
> >> Hi,
> >> 
> >> On 7/10/19 9:49 PM, Stefano Stabellini wrote:
> >>>   phandle = <0x00000002>;
> >>> 
> >>> I think that means that interrupts go to the GIC via Crossbar; i.e. the
> >>> parent interrupt controller of Crossbar is the GIC.
> >> 
> >> But the crossbar's interrupt-parent node is 0x00000008 and phandle value
> >> 0x00000008 belongs to
> >> interrupt-controller@48281000 {
> >> 
> >> 		compatible = "ti,omap5-wugen-mpu", "ti,omap4-wugen-mpu";
> >> 
> >> For me it looks like interrupts from crossbar goes to wugen and the from
> >> wugen to GIC. But I don't quite understand it.
> > 
> > Hi Denis,
> > 
> > I only read your email and got a partial picture. I read the full device
> > tree now and the hierarchy is as follow:
> > 
> > - crossbar routes to phandle 8
> > - phandle 8 is omap5-wugen-mpu and routes to phandle 2
> > - phandle 2 is the GIC
> > 
> > So:
> > 
> > crossbar -> omap5-wugen-mpu -> GIC
> 
> I am interested whether we should do something with omap5-wugen-mpu. I
> found that crossbar is connected to GIC. And on some schemes in trm it
> is connected via omap5-wugen-mpu. So, it is not clear for me whether it
> should be handled in xen.

-- 
Hunyue Yau
http://www.hy-research.com/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-07-11  2:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 18:54 [Xen-devel] [GSoC-2019] About the crossbar and xen Denis Obrezkov
2019-07-10 19:49 ` Stefano Stabellini
2019-07-10 19:54   ` Denis Obrezkov
2019-07-10 20:17     ` Stefano Stabellini
2019-07-10 20:43       ` Denis Obrezkov
2019-07-10 23:20         ` Hunyue Yau [this message]
2019-07-11 12:50           ` Denis Obrezkov
2019-07-11 17:32             ` Julien Grall
2019-07-11 18:29               ` Hunyue Yau
2019-07-12 15:13                 ` Julien Grall
2019-07-12 18:32                   ` Hunyue Yau z
2019-07-15 11:36                     ` Julien Grall
2019-07-11 18:29               ` Denis Obrezkov
2019-07-12 15:00                 ` Julien Grall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=520937670.d9P0eaHOQZ@acer0 \
    --to=hy-gsoc@hy-research.com \
    --cc=denisobrezkov@gmail.com \
    --cc=drhunter95@gmail.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.