linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chaotian.jing@mediatek.com (Chaotian Jing)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/7] mmc: mediatek: Add Mediatek MMC driver
Date: Thu, 4 Jun 2015 10:54:03 +0800	[thread overview]
Message-ID: <1433386443.3304.2.camel@mhfsdcap03> (raw)
In-Reply-To: <20150519111558.GD6325@pengutronix.de>

On Tue, 2015-05-19 at 13:15 +0200, Sascha Hauer wrote:
> On Tue, May 19, 2015 at 02:36:46PM +0800, Chaotian Jing wrote:
> > Add Mediatek MMC driver code
> > Support eMMC/SD/SDIO
> > 
> > Signed-off-by: Chaotian Jing <chaotian.jing@mediatek.com>
> > ---
> >  drivers/mmc/host/Kconfig  |    8 +
> >  drivers/mmc/host/Makefile |    1 +
> >  drivers/mmc/host/mtk-sd.c | 1422 +++++++++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 1431 insertions(+)
> >  create mode 100644 drivers/mmc/host/mtk-sd.c
> > 
> > +
> > +	host->src_clk = devm_clk_get(&pdev->dev, "source");
> > +	if (IS_ERR(host->src_clk)) {
> > +		ret = PTR_ERR(host->src_clk);
> > +		goto host_free;
> > +	}
> > +
> > +	host->h_clk = devm_clk_get(&pdev->dev, "hclk");
> > +	if (IS_ERR(host->h_clk)) {
> > +		/* host->h_clk is optional, Only for MSDC0/3 at MT8173 */
> > +		dev_dbg(&pdev->dev,
> > +				"Invalied hclk from the device tree!\n");
> > +	}
> 
> s/Invalied/Invalid/
> 
> According to my reference manual the controller always needs a hclk. It
> seems on some controllers it is just not software controllable. If
> that's the case you should always provide a hclk to the driver and make
> this clock mandatory.
For MT8173, MSDC1, MSDC2's HCLK are in Infra, software cannot control
it. So just set the HCLK to clk_null ?

If it is, will set HCLK to clk_null at next revision, and the same
changes will make for MT8135.
> 
> Sascha
> 

  reply	other threads:[~2015-06-04  2:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  6:36 [PATCH v4 0/7] Add Mediatek MMC driver Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 1/7] mmc: dt-bindings: add Mediatek MMC bindings Chaotian Jing
2015-05-19  9:41   ` Ulf Hansson
2015-05-26  6:27     ` Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 2/7] mmc: mediatek: Add Mediatek MMC driver Chaotian Jing
2015-05-19 10:27   ` Ulf Hansson
2015-05-22  8:40     ` Chaotian Jing
2015-05-22 12:51       ` Ulf Hansson
2015-05-26  6:16         ` Chaotian Jing
2015-05-26 12:33           ` Ulf Hansson
2015-05-27 11:34             ` Chaotian Jing
2015-06-04  7:32               ` Ulf Hansson
2015-05-19 11:15   ` Sascha Hauer
2015-06-04  2:54     ` Chaotian Jing [this message]
2015-06-04  9:02       ` Sascha Hauer
2015-05-19 11:19   ` Russell King - ARM Linux
2015-05-20  9:14     ` Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 3/7] mmc: mediatek: Add PM support for " Chaotian Jing
2015-05-19 10:41   ` Ulf Hansson
2015-05-19 11:04   ` Sascha Hauer
2015-05-19 11:55     ` Ulf Hansson
2015-05-19  6:36 ` [PATCH v4 4/7] arm64: dts: mediatek: Add MT8173 MMC dts Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 5/7] arm64: mediatek: Add Mediatek MMC support in defconfig Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 6/7] ARM: mediatek: dts: Add emmc support to mt8135 Chaotian Jing
2015-05-19  6:36 ` [PATCH v4 7/7] ARM: multi_v7_defconfig: Enable Mediatek MMC support multi-v7 Chaotian Jing

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=1433386443.3304.2.camel@mhfsdcap03 \
    --to=chaotian.jing@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).