public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Jun Nie <jun.nie@linaro.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
	"xie.baoyou" <xie.baoyou@zte.com.cn>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Jason Liu <jason.liu@linaro.org>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] mmc: dw: Add fifo watermark quirk
Date: Mon, 31 Oct 2016 18:35:04 +0900	[thread overview]
Message-ID: <db1f0415-41a0-8a94-b2fb-bfc39b3cee2a@samsung.com> (raw)
In-Reply-To: <CABymUCMqjcFmK=T8Um+zLqECvzv+o4M8VjribrG=SrePn5BU+Q@mail.gmail.com>

On 10/31/2016 05:48 PM, Jun Nie wrote:
> 2016-10-28 13:30 GMT+08:00 Jaehoon Chung <jh80.chung@samsung.com>:
>> On 10/28/2016 11:37 AM, Jun Nie wrote:
>>> Data done irq is expected if data length is less than
>>> watermark in PIO mode. But fifo watermark is requested
>>> to be aligned with data length in some SoC so that TX/RX
>>> irq can be generated with data done irq. Add the
>>> watermark quirk to mark this requirement and force
>>> fifo watermark setting accordingly.
>>>
>>> Signed-off-by: Jun Nie <jun.nie@linaro.org>
>>> ---
>>>  drivers/mmc/host/dw_mmc.c  | 11 +++++++++--
>>>  include/linux/mmc/dw_mmc.h |  2 ++
>>>  2 files changed, 11 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
>>> index 24ae05b6..e0f49cc 100644
>>> --- a/drivers/mmc/host/dw_mmc.c
>>> +++ b/drivers/mmc/host/dw_mmc.c
>>> @@ -1111,11 +1111,15 @@ static void dw_mci_submit_data(struct dw_mci *host, struct mmc_data *data)
>>>               mci_writel(host, CTRL, temp);
>>>
>>>               /*
>>> -              * Use the initial fifoth_val for PIO mode.
>>> +              * Use the initial fifoth_val for PIO mode. If wm_quirk
>>> +              * is set, we set watermark same as data size.
>>>                * If next issued data may be transfered by DMA mode,
>>>                * prev_blksz should be invalidated.
>>>                */
>>> -             mci_writel(host, FIFOTH, host->fifoth_val);
>>> +             if (host->wm_quirk)
>>> +                     dw_mci_adjust_fifoth(host, data);
>>> +             else
>>> +                     mci_writel(host, FIFOTH, host->fifoth_val);
>>>               host->prev_blksz = 0;
>>>       } else {
>>>               /*
>>> @@ -2957,6 +2961,9 @@ static struct dw_mci_board *dw_mci_parse_dt(struct dw_mci *host)
>>>
>>>       of_property_read_u32(np, "fifo-addr", &host->fifo_addr_override);
>>>
>>> +     if (of_get_property(np, "fifo-watermark-quirk", NULL))
>>> +             host->wm_quirk = true;
>>> +
>>>       if (!of_property_read_u32(np, "clock-frequency", &clock_frequency))
>>>               pdata->bus_hz = clock_frequency;
>>>
>>> diff --git a/include/linux/mmc/dw_mmc.h b/include/linux/mmc/dw_mmc.h
>>> index 4866ef5..2ccfd9c 100644
>>> --- a/include/linux/mmc/dw_mmc.h
>>> +++ b/include/linux/mmc/dw_mmc.h
>>> @@ -108,6 +108,7 @@ struct dw_mci_dma_slave {
>>>   * @slot: Slots sharing this MMC controller.
>>>   * @fifo_depth: depth of FIFO.
>>>   * @fifo_addr_override: override fifo reg offset with this value.
>>> + * @wm_quirk: force fifo watermark equal with data length in PIO mode.
>>
>> quirk...hmm..It might be just my preference..
>> quirk looks like workaround...so how about changing other name?
> 
> How about fifo_wm_aligned ?

If it's not quirk or workaround, whatever. :)

Best Regards,
Jaehoon Chung

> 
>>
>>>   * @data_shift: log2 of FIFO item size.
>>>   * @part_buf_start: Start index in part_buf.
>>>   * @part_buf_count: Bytes of partial data in part_buf.
>>> @@ -156,6 +157,7 @@ struct dw_mci {
>>>       void __iomem            *regs;
>>>       void __iomem            *fifo_reg;
>>>       u32                     fifo_addr_override;
>>> +     u32                     wm_quirk;
>>
>> For True or false, u32?
> True means alignment is needed. Will add  this to comments.
>>
>>>
>>>       struct scatterlist      *sg;
>>>       struct sg_mapping_iter  sg_miter;
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 


      reply	other threads:[~2016-10-31  9:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28  2:37 [PATCH v2 0/5] Add intial support to DW MMC host on ZTE SoC Jun Nie
2016-10-28  2:37 ` [PATCH v2 1/5] mmc: dt-bindings: add ZTE MMC bindings Jun Nie
2016-10-28  2:37 ` [PATCH v2 2/5] mmc: zx: Initial support for ZX mmc controller Jun Nie
2016-10-28  5:16   ` Jaehoon Chung
2016-10-31  8:47     ` Jun Nie
2016-10-31  9:40       ` Jaehoon Chung
2016-11-01  1:16         ` Jun Nie
2016-11-01  7:25           ` Jaehoon Chung
2016-11-01  7:45             ` Jun Nie
2016-10-28 12:00   ` kbuild test robot
2016-10-28  2:37 ` [PATCH v2 3/5] Documentation: synopsys-dw-mshc: add binding for fifo quirks Jun Nie
2016-10-28  2:37 ` [PATCH v2 4/5] mmc: dw: Add fifo address property Jun Nie
2016-10-28  5:24   ` Jaehoon Chung
2016-10-31  8:50     ` Jun Nie
2016-10-31  9:35       ` Jaehoon Chung
2016-10-28  2:37 ` [PATCH v2 5/5] mmc: dw: Add fifo watermark quirk Jun Nie
2016-10-28  5:30   ` Jaehoon Chung
2016-10-31  8:48     ` Jun Nie
2016-10-31  9:35       ` Jaehoon Chung [this message]

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=db1f0415-41a0-8a94-b2fb-bfc39b3cee2a@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=jason.liu@linaro.org \
    --cc=jun.nie@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=ulf.hansson@linaro.org \
    --cc=xie.baoyou@zte.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