mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Hermes Zhang <chenhuiz@axis.com>
Cc: kernel@axis.com, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: core: expose MMC_CAP_AGGRESSIVE_PM to DT
Date: Tue, 24 Jan 2023 12:06:53 +0100	[thread overview]
Message-ID: <CAPDyKFqUnp_rDcckBSW386webSgjAhfdONN_AKYCS-kY3XwKPg@mail.gmail.com> (raw)
In-Reply-To: <20230118045749.3913296-1-chenhuiz@axis.com>

On Wed, 18 Jan 2023 at 05:57, Hermes Zhang <chenhuiz@axis.com> wrote:
>
> This patch expose the MMC_CAP_AGGRESSIVE_PM flag to DT which
> allows the host to enable it from DT.
>
> Signed-off-by: Hermes Zhang <chenhuiz@axis.com>
> ---
>  drivers/mmc/core/host.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c
> index d17eda753b7e..1d98a301515d 100644
> --- a/drivers/mmc/core/host.c
> +++ b/drivers/mmc/core/host.c
> @@ -376,6 +376,8 @@ int mmc_of_parse(struct mmc_host *host)
>                 host->caps |= MMC_CAP_HW_RESET;
>         if (device_property_read_bool(dev, "cap-sdio-irq"))
>                 host->caps |= MMC_CAP_SDIO_IRQ;
> +       if (device_property_read_bool(dev, "cap-aggressive-pm"))
> +               host->caps |= MMC_CAP_AGGRESSIVE_PM;

I think this can be debated whether this is a description of some
characteristics of the HW.

That said, please add the DT list and maintainers and resend, to let
them share their view too.

>         if (device_property_read_bool(dev, "full-pwr-cycle"))
>                 host->caps2 |= MMC_CAP2_FULL_PWR_CYCLE;
>         if (device_property_read_bool(dev, "full-pwr-cycle-in-suspend"))
> --

Kind regards
Uffe

      reply	other threads:[~2023-01-24 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  4:57 Hermes Zhang
2023-01-24 11:06 ` Ulf Hansson [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=CAPDyKFqUnp_rDcckBSW386webSgjAhfdONN_AKYCS-kY3XwKPg@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=chenhuiz@axis.com \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.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

all inboxes | Powered by JetHome®