From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Frediano Ziglio <frediano.ziglio@huawei.com>,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@citrix.com>,
zoltan.kiss@huawei.com
Subject: Re: [PATCH v5.99.1 RFC 1/4] xen/arm: Duplicate gic-v2.c file to support hip04 platform version
Date: Wed, 25 Feb 2015 15:46:07 +0000 [thread overview]
Message-ID: <1424879167.18290.16.camel@citrix.com> (raw)
In-Reply-To: <54EDEB9F.9080207@linaro.org>
On Wed, 2015-02-25 at 15:34 +0000, Julien Grall wrote:
> Hi Frediano,
>
> On 25/02/15 15:28, Frediano Ziglio wrote:
> > HiSilison Hip04 platform use a slightly different version
>
> I honestly don't like the idea to copy the whole GIC-v2 drivers. It will
> require more maintenance for us.
Will it? This puts the hip driver in its own file where I presume
Frediano et al will take care of it.
> Is there any way to introduce callbacks in the GICv2 code where the
> hisilicon hardware differs?
That's even worse than the first approach (if (hip()) in gic-v2.c) IMHO.
The if-s (or hooks) would be a maintenance burden in the gic-v2.c
driver, making maintenance harder for all the other platforms which
actually followed the spec.
>
> > Signed-off-by: Frediano Ziglio <frediano.ziglio@huawei.com>
> > ---
> > xen/arch/arm/Makefile | 2 +-
> > xen/arch/arm/gic-hip04.c | 788 +++++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 789 insertions(+), 1 deletion(-)
> > create mode 100644 xen/arch/arm/gic-hip04.c
> >
> > diff --git a/xen/arch/arm/Makefile b/xen/arch/arm/Makefile
> > index 41aba2e..6fb8ba9 100644
> > --- a/xen/arch/arm/Makefile
> > +++ b/xen/arch/arm/Makefile
> > @@ -11,7 +11,7 @@ obj-y += vpsci.o
> > obj-y += domctl.o
> > obj-y += sysctl.o
> > obj-y += domain_build.o
> > -obj-y += gic.o gic-v2.o
> > +obj-y += gic.o gic-v2.o gic-hip04.o
>
> As you do a verbatim copy, you should enable to compilation on the next
> patch.
>
> Regards,
>
next prev parent reply other threads:[~2015-02-25 15:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 9:56 [PATCH v5] xen/arm: Add support for Huawei hip04-d01 platform Frediano Ziglio
2015-02-20 9:56 ` [PATCH v5 1/4] xen/arm: Make gic-v2 code handle " Frediano Ziglio
2015-02-24 16:16 ` Ian Campbell
2015-02-25 15:28 ` [PATCH v5.99.1 RFC 0/4] xen/arm: Add support for Huawei " Frediano Ziglio
2015-02-25 15:28 ` [PATCH v5.99.1 RFC 1/4] xen/arm: Duplicate gic-v2.c file to support hip04 platform version Frediano Ziglio
2015-02-25 15:34 ` Julien Grall
2015-02-25 15:42 ` Frediano Ziglio
2015-02-25 15:46 ` Ian Campbell [this message]
2015-02-25 15:47 ` Frediano Ziglio
2015-02-25 16:34 ` Stefano Stabellini
2015-02-25 16:59 ` Ian Campbell
2015-02-26 12:44 ` Ian Campbell
2015-02-26 13:54 ` Julien Grall
2015-02-26 15:28 ` Ian Campbell
2015-02-26 17:39 ` Ian Campbell
2015-02-26 17:59 ` Stefano Stabellini
2015-02-25 15:28 ` [PATCH v5.99.1 RFC 2/4] xen/arm: Make gic-v2 code handle hip04-d01 platform Frediano Ziglio
2015-02-25 16:53 ` Stefano Stabellini
2015-02-26 9:54 ` Frediano Ziglio
2015-02-25 15:28 ` [PATCH v5.99.1 RFC 3/4] xen/arm: handle GICH register changes for " Frediano Ziglio
2015-02-25 16:53 ` Stefano Stabellini
2015-02-25 15:28 ` [PATCH v5.99.1 RFC 4/4] xen/arm: Force dom0 to use normal GICv2 driver on Hip04 platform Frediano Ziglio
2015-02-25 16:54 ` Stefano Stabellini
2015-02-20 9:56 ` [PATCH v5 2/4] xen/arm: Add support for DTBs with strange names of Hip04 GICv2 Frediano Ziglio
2015-02-24 14:19 ` Julien Grall
2015-02-24 16:13 ` Ian Campbell
2015-02-24 16:38 ` Frediano Ziglio
2015-02-24 14:19 ` Julien Grall
2015-02-20 9:56 ` [PATCH v5 3/4] xen/arm: handle GICH register changes for hip04-d01 platform Frediano Ziglio
2015-02-20 9:56 ` [PATCH v5 4/4] xen/arm: Force dom0 to use normal GICv2 driver on Hip04 platform Frediano Ziglio
2015-02-25 16:43 ` [PATCH v5] xen/arm: Add support for Huawei hip04-d01 platform Ian Campbell
2015-02-25 17:10 ` Frediano Ziglio
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=1424879167.18290.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=frediano.ziglio@huawei.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@huawei.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 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.