All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: linux-arm-kernel@lists.infradead.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@googlegroups.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add a regmap to Allwinner R40 CCU to export GMAC register
Date: Thu, 2 Nov 2017 00:11:25 -0700	[thread overview]
Message-ID: <20171102071125.GL30645@codeaurora.org> (raw)
In-Reply-To: <14505033-D960-4287-92F2-554E2EDDFC59@aosc.io>

On 10/09, Icenowy Zheng wrote:
> 
> 
> 于 2017年10月9日 GMT+08:00 下午3:18:09, Maxime Ripard <maxime.ripard@free-electrons.com> 写到:
> >On Fri, Oct 06, 2017 at 06:33:31AM +0000, Icenowy Zheng wrote:
> >> In the CCU of the Allwinner R40 SoC, there's a GMAC configuration
> >register,
> >> which is intended to be accessed by the dwmac-sun8i driver. On SoCs
> >already
> >> supported by the driver the register is placed in the syscon rather
> >than
> >> the CCU.
> >> 
> >> As CCU is a critical part of the SoC, so write to it should be
> >strictly
> >> limited. A regmap with restricted write permission is created by the
> >R40
> >> CCU driver, and can be get with dev_get_regmap. In order to tie the
> >regmap
> >> to the CCU device, the R40 CCU is now a platform driver, so a
> >platform
> >> device is created for it (and then tied with the regmap).
> >> 
> >> The first patch does the conversion of the driver to a platform
> >driver,
> >> and the second patch adds the regmap.
> >
> >I'd like to see first what you want to do with it.
> 
> Export the GMAC configuration register to dwmac-sun8i.
> 

Is this series going to be reposted?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add a regmap to Allwinner R40 CCU to export GMAC register
Date: Thu, 2 Nov 2017 00:11:25 -0700	[thread overview]
Message-ID: <20171102071125.GL30645@codeaurora.org> (raw)
In-Reply-To: <14505033-D960-4287-92F2-554E2EDDFC59@aosc.io>

On 10/09, Icenowy Zheng wrote:
> 
> 
> ? 2017?10?9? GMT+08:00 ??3:18:09, Maxime Ripard <maxime.ripard@free-electrons.com> ??:
> >On Fri, Oct 06, 2017 at 06:33:31AM +0000, Icenowy Zheng wrote:
> >> In the CCU of the Allwinner R40 SoC, there's a GMAC configuration
> >register,
> >> which is intended to be accessed by the dwmac-sun8i driver. On SoCs
> >already
> >> supported by the driver the register is placed in the syscon rather
> >than
> >> the CCU.
> >> 
> >> As CCU is a critical part of the SoC, so write to it should be
> >strictly
> >> limited. A regmap with restricted write permission is created by the
> >R40
> >> CCU driver, and can be get with dev_get_regmap. In order to tie the
> >regmap
> >> to the CCU device, the R40 CCU is now a platform driver, so a
> >platform
> >> device is created for it (and then tied with the regmap).
> >> 
> >> The first patch does the conversion of the driver to a platform
> >driver,
> >> and the second patch adds the regmap.
> >
> >I'd like to see first what you want to do with it.
> 
> Export the GMAC configuration register to dwmac-sun8i.
> 

Is this series going to be reposted?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-11-02  7:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06  6:33 [PATCH 0/2] Add a regmap to Allwinner R40 CCU to export GMAC register Icenowy Zheng
2017-10-06  6:33 ` Icenowy Zheng
2017-10-06  6:33 ` [PATCH 1/2] clk: sunxi-ng: r40: rewrite init code to a platform driver Icenowy Zheng
2017-10-06  6:33   ` Icenowy Zheng
2017-10-06  6:33 ` [PATCH 2/2] clk: sunxi-ng: r40: export a regmap to access the GMAC register Icenowy Zheng
2017-10-06  6:33   ` Icenowy Zheng
2017-10-09  7:18 ` [PATCH 0/2] Add a regmap to Allwinner R40 CCU to export " Maxime Ripard
2017-10-09  7:18   ` Maxime Ripard
2017-10-09  7:22   ` Icenowy Zheng
2017-10-09  7:22     ` Icenowy Zheng
2017-11-02  7:11     ` Stephen Boyd [this message]
2017-11-02  7:11       ` Stephen Boyd
2017-11-02  7:49       ` Icenowy Zheng
2017-11-02  7:49         ` Icenowy Zheng

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=20171102071125.GL30645@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=icenowy@aosc.io \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=wens@csie.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 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.