From: Arnd Bergmann <arnd@arndb.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@stericsson.com,
Chris Ball <cjb@laptop.org>,
Russell King <linux@arm.linux.org.uk>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree
Date: Mon, 15 Oct 2012 14:20:29 +0000 [thread overview]
Message-ID: <201210151420.29930.arnd@arndb.de> (raw)
In-Reply-To: <1350306959-5843-1-git-send-email-lee.jones@linaro.org>
On Monday 15 October 2012, Lee Jones wrote:
> Capabilities are an important part of the MMC subsystem. Much
> supported functionality would be lost if we didn't provide the
> same level of support when booting Device Tree as we currently
> do when the subsystem is passed capabilities via platform data.
> This patch supplies this support with one simple call to a
> DT parsing function.
We already document all the commonly used properties
in Documentation/devicetree/bindings/mmc/mmc.txt
Please don't add any duplicates or those that are not used
so far.
> + if(of_property_read_bool(np, "mmc-cap-4-bit-data"))
> + *caps |= MMC_CAP_4_BIT_DATA;
see "bus-width" property.
> + if(of_property_read_bool(np, "mmc-cap-mmc-highspeed"))
> + *caps |= MMC_CAP_MMC_HIGHSPEED;
> + if(of_property_read_bool(np, "mmc-cap-sd-highspeed"))
> + *caps |= MMC_CAP_SD_HIGHSPEED;
implied by "max-frequency" property.
> + if(of_property_read_bool(np, "mmc-cap-sdio-irq"))
> + *caps |= MMC_CAP_SDIO_IRQ;
implied by presence of SDIO irq property.
> + if(of_property_read_bool(np, "mmc-cap-spi"))
> + *caps |= MMC_CAP_SPI;
Only used by the mmc_spi driver, can be hardcoded there.
> + if(of_property_read_bool(np, "mmc-cap-needs-poll"))
> + *caps |= MMC_CAP_NEEDS_POLL;
implied by absence of irqs property.
> + if(of_property_read_bool(np, "mmc-cap-8-bit-data"))
> + *caps |= MMC_CAP_8_BIT_DATA;
see "bus-width" property.
> + if(of_property_read_bool(np, "mmc-cap-nonremovable"))
> + *caps |= MMC_CAP_NONREMOVABLE;
see "non-removable property.
> + if(of_property_read_bool(np, "mmc-cap-wait-while-busy"))
> + *caps |= MMC_CAP_WAIT_WHILE_BUSY;
This seems to be a linux device driver specific quirk that doesn't
belong into a hardware description.
> + if(of_property_read_bool(np, "mmc-cap-erase"))
> + *caps |= MMC_CAP_ERASE;
driver specific.
> ...
and so on. What are you actually missing in the properties that
are already there?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree
Date: Mon, 15 Oct 2012 14:20:29 +0000 [thread overview]
Message-ID: <201210151420.29930.arnd@arndb.de> (raw)
In-Reply-To: <1350306959-5843-1-git-send-email-lee.jones@linaro.org>
On Monday 15 October 2012, Lee Jones wrote:
> Capabilities are an important part of the MMC subsystem. Much
> supported functionality would be lost if we didn't provide the
> same level of support when booting Device Tree as we currently
> do when the subsystem is passed capabilities via platform data.
> This patch supplies this support with one simple call to a
> DT parsing function.
We already document all the commonly used properties
in Documentation/devicetree/bindings/mmc/mmc.txt
Please don't add any duplicates or those that are not used
so far.
> + if(of_property_read_bool(np, "mmc-cap-4-bit-data"))
> + *caps |= MMC_CAP_4_BIT_DATA;
see "bus-width" property.
> + if(of_property_read_bool(np, "mmc-cap-mmc-highspeed"))
> + *caps |= MMC_CAP_MMC_HIGHSPEED;
> + if(of_property_read_bool(np, "mmc-cap-sd-highspeed"))
> + *caps |= MMC_CAP_SD_HIGHSPEED;
implied by "max-frequency" property.
> + if(of_property_read_bool(np, "mmc-cap-sdio-irq"))
> + *caps |= MMC_CAP_SDIO_IRQ;
implied by presence of SDIO irq property.
> + if(of_property_read_bool(np, "mmc-cap-spi"))
> + *caps |= MMC_CAP_SPI;
Only used by the mmc_spi driver, can be hardcoded there.
> + if(of_property_read_bool(np, "mmc-cap-needs-poll"))
> + *caps |= MMC_CAP_NEEDS_POLL;
implied by absence of irqs property.
> + if(of_property_read_bool(np, "mmc-cap-8-bit-data"))
> + *caps |= MMC_CAP_8_BIT_DATA;
see "bus-width" property.
> + if(of_property_read_bool(np, "mmc-cap-nonremovable"))
> + *caps |= MMC_CAP_NONREMOVABLE;
see "non-removable property.
> + if(of_property_read_bool(np, "mmc-cap-wait-while-busy"))
> + *caps |= MMC_CAP_WAIT_WHILE_BUSY;
This seems to be a linux device driver specific quirk that doesn't
belong into a hardware description.
> + if(of_property_read_bool(np, "mmc-cap-erase"))
> + *caps |= MMC_CAP_ERASE;
driver specific.
> ...
and so on. What are you actually missing in the properties that
are already there?
Arnd
next prev parent reply other threads:[~2012-10-15 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 13:15 [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree Lee Jones
2012-10-15 13:15 ` Lee Jones
2012-10-15 13:15 ` [PATCH 2/2] mmc: mmci: Make use of new DT capability parsing function Lee Jones
2012-10-15 13:15 ` Lee Jones
2012-10-15 14:20 ` Arnd Bergmann [this message]
2012-10-15 14:20 ` [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree Arnd Bergmann
2012-10-15 16:07 ` Lee Jones
2012-10-15 16:07 ` Lee Jones
2012-10-17 13:38 ` Arnd Bergmann
2012-10-17 13:38 ` Arnd Bergmann
2012-10-17 18:53 ` Ulf Hansson
2012-10-17 18:53 ` Ulf Hansson
2012-10-17 19:56 ` Philip Rakity
2012-10-17 19:56 ` Philip Rakity
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=201210151420.29930.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.