From: "Pali Rohár" <pali.rohar@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/2] mmc: omap_hsmmc: Add support for slot-name property in DT
Date: Sun, 3 Jan 2016 00:03:54 +0100 [thread overview]
Message-ID: <201601030003.54168@pali> (raw)
In-Reply-To: <9361696.ohU1ACX8N1@wuerfel>
[-- Attachment #1: Type: Text/Plain, Size: 1597 bytes --]
On Saturday 02 January 2016 23:57:47 Arnd Bergmann wrote:
> On Saturday 02 January 2016 16:22:03 Pali Rohár wrote:
> > On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> > > On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
> > > > > I mean you can add the platform data to the
> > > > > omap_auxdata_lookup[] table for this board.
> > > >
> > > > But can I mix data from omap3-n900.dts and
> > > > omap_auxdata_lookup[]?
> >
> > Hm... looks like it is not possible. omap_hsmmc driver ignores any
> > supplied platform data if there are device tree data. So array
> > omap_auxdata_lookup[] does not help.
>
> Obviously you need to the driver to work with that setting. Maybe
> something as simple as
>
> diff --git a/drivers/mmc/host/omap_hsmmc.c
> b/drivers/mmc/host/omap_hsmmc.c index e06b1881b6a1..4fa35fc84b8b
> 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -2006,7 +2006,7 @@ static int omap_hsmmc_probe(struct
> platform_device *pdev) void __iomem *base;
>
> match = of_match_device(of_match_ptr(omap_mmc_of_match),
> &pdev->dev); - if (match) {
> + if (!pdata && match) {
> pdata = of_get_hsmmc_pdata(&pdev->dev);
>
> if (IS_ERR(pdata))
>
>
> Arnd
But in this case I must copy mmc definition from omap3-n900.dts file
back to board code to omap_auxdata_lookup[]. And mmc definitions in
omap3-n900.dts will be ignored. This is step back.
Mixing mmc definitions from DTS file together with omap_auxdata_lookup[]
just will not work.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2016-01-02 23:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:14 [PATCH 0/2] omap_hsmmc: Supports slot-name also in DT Pali Rohár
[not found] ` <1431724489-32359-1-git-send-email-pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-15 21:14 ` [PATCH 1/2] mmc: omap_hsmmc: Add support for slot-name property " Pali Rohár
2015-05-15 21:19 ` Arnd Bergmann
2015-05-15 21:22 ` Pali Rohár
2015-05-15 21:25 ` Arnd Bergmann
2015-05-18 15:06 ` Tony Lindgren
[not found] ` <20150518150607.GD10274-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-05-18 15:07 ` Arnd Bergmann
2015-12-25 12:53 ` Pali Rohár
2015-12-28 14:14 ` Arnd Bergmann
2015-12-28 14:28 ` Pali Rohár
2015-12-28 14:41 ` Arnd Bergmann
2015-12-28 14:54 ` Pali Rohár
2015-12-28 14:55 ` Arnd Bergmann
2016-01-02 15:22 ` Pali Rohár
2016-01-02 22:57 ` Arnd Bergmann
2016-01-02 23:03 ` Pali Rohár [this message]
2016-01-02 23:17 ` Arnd Bergmann
2015-05-15 21:14 ` [PATCH 2/2] omap3-n900.dts: Add slot-name properties for mmc devices Pali Rohár
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=201601030003.54168@pali \
--to=pali.rohar@gmail.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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).