linux-kernel - Re: [PATCH V4 4/5] mmc: mmci: stm32: define get_dctrl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPDyKFqh1pZhaiS9D22egZjDb_SL3_shs4Gr4PJUZVAXCbW5aA@mail.gmail.com>
Date:   Wed, 27 Mar 2019 15:47:23 +0100
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Ludovic BARRE <ludovic.barre@...com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        DTML <devicetree@...r.kernel.org>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH V4 4/5] mmc: mmci: stm32: define get_dctrl_cfg

On Wed, 27 Mar 2019 at 15:44, Ludovic BARRE <ludovic.barre@...com> wrote:
>
>
>
> On 3/27/19 11:54 AM, Ulf Hansson wrote:
> > On Wed, 27 Mar 2019 at 10:05, Ludovic Barre <ludovic.Barre@...com> wrote:
> >>
> >> From: Ludovic Barre <ludovic.barre@...com>
> >>
> >> This patch defines get_dctrl_cfg callback for sdmmc variant.
> >> sdmmc variant has specific stm32 transfer modes.
> >> sdmmc data transfer mode selection could be:
> >> -Block data transfer ending on block count.
> >> -SDIO multibyte data transfer.
> >> -MMC Stream data transfer (not used).
> >> -Block data transfer ending with STOP_TRANSMISSION command.
> >>
> >> Signed-off-by: Ludovic Barre <ludovic.barre@...com>
> >> ---
> >>   drivers/mmc/host/mmci.h             |  5 +++++
> >>   drivers/mmc/host/mmci_stm32_sdmmc.c | 18 ++++++++++++++++++
> >>   2 files changed, 23 insertions(+)
> >>
> >> diff --git a/drivers/mmc/host/mmci.h b/drivers/mmc/host/mmci.h
> >> index 35c91d0..82e9f94 100644
> >> --- a/drivers/mmc/host/mmci.h
> >> +++ b/drivers/mmc/host/mmci.h
> >> @@ -131,6 +131,11 @@
> >>   /* Control register extensions in the Qualcomm versions */
> >>   #define MCI_DPSM_QCOM_DATA_PEND        BIT(17)
> >>   #define MCI_DPSM_QCOM_RX_DATA_PEND BIT(20)
> >> +/* Control register extensions in STM32 versions */
> >> +#define MCI_DPSM_STM32_MODE_BLOCK      (0 << 2)
> >> +#define MCI_DPSM_STM32_MODE_SDIO       (1 << 2)
> >> +#define MCI_DPSM_STM32_MODE_STREAM     (2 << 2)
> >> +#define MCI_DPSM_STM32_MODE_BLOCK_STOP (3 << 2)
> >>
> >>   #define MMCIDATACNT            0x030
> >>   #define MMCISTATUS             0x034
> >> diff --git a/drivers/mmc/host/mmci_stm32_sdmmc.c b/drivers/mmc/host/mmci_stm32_sdmmc.c
> >> index cfbfc6f..8e83ae6 100644
> >> --- a/drivers/mmc/host/mmci_stm32_sdmmc.c
> >> +++ b/drivers/mmc/host/mmci_stm32_sdmmc.c
> >> @@ -265,10 +265,28 @@ static void mmci_sdmmc_set_pwrreg(struct mmci_host *host, unsigned int pwr)
> >>          }
> >>   }
> >>
> >> +static u32 sdmmc_get_dctrl_cfg(struct mmci_host *host)
> >> +{
> >> +       u32 datactrl;
> >> +
> >> +       datactrl = mmci_dctrl_blksz(host);
> >> +
> >> +       if (host->mmc->card && mmc_card_sdio(host->mmc->card) &&
> >> +           host->data->blocks == 1)
> >> +               datactrl |= MCI_DPSM_STM32_MODE_SDIO;
> >> +       else if (host->data->stop && !host->mrq->sbc)
> >> +               datactrl |= MCI_DPSM_STM32_MODE_BLOCK_STOP;
> >
> > Just a question here. Does this mean that the controller sends the
> > stop command automatically when a transfer has finished successfully?
>
> The controller not sends the stop command, this bit is just an
> information for the Data State Machine to know how the data transfer
> finish.

Okay, thanks for clarifying!

Kind regards
Uffe