Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Marten Lindahl <martenli@axis.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Mårten Lindahl" <Marten.Lindahl@axis.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Doug Anderson" <dianders@google.com>, kernel <kernel@axis.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v3] mmc: dw_mmc: Allow lower TMOUT value than maximum
Date: Tue, 16 Nov 2021 17:59:53 +0100	[thread overview]
Message-ID: <20211116165949.GA32249@axis.com> (raw)
In-Reply-To: <CAPDyKFpKbKEePYyb1fQ_cxjtJS6JuF1qFKh2KKfXpM23nvkH+g@mail.gmail.com>

On Mon, Nov 15, 2021 at 03:54:19PM +0100, Ulf Hansson wrote:
> On Wed, 10 Nov 2021 at 12:05, Mårten Lindahl <marten.lindahl@axis.com> wrote:
> >
> > The TMOUT register is always set with a full value for every transfer,
> > which (with a 200MHz clock) will give a full DRTO of ~84 milliseconds.
> > Since the software dto_timer acts as a backup in cases when this timeout
> > is not long enough, it is normally not a problem. But setting a full
> > value makes it impossible to test shorter timeouts, when for example
> > testing data read times on different SD cards.
> >
> > Add a function to set any value smaller than the maximum of 0xFFFFFF.
> >
> > Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
> 
> Applied for next, thanks!
> 
> Kind regards
> Uffe
>

Hi Ulf!

During tests on some units I found that there is a potential overflow
of the 32bit divider in this patch (if clk_div > 4).

Is it possible to stop this patch, until I created a new version of it?
I guess it's better to update this patch, in favour of sending a new
correction patch for it?

Kind regards
Mårten

> 
> > ---
> >
> > v2:
> >  - Calculate new value before checking boundaries
> >  - Include CLKDIV register to get proper value
> >
> > v3:
> >  - Use 'if-else' instead of 'goto'
> >  - Don't touch response field when maximize data field
> >
> >  drivers/mmc/host/dw_mmc.c | 28 +++++++++++++++++++++++++++-
> >  1 file changed, 27 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> > index 6578cc64ae9e..637ae2aea9fa 100644
> > --- a/drivers/mmc/host/dw_mmc.c
> > +++ b/drivers/mmc/host/dw_mmc.c
> > @@ -1283,6 +1283,32 @@ static void dw_mci_setup_bus(struct dw_mci_slot *slot, bool force_clkinit)
> >         mci_writel(host, CTYPE, (slot->ctype << slot->id));
> >  }
> >
> > +static void dw_mci_set_data_timeout(struct dw_mci *host,
> > +                                   unsigned int timeout_ns)
> > +{
> > +       unsigned int clk_div, tmp, tmout;
> > +
> > +       clk_div = (mci_readl(host, CLKDIV) & 0xFF) * 2;
> > +       if (clk_div == 0)
> > +               clk_div = 1;
> > +
> > +       tmp = DIV_ROUND_UP_ULL((u64)timeout_ns * host->bus_hz,
> > +                              NSEC_PER_SEC * clk_div);
> > +
> > +       /* TMOUT[7:0] (RESPONSE_TIMEOUT) */
> > +       tmout = 0xFF; /* Set maximum */
> > +
> > +       /* TMOUT[31:8] (DATA_TIMEOUT) */
> > +       if (!tmp || tmp > 0xFFFFFF)
> > +               tmout |= (0xFFFFFF << 8);
> > +       else
> > +               tmout |= (tmp & 0xFFFFFF) << 8;
> > +
> > +       mci_writel(host, TMOUT, tmout);
> > +       dev_dbg(host->dev, "timeout_ns: %u => TMOUT[31:8]: 0x%06x",
> > +               timeout_ns, tmout >> 8);
> > +}
> > +
> >  static void __dw_mci_start_request(struct dw_mci *host,
> >                                    struct dw_mci_slot *slot,
> >                                    struct mmc_command *cmd)
> > @@ -1303,7 +1329,7 @@ static void __dw_mci_start_request(struct dw_mci *host,
> >
> >         data = cmd->data;
> >         if (data) {
> > -               mci_writel(host, TMOUT, 0xFFFFFFFF);
> > +               dw_mci_set_data_timeout(host, data->timeout_ns);
> >                 mci_writel(host, BYTCNT, data->blksz*data->blocks);
> >                 mci_writel(host, BLKSIZ, data->blksz);
> >         }
> > --
> > 2.20.1
> >

  reply	other threads:[~2021-11-16 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20211110110553epcas1p27c5a3a2ff49282ae29895bcd30f922c3@epcas1p2.samsung.com>
2021-11-10 11:05 ` [PATCH v3] mmc: dw_mmc: Allow lower TMOUT value than maximum Mårten Lindahl
2021-11-10 16:12   ` Doug Anderson
2021-11-10 21:54   ` Jaehoon Chung
2021-11-15 14:54   ` Ulf Hansson
2021-11-16 16:59     ` Marten Lindahl [this message]
2021-11-17  9:36       ` Ulf Hansson

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=20211116165949.GA32249@axis.com \
    --to=martenli@axis.com \
    --cc=Marten.Lindahl@axis.com \
    --cc=dianders@google.com \
    --cc=jh80.chung@samsung.com \
    --cc=kernel@axis.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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