[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150205112701.GD11344@leverpostej>
Date: Thu, 5 Feb 2015 11:27:01 +0000
From: Mark Rutland <mark.rutland@....com>
To: Addy Ke <addy.ke@...k-chips.com>
Cc: "robh+dt@...nel.org" <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"tgih.jun@...sung.com" <tgih.jun@...sung.com>,
"jh80.chung@...sung.com" <jh80.chung@...sung.com>,
"chris@...ntf.net" <chris@...ntf.net>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"dinguyen@...era.com" <dinguyen@...era.com>,
"heiko@...ech.de" <heiko@...ech.de>,
"olof@...om.net" <olof@...om.net>,
"dianders@...omium.org" <dianders@...omium.org>,
"sonnyrao@...omium.org" <sonnyrao@...omium.org>,
"amstan@...omium.org" <amstan@...omium.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-rockchip@...ts.infradead.org"
<linux-rockchip@...ts.infradead.org>,
"zhenfu.fang@...k-chips.com" <zhenfu.fang@...k-chips.com>,
"cf@...k-chips.com" <cf@...k-chips.com>,
"lintao@...k-chips.com" <lintao@...k-chips.com>,
"chenfen@...k-chips.com" <chenfen@...k-chips.com>,
"zyf@...k-chips.com" <zyf@...k-chips.com>,
"xjq@...k-chips.com" <xjq@...k-chips.com>,
"huangtao@...k-chips.com" <huangtao@...k-chips.com>,
"zyw@...k-chips.com" <zyw@...k-chips.com>,
"yzq@...k-chips.com" <yzq@...k-chips.com>,
"hj@...k-chips.com" <hj@...k-chips.com>,
"kever.yang@...k-chips.com" <kever.yang@...k-chips.com>,
"zhangqing@...k-chips.com" <zhangqing@...k-chips.com>,
"hl@...k-chips.com" <hl@...k-chips.com>
Subject: Re: [PATCH] mmc: core: add runtime-resume caps to support resume at
runtime_resume
On Thu, Feb 05, 2015 at 11:06:59AM +0000, Addy Ke wrote:
> Signed-off-by: Addy Ke <addy.ke@...k-chips.com>
> ---
> Documentation/devicetree/bindings/mmc/mmc.txt | 11 +++++++++++
> drivers/mmc/core/host.c | 2 ++
> 2 files changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt
> index 438899e..303b448 100644
> --- a/Documentation/devicetree/bindings/mmc/mmc.txt
> +++ b/Documentation/devicetree/bindings/mmc/mmc.txt
> @@ -40,9 +40,20 @@ Optional properties:
> - mmc-hs200-1_2v: eMMC HS200 mode(1.2V I/O) is supported
> - mmc-hs400-1_8v: eMMC HS400 mode(1.8V I/O) is supported
> - mmc-hs400-1_2v: eMMC HS400 mode(1.2V I/O) is supported
> +- runtime-resume: resume at runtime_resume is supported
This reads like description of Linux internals (runtime_resume), which
shouldn't be in the DT.
What does this mean at the HW level? I'm sure we can find a better name
for this, or another way of describing this.
> - dsr: Value the card's (optional) Driver Stage Register (DSR) should be
> programmed with. Valid range: [0 .. 0xffff].
>
> +Card power and reset control:
> +The following properties can be specified for cases where the MMC
> +peripheral needs additional reset, regulator and clock lines. It is for
> +example common for WiFi/BT adapters to have these separate from the main
> +MMC bus:
> + - card-reset-gpios: Specify GPIOs for card reset (reset active low)
> + - card-external-vcc-supply: Regulator to drive (independent) card VCC
> + - clock with name "card_ext_clock": External clock provided to the card
Are these proeprties placed on the MMC controller node, or a sub-node
representing the card/slot?
Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists