From: Sudeep Holla <sudeep.holla@arm.com>
To: Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org, Liviu Dudau <liviu.dudau@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH] arm64: dts: juno: fix size of GICv2m MSI frames
Date: Wed, 28 Feb 2018 15:58:11 +0000 [thread overview]
Message-ID: <f4ce910b-f263-a4e1-710c-875ac152d4bf@arm.com> (raw)
In-Reply-To: <36126393-ee37-40f1-9d5d-1c7f25c648dc@arm.com>
On 28/02/18 15:51, Robin Murphy wrote:
> Hi Sudeep,
>
> Cheers for sorting it out...
>
> On 28/02/18 15:48, Sudeep Holla wrote:
>> Currently the size of GICv2m MSI frames are listed as 4kB while the
>> Juno TRM specifies 64kB for each of these MSI frames.
>>
>> Though the devices connected themself might just use the first 4kB,
>
> s/themself/themselves/
>
>> to be consistent with the genaral practice of 64kB boundary alignment
>
> s/genaral/general/
>
Fixed those now.
>> to all the devices, lets keep the size as 64kB. This might also help
>> in avoiding any surprise when passing the device to a VM.
>>
>> This patch increase the size of each GICv2m MSI frames from 4kB to 64kB
>> as per the specification.
>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
>
Thanks.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-02-28 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 14:32 [PATCH 0/2] irqchip: GICv2m Multi-MSI support Marc Zyngier
2018-02-07 14:32 ` [PATCH 1/2] irqchip/gic-v2m: Add PCI " Marc Zyngier
2018-02-07 15:18 ` Liviu Dudau
2018-02-07 14:32 ` [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region Marc Zyngier
2018-02-12 18:17 ` Sudeep Holla
2018-02-12 18:22 ` Robin Murphy
2018-02-12 18:26 ` Sudeep Holla
2018-02-12 18:27 ` Marc Zyngier
2018-02-12 19:17 ` Robin Murphy
2018-02-28 15:48 ` Sudeep Holla
2018-02-28 15:48 ` [PATCH] arm64: dts: juno: fix size of GICv2m MSI frames Sudeep Holla
2018-02-28 15:51 ` Robin Murphy
2018-02-28 15:58 ` Sudeep Holla [this message]
2018-02-28 16:54 ` Marc Zyngier
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=f4ce910b-f263-a4e1-710c-875ac152d4bf@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=marc.zyngier@arm.com \
--cc=robin.murphy@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).