From: Dinh Nguyen <dinguyen@altera.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "dinh.linux@gmail.com" <dinh.linux@gmail.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"mturquette@linaro.org" <mturquette@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"cjb@laptop.org" <cjb@laptop.org>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>,
"tgih.jun@samsung.com" <tgih.jun@samsung.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv3 3/4] mmc: dw_mmc-socfpga: Clean up SOCFPGA platform specific funcationality
Date: Thu, 5 Dec 2013 10:18:00 -0600 [thread overview]
Message-ID: <1386260280.3783.4.camel@linux-builds1> (raw)
In-Reply-To: <20131205114740.GM29200@e106331-lin.cambridge.arm.com>
On Thu, 2013-12-05 at 11:47 +0000, Mark Rutland wrote:
> On Wed, Dec 04, 2013 at 10:52:55PM +0000, dinguyen@altera.com wrote:
> > From: Dinh Nguyen <dinguyen@altera.com>
> >
> > The SDR timing registers for the SD/MMC IP block for SOCFPGA is located
> > in the system manager. This system manager IP block is located outside of
> > the SD IP block itself. We can use the normal clock API to set the SDR
> > settings.
> >
> > Also, there is no need for "altr,dw-mshc-ciu-div" as the driver can get
> > the value of the CIU clock from the common clock API.
>
> If this property isn't necessary, please mark it as deprecated in the
> documentation.
I would deprecate it. If only there was documentation for it.
>
> [...]
>
> > + if (IS_ERR(sysmgr_clk))
> > + dev_err(host->dev, "sysmgr-sdr-mmc not available\n");
> > + else {
> > + clk_disable_unprepare(host->ciu_clk);
> > + clk_prepare_enable(sysmgr_clk);
> > + clk_prepare_enable(host->ciu_clk);
> > + }
> > return 0;
> > }
>
> This looks a little odd. Should you not return an error if you don't
> have the requisite clocks?
>
> [...]
>
> > - priv->sysreg = syscon_regmap_lookup_by_compatible("altr,sys-mgr");
> > - if (IS_ERR(priv->sysreg)) {
> > - dev_err(host->dev, "regmap for altr,sys-mgr lookup failed.\n");
> > - return PTR_ERR(priv->sysreg);
> > - }
>
> Is this property deprecated?
"altr,sys-mgr" is used in other places, so no deprecated is necessary.
>
> > -
> > - ret = of_property_read_u32(np, "altr,dw-mshc-ciu-div", &div);
> > - if (ret)
> > - dev_info(host->dev, "No dw-mshc-ciu-div specified, assuming 1");
> > - priv->ciu_div = div;
> > -
> > - ret = of_property_read_u32_array(np,
> > - "altr,dw-mshc-sdr-timing", timing, 2);
>
> Deprecated too?
Once again "altr,dw-mshc-sdr-timing" was not documented. But either way,
v4 of this patch will not be introducing any new bindings. Thanks to
Arnd's suggestion, I found a way to hook into the existing socfpga clock
driver.
Thanks alot for your review!
Dinh
>
> Thanks,
> Mark.
>
next prev parent reply other threads:[~2013-12-05 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 22:52 [PATCHv3 0/4] socfpga: Enable SD/MMC support dinguyen
2013-12-04 22:52 ` [PATCHv3 1/4] clk: socfpga: Add a clock driver for SOCFPGA's system manager dinguyen
2013-12-05 3:00 ` Arnd Bergmann
2013-12-04 22:52 ` [PATCHv3 2/4] arm: dts: Add a system manager compatible property dinguyen
2013-12-05 11:40 ` Mark Rutland
2013-12-04 22:52 ` [PATCHv3 3/4] mmc: dw_mmc-socfpga: Clean up SOCFPGA platform specific funcationality dinguyen
2013-12-05 11:47 ` Mark Rutland
2013-12-05 16:18 ` Dinh Nguyen [this message]
2013-12-04 22:52 ` [PATCHv3 4/4] arm: dts: Add support for SD/MMC on SOCFPGA dinguyen
2013-12-05 3:07 ` Arnd Bergmann
2013-12-05 16:14 ` Dinh Nguyen
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=1386260280.3783.4.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=Pawel.Moll@arm.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=tgih.jun@samsung.com \
/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).