From: Pavel Machek <pavel@denx.de>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
kgene.kim@samsung.com, heiko@sntech.de, tgih.jun@samsung.com,
linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <chris@printf.net>,
linux-samsung-soc@vger.kernel.org, dinguyen@altera.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv10 0/5] ARM: remove the sub-node and deprecate supports-highspeed property for dwmmc.
Date: Tue, 26 Aug 2014 12:19:24 +0200 [thread overview]
Message-ID: <20140826101923.GA13619@amd> (raw)
In-Reply-To: <53FB2807.7070503@samsung.com>
Hi!
> >> Would you elaborate?
> >>
> >> If I have a device like a phone, I may want to put one "slot" inside
> >> phone for basic system, and offer second slot for user expansion
> >> (initially empty).
> >
> > if multiple slot is supported, then a mmcqd should be processing for multiple slots.
> > It's too inefficient, and affect the whole performance reduction.
> Sorry, Discard this comment. it means dwmci, not mmcqd.
Well, that's a Linux problem, and for many applications, not even
problem at all.
Device tree should describe hardware, and hardware can do multiple
slots per controller, so device tree should describe multiple slots
per controller.
Now, the configuration may be uncommon, but you are moving from good
hardware description to bad hardware description.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-08-26 10:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 7:37 [PATCHv10 0/5] ARM: remove the sub-node and deprecate supports-highspeed property for dwmmc Jaehoon Chung
2014-08-07 7:37 ` [PATCHv10 1/5] mmc: dw_mmc: Slot quirk "disable-wp" is deprecated Jaehoon Chung
2014-08-11 9:45 ` Ulf Hansson
2014-08-07 7:37 ` [PATCHv10 2/5] mmc: dw_mmc: modify the dt-binding for removing slot-node and supports-highspeed Jaehoon Chung
2014-08-11 9:46 ` Ulf Hansson
[not found] ` <1407397082-32495-1-git-send-email-jh80.chung-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-08-07 7:38 ` [PATCHv10 3/5] ARM: dts: exynos: unuse the slot-node and deprecate the supports-highspeed for dw-mmc Jaehoon Chung
2014-08-18 12:23 ` Jaehoon Chung
2014-08-18 14:10 ` Andreas Färber
2014-08-18 16:54 ` Kukjin Kim
2014-08-18 17:06 ` Andreas Färber
2014-08-18 17:40 ` Kukjin Kim
2014-08-19 3:52 ` Jaehoon Chung
2014-08-07 7:38 ` [PATCHv10 4/5] ARM: dts: socfpga: " Jaehoon Chung
2014-08-11 21:03 ` Dinh Nguyen
2014-08-07 7:38 ` [PATCHv10 5/5] ARM: dts: rockchip: " Jaehoon Chung
2014-08-11 14:38 ` Heiko Stübner
2014-08-25 11:21 ` [PATCHv10 0/5] ARM: remove the sub-node and deprecate supports-highspeed property for dwmmc Pavel Machek
2014-08-25 11:28 ` Jaehoon Chung
2014-08-25 11:37 ` Pavel Machek
2014-08-25 12:09 ` Jaehoon Chung
2014-08-25 12:11 ` Jaehoon Chung
2014-08-26 10:19 ` Pavel Machek [this message]
2014-08-27 3:11 ` Jaehoon Chung
2014-08-27 11:56 ` Pavel Machek
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=20140826101923.GA13619@amd \
--to=pavel@denx.de \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tgih.jun@samsung.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).