Hi,
On 12/07/2019 19:32, Hunyue Yau z wrote:
On Friday, July 12, 2019 16:13:32 Julien Grall wrote:
Hi,
On 7/11/19 7:29 PM, Hunyue Yau wrote:
[This mail incorporates comments raised on IRC. I have made some of this
mHi,ore verbose to provide context to people that haven't seen the IRC
comments
On Friday, July 12, 2019 16:13:32 Julien Grall wrote:
> Hi,
>
> On 7/11/19 7:29 PM, Hunyue Yau wrote:
> > [This mail incorporates comments raised on IRC. I have made some of this
> > mHi,ore verbose to provide context to people that haven't seen the IRC
> > comments.]
> Thank you for the summary!
Hi,
On 7/11/19 7:29 PM, Hunyue Yau wrote:
[This mail incorporates comments raised on IRC. I have made some of this mHi,ore
verbose to provide context to people that haven't seen the IRC comments.]
Thank you for the summary!
This will be a bunch of facts on the am5. Someone else will have re
On 7/11/19 7:29 PM, Denis Obrezkov wrote:
Hi,
Hi,
On 7/11/19 7:32 PM, Julien Grall wrote:
What do you think?
Have you looked at the series I pointed out earlier on? It extends Xen
to support other interrupt controller parent.
Yes, but you said once that these patch series wasn't accept
Hi,
On 7/11/19 7:32 PM, Julien Grall wrote:
>>
>> What do you think?
>
> Have you looked at the series I pointed out earlier on? It extends Xen
> to support other interrupt controller parent.
>
Yes, but you said once that these patch series wasn't accepted because
maintainers didn't like someth
[This mail incorporates comments raised on IRC. I have made some of this more
verbose to provide context to people that haven't seen the IRC comments.]
This will be a bunch of facts on the am5. Someone else will have relate it
back to Xen.
1 - The WUGen is a hardware block on the MPU block that
On 7/11/19 1:50 PM, Denis Obrezkov wrote:
Hi,
Hi,
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.
Hi,
>>
>> 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.
>
Also, I am interested in how to add
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 t
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 = <0x0002>;
>>>
>>> I think that means that interrupts go to the GIC via Crossbar; i.e. the
>>> parent interrupt contr
On Wed, 10 Jul 2019, Denis Obrezkov wrote:
> Hi,
>
> On 7/10/19 9:49 PM, Stefano Stabellini wrote:
>
> >
> > phandle = <0x0002>;
> >
> > 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'
Hi,
On 7/10/19 9:49 PM, Stefano Stabellini wrote:
>
> phandle = <0x0002>;
>
> 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 0x0008 and phandle value
0x000
On Wed, 10 Jul 2019, Denis Obrezkov wrote:
> Hello,
>
> so, I think I understood why uart doesn't work, that's because all the
> irqs are routed to the crossbar not to GIC, so, xen can't deal with them.
>
> One thing I am concerned of is the:
> interrupt-controller@48281000 {
>
Hello,
so, I think I understood why uart doesn't work, that's because all the
irqs are routed to the crossbar not to GIC, so, xen can't deal with them.
One thing I am concerned of is the:
interrupt-controller@48281000 {
compatible = "ti,omap5-wugen-mpu", "ti,omap4-wugen-mp
14 matches
Mail list logo
