All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	zoltan.kiss@huawei.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 03/10] xen/arm: Define quirk for Hip04 GICv2 divergence
Date: Mon, 3 Nov 2014 13:54:51 +0000	[thread overview]
Message-ID: <1415022891.24785.9.camel@citrix.com> (raw)
In-Reply-To: <54578814.3060605@linaro.org>

On Mon, 2014-11-03 at 13:50 +0000, Julien Grall wrote:
> Actually you use the quirk to do hisilicon specific (mostly in patch
> #6). I would rename the quirk to show it's platform specific, something
> like:
> 
> PLATFORM_QUIRK_HISILICON_GICV2 or PLATFROM_QUIRK_HISILICON_GICV2_16_CPU.

I think this should be keyed of the DT compatible string, since there is
one, it's not really a quirk, it's essentially implementing a different
hardware spec.

Ian.

  reply	other threads:[~2014-11-03 13:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 10:11 xen/arm: Add support for Huawei hip04-d01 platform Frediano Ziglio
2014-11-03 10:11 ` [PATCH 01/10] xen/arm: Implement " Frediano Ziglio
2014-11-03 13:39   ` Julien Grall
2015-01-13 11:58   ` Ian Campbell
2015-01-13 14:09     ` Frediano Ziglio
2015-01-13 14:42       ` Ian Campbell
2015-01-13 15:11         ` Frediano Ziglio
2015-01-13 15:23           ` Ian Campbell
2015-01-13 15:48             ` Frediano Ziglio
2015-02-19 14:23               ` Frediano Ziglio
2015-02-19 16:19                 ` Ian Campbell
2014-11-03 10:11 ` [PATCH 02/10] xen/arm: Implement hip04-d01 board reboot Frediano Ziglio
2014-11-03 13:40   ` Julien Grall
2014-11-03 10:11 ` [PATCH 03/10] xen/arm: Define quirk for Hip04 GICv2 divergence Frediano Ziglio
2014-11-03 13:50   ` Julien Grall
2014-11-03 13:54     ` Ian Campbell [this message]
2014-11-03 10:11 ` [PATCH 04/10] xen/arm: Make gic-v2 code handle hip04-d01 platform Frediano Ziglio
2014-11-03 14:10   ` Julien Grall
2015-01-13 11:54   ` Ian Campbell
2015-01-13 13:36     ` Frediano Ziglio
2014-11-03 10:11 ` [PATCH 05/10] xen/arm: Add support for DTBs with strange names of Hip04 GICv2 Frediano Ziglio
2014-11-03 10:11 ` [PATCH 06/10] xen/arm: handle GICH register changes for hip04-d01 platform Frediano Ziglio
2014-11-03 14:12   ` Julien Grall
2014-11-03 10:11 ` [PATCH 07/10] xen/arm: Force domains to use normal GICv2 driver on Hip04 platform Frediano Ziglio
2014-11-03 14:16   ` Julien Grall
2015-01-13 11:54     ` Ian Campbell
2014-11-03 10:12 ` [PATCH 08/10] xen/arm: Move vGIC registers " Frediano Ziglio
2014-11-03 10:12 ` [PATCH 09/10] xen/device_tree: Add new helper to read arrays from a DTB Frediano Ziglio
2014-11-03 14:14   ` Julien Grall
2014-11-03 14:15   ` Julien Grall
2014-11-03 10:12 ` [PATCH 10/10] xen/arm: Handle different bootwrapper locations for Hip04 platform Frediano Ziglio
2014-11-03 14:13   ` Julien Grall
2014-11-03 15:28     ` Frediano Ziglio
2014-11-03 15:33       ` Julien Grall
2014-11-03 15:36         ` Frediano Ziglio
2014-11-03 15:40           ` 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=1415022891.24785.9.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.