linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Ai Kyuse <ai.kyuse.uw@renesas.com>
Subject: Re: [PATCH v5 03/11] mmc: tmio: Add hw reset support
Date: Thu, 1 Sep 2016 08:45:18 +0200	[thread overview]
Message-ID: <20160901064518.GA15138@verge.net.au> (raw)
In-Reply-To: <CAPDyKFrne-a=p9_mod7h6Nh-WD0HWBHfh9s1nUjBCJkwhsxbWw@mail.gmail.com>

On Wed, Aug 31, 2016 at 09:50:53AM +0200, Ulf Hansson wrote:
> On 30 August 2016 at 23:09, Simon Horman <horms+renesas@verge.net.au> wrote:
> > From: Ai Kyuse <ai.kyuse.uw@renesas.com>
> >
> > Add hw reset support.
> >
> > Signed-off-by: Ai Kyuse <ai.kyuse.uw@renesas.com>
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> > This is required by tuning support which will
> > be introduced by follow-up patches.
> >
> > v5 [Simon Horman]
> > * As suggested by Ulf Hansson
> >   - Broke out of a larger patch
> > ---
> >  drivers/mmc/host/tmio_mmc.h     |  1 +
> >  drivers/mmc/host/tmio_mmc_pio.c | 12 ++++++++++++
> >  2 files changed, 13 insertions(+)
> >
> > diff --git a/drivers/mmc/host/tmio_mmc.h b/drivers/mmc/host/tmio_mmc.h
> > index 4b36cb5c2d9c..4b71f31fba63 100644
> > --- a/drivers/mmc/host/tmio_mmc.h
> > +++ b/drivers/mmc/host/tmio_mmc.h
> > @@ -164,6 +164,7 @@ struct tmio_mmc_host {
> >         int (*start_signal_voltage_switch)(struct mmc_host *mmc,
> >                                            struct mmc_ios *ios);
> >         int (*write16_hook)(struct tmio_mmc_host *host, int addr);
> > +       void (*hw_reset)(struct tmio_mmc_host *host);
> >  };
> >
> >  struct tmio_mmc_host *tmio_mmc_host_alloc(struct platform_device *pdev);
> > diff --git a/drivers/mmc/host/tmio_mmc_pio.c b/drivers/mmc/host/tmio_mmc_pio.c
> > index 806308ac93e7..90758647bae6 100644
> > --- a/drivers/mmc/host/tmio_mmc_pio.c
> > +++ b/drivers/mmc/host/tmio_mmc_pio.c
> > @@ -756,6 +756,17 @@ static int tmio_mmc_start_data(struct tmio_mmc_host *host,
> >         return 0;
> >  }
> >
> > +static void tmio_mmc_hw_reset(struct mmc_host *mmc)
> > +{
> > +       struct tmio_mmc_host *host = mmc_priv(mmc);
> > +
> > +       if (host->hw_reset)
> > +               host->hw_reset(host);
> > +
> > +       mmc_retune_timer_stop(host->mmc);
> > +       mmc_retune_needed(host->mmc);
> 
> Both the above tuning calls are completely pointless as the mmc core
> will run a reinitialization of the card when a ->hw_reset() host ops
> is invoked.
> That means a regular tuning will happen as part of the initialization
> of the card, so you don't need to trigger it from here as well.
> 
> So if that's the only reason to why you need to add the hw_reset()
> support, I think you should drop it instead.

Yes, sorry for leaving that in.
I will drop it.

> > +}
> > +
> >  /* Process requests from the MMC layer */
> >  static void tmio_mmc_request(struct mmc_host *mmc, struct mmc_request *mrq)
> >  {
> > @@ -970,6 +981,7 @@ static struct mmc_host_ops tmio_mmc_ops = {
> >         .get_cd         = mmc_gpio_get_cd,
> >         .enable_sdio_irq = tmio_mmc_enable_sdio_irq,
> >         .multi_io_quirk = tmio_multi_io_quirk,
> > +       .hw_reset       = tmio_mmc_hw_reset,
> >  };
> >
> >  static int tmio_mmc_init_ocr(struct tmio_mmc_host *host)
> > --
> > 2.7.0.rc3.207.g0ac5344
> >
> 
> Kind regards
> Uffe
> 

  reply	other threads:[~2016-09-01  6:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 21:09 [PATCH v5 00/11] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-08-30 21:09 ` [PATCH v5 01/11] mmc: tmio: enhance illegal sequence handling Simon Horman
2016-08-30 21:09 ` [PATCH v5 02/11] mmc: tmio: document mandatory and optional callbacks Simon Horman
2016-08-30 21:09 ` [PATCH v5 03/11] mmc: tmio: Add hw reset support Simon Horman
2016-08-31  7:50   ` Ulf Hansson
2016-09-01  6:45     ` Simon Horman [this message]
2016-08-30 21:09 ` [PATCH v5 04/11] mmc: tmio: Add tuning support Simon Horman
2016-08-30 21:09 ` [PATCH v5 05/11] mmc: sh_mobile_sdhi: " Simon Horman
2016-08-30 21:09 ` [PATCH v5 06/11] ARM: dts: lager: Enable UHS-I SDR-104 Simon Horman
2016-08-30 21:09 ` [PATCH v5 07/11] arm64: dts: r8a7795: remove unnecessary cap-mmc-highspeed property Simon Horman
2016-09-01 14:32   ` Simon Horman
2016-09-16 10:29   ` Wolfram Sang
2016-08-30 21:09 ` [PATCH v5 08/11] arm64: r8a7795: Set maximum frequencies for SDHI clocks Simon Horman
2016-08-31  8:44   ` Wolfram Sang
2016-09-01 14:24     ` Simon Horman
2016-08-30 21:09 ` [PATCH v5 09/11] arm64: dts: r8a7795: salvator: enable UHS for SDHI 0 & 3 Simon Horman
2016-08-30 21:09 ` [PATCH v5 10/11] arm64: dts: r8a7795: salvator-x: Enable UHS-I SDR-104 Simon Horman
2016-09-01  7:23   ` Wolfram Sang
2016-09-01 14:25     ` Simon Horman
2016-09-01 14:29       ` Wolfram Sang
2016-09-01 14:37         ` Simon Horman
2016-08-30 21:09 ` [PATCH v5 11/11] arm64: defconfig: Enable SDHI and GPIO_REGULATOR Simon Horman
2016-09-01 14:33   ` Simon Horman

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=20160901064518.GA15138@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ai.kyuse.uw@renesas.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).