Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/7] clk: sunxi-ng: add A64 compatible string
Date: Mon, 25 Jun 2018 17:58:50 +0200	[thread overview]
Message-ID: <20180625155850.m4unvqyxc3aavrkv@flea> (raw)
In-Reply-To: <20180622124540.56203-3-icenowy@aosc.io>

On Fri, Jun 22, 2018 at 08:45:37PM +0800, Icenowy Zheng wrote:
> As claiming Allwinner A64 SRAM C is a prerequisite for all sub-blocks of
> the A64 DE2, not only the CCU sub-block, a bus driver is then written for
> enabling the access to the whole DE2 part by claiming the SRAM.
> 
> In this situation, the A64 compatible string will be just added with no
> other requirments, as they're processed by the parent bus driver.
> 
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> ---
> No changes since v1.
> 
>  drivers/clk/sunxi-ng/ccu-sun8i-de2.c | 11 ++++-------
>  1 file changed, 4 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/clk/sunxi-ng/ccu-sun8i-de2.c b/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> index 468d1abaf0ee..8df7cd93453e 100644
> --- a/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> +++ b/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> @@ -292,13 +292,10 @@ static const struct of_device_id sunxi_de2_clk_ids[] = {
>  		.compatible = "allwinner,sun50i-h5-de2-clk",
>  		.data = &sun50i_a64_de2_clk_desc,
>  	},
> -	/*
> -	 * The Allwinner A64 SoC needs some bit to be poke in syscon to make
> -	 * DE2 really working.
> -	 * So there's currently no A64 compatible here.
> -	 * H5 shares the same reset line with A64, so here H5 is using the
> -	 * clock description of A64.
> -	 */
> +	{
> +		.compatible = "allwinner,sun50i-a64-de2-clk",
> +		.data = &sun50i_a64_de2_clk_desc,
> +	},

This should be before the h5 (and possibly others?) compatible.

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180625/0510cac7/attachment.sig>

  reply	other threads:[~2018-06-25 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:45 [PATCH v2 2/7] dt-bindings: add binding for the Allwinner A64 DE2 bus Icenowy Zheng
2018-06-22 12:45 ` [PATCH v2 3/7] bus: add bus driver for accessing Allwinner A64 DE2 Icenowy Zheng
2018-06-25 15:58   ` Maxime Ripard
2018-06-25 15:59     ` Icenowy Zheng
2018-06-22 12:45 ` [PATCH v2 4/7] clk: sunxi-ng: add A64 compatible string Icenowy Zheng
2018-06-25 15:58   ` Maxime Ripard [this message]
2018-06-22 12:45 ` [PATCH v2 5/7] arm64: allwinner: a64: add necessary device tree nodes for DE2 CCU Icenowy Zheng
2018-06-23 14:06   ` [linux-sunxi] " Julian Calaby
2018-06-23 14:18     ` Icenowy Zheng
2018-06-23 14:49       ` Julian Calaby
2018-06-22 12:45 ` [PATCH v2 6/7] arm64: allwinner: a64: add device tree node for HDMI simplefb Icenowy Zheng
2018-06-25 15:59   ` Maxime Ripard
2018-06-26  3:32   ` [linux-sunxi] " Chen-Yu Tsai
2018-06-25 20:18 ` [PATCH v2 2/7] dt-bindings: add binding for the Allwinner A64 DE2 bus Rob Herring

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=20180625155850.m4unvqyxc3aavrkv@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox