From: Sascha Hauer <s.hauer@pengutronix.de>
To: Trent Piepho <tpiepho@kymetacorp.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/4] mci: core: bus-width property should override driver default
Date: Thu, 19 Nov 2015 08:52:43 +0100 [thread overview]
Message-ID: <20151119075243.GC11966@pengutronix.de> (raw)
In-Reply-To: <1447880807.4553.171.camel@rtred1test09.kymeta.local>
On Wed, Nov 18, 2015 at 09:06:46PM +0000, Trent Piepho wrote:
> The OF code for parsing bus-width would only add the specified width
> to those the driver might have already set capability flags for.
>
> Because of this, if the driver had set 8 or 4 bit width, it wasn't
> possible for the DT to specify that fewer pins were used on the board
> and a smaller width was necessary.
>
> Change this so the width in the DT overrides whatever widths the
> driver says it supports. There is no reason to have an incorrect
> device tree and it makes far more sense for the DT to override the
> driver default than for the driver default to override the DT.
>
> The widths the driver puts in host_caps before calling mci_of_parse()
> are considered the default if the DT doesn't specify bus-width. This
> should cause the least amount of change to existing boards, as despite
> a comment that no bus-width meant to use 1 bit, using the driver
> default is what was really happening.
>
> Unfortunately, half of existing drivers default to the largest width
> they support while the other half default to the smallest. Boards
> should just stick the width in the device tree.
>
> Signed-off-by: Trent Piepho <tpiepho@kymetacorp.com>
> ---
> drivers/mci/mci-core.c | 38 ++++++++++++++++++++++----------------
> include/mci.h | 2 ++
> 2 files changed, 24 insertions(+), 16 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-11-19 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 21:06 Trent Piepho
2015-11-18 21:11 ` [PATCH 2/4] mci: dw_mmc: socfpga: Supply bus-width in platform_data Trent Piepho
2015-11-18 21:12 ` [PATCH 3/4] mci: dw_mmc: Delete devname " Trent Piepho
2015-11-18 21:14 ` [PATCH 4/4] mci: dw_mmc: Add support for high speed modes Trent Piepho
2015-11-19 7:52 ` Sascha Hauer [this message]
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=20151119075243.GC11966@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=tpiepho@kymetacorp.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