public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: fwu@marvell.com, linus.walleij@linaro.org
Cc: tony@atomide.com, plagnioj@jcrosoft.com, kgene.kim@samsung.com,
	heiko@sntech.de, t.figa@samsung.com, thomas.abraham@linaro.org,
	srinivas.kandagatla@gmail.com, maxime.coquelin@st.com,
	patrice.chotard@st.com, thierry.reding@gmail.com,
	baohua@kernel.org, viresh.linux@gmail.com,
	matt.porter@linaro.org, syin@broadcom.com, jg1.han@samsung.com,
	Rongjun.Ying@csr.com, Rong.Wang@csr.com, linux@prisktech.co.nz,
	yongjun_wei@trendmicro.com.cn, laurent.navet@gmail.com,
	linux-kernel@vger.kernel.org, swarren@nvidia.com,
	cxie4@marvell.com, ylmao@marvell.com, njiang1@marvell.com,
	tianxf@marvell.com, fswu@marvell.com
Subject: Re: [PATCH v5] pinctrl: to avoid duplicated calling enable_pinmux_setting for a pin
Date: Thu, 05 Jun 2014 09:49:17 -0600	[thread overview]
Message-ID: <5390917D.4040607@wwwdotorg.org> (raw)
In-Reply-To: <1401951040-17403-1-git-send-email-fwu@marvell.com>

On 06/05/2014 12:50 AM, fwu@marvell.com wrote:
> From: Fan Wu <fwu@marvell.com>
> 
> What the patch did:
> 1.To call pinmux_disable_setting ahead of pinmux_enable_setting in each time of
>   calling pinctrl_select_state
> 2.Remove the HW disable operation in in pinmux_disable_setting function.
> 3.Remove the disable ops in struct pinmux_ops
> 4.Remove all the disable ops users in current code base.
...

The overall concept, plus the bcm2835, and Tegra driver parts,
Acked-by: Stephen Warren <swarren@nvidia.com>

That said ...

> diff --git a/drivers/pinctrl/pinctrl-tegra.c b/drivers/pinctrl/pinctrl-tegra.c

> -static void tegra_pinctrl_disable(struct pinctrl_dev *pctldev,
> -				  unsigned function, unsigned group)
> -{
> -	struct tegra_pmx *pmx = pinctrl_dev_get_drvdata(pctldev);
> -	const struct tegra_pingroup *g;
> -	u32 val;
> -
> -	g = &pmx->soc->groups[group];
> -
> -	if (WARN_ON(g->mux_reg < 0))
> -		return;
> -
> -	val = pmx_readl(pmx, g->mux_bank, g->mux_reg);
> -	val &= ~(0x3 << g->mux_bit);
> -	val |= g->func_safe << g->mux_bit;
> -	pmx_writel(pmx, val, g->mux_bank, g->mux_reg);

Those last 5 lines don't exist in the latest code, so this patch won't
apply cleanly. You probably want to rebase this on top of LinusW's
latest pinctrl development branch.

  parent reply	other threads:[~2014-06-05 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  6:50 [PATCH v5] pinctrl: to avoid duplicated calling enable_pinmux_setting for a pin fwu
2014-06-05  7:29 ` Maxime Coquelin
2014-06-05 15:49 ` Stephen Warren [this message]
2014-06-06  7:52 ` Patrice Chotard
2014-06-06  8:13 ` Heiko Stübner

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=5390917D.4040607@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=Rong.Wang@csr.com \
    --cc=Rongjun.Ying@csr.com \
    --cc=baohua@kernel.org \
    --cc=cxie4@marvell.com \
    --cc=fswu@marvell.com \
    --cc=fwu@marvell.com \
    --cc=heiko@sntech.de \
    --cc=jg1.han@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=laurent.navet@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@prisktech.co.nz \
    --cc=matt.porter@linaro.org \
    --cc=maxime.coquelin@st.com \
    --cc=njiang1@marvell.com \
    --cc=patrice.chotard@st.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=srinivas.kandagatla@gmail.com \
    --cc=swarren@nvidia.com \
    --cc=syin@broadcom.com \
    --cc=t.figa@samsung.com \
    --cc=thierry.reding@gmail.com \
    --cc=thomas.abraham@linaro.org \
    --cc=tianxf@marvell.com \
    --cc=tony@atomide.com \
    --cc=viresh.linux@gmail.com \
    --cc=ylmao@marvell.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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