From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: DW MMC multislot support
Date: Fri, 30 Mar 2018 15:37:39 +0000 [thread overview]
Message-ID: <1522424259.32101.7.camel@synopsys.com> (raw)
Hi,
I have plans to add multislot support to DesignWare MMC driver.
As of today I have proof of concept for multislot DW MMC driver with two slots working
simultaneously:
I reverted all commits which remove previous implementation of "pseudo-multislot"
and add all required steps for changing slot number to __dw_mci_start_request function.
But I have several issues with set_ios function in multislot mode (as each slot
is registered as separate mmc host):
1) We can change clock for slot 1 while slot 0 is active.
2) We can disable one slot (by calling set_ios with 'power_mode' == MMC_POWER_OFF)
which cause clock disable for all slots.
3) We can enable one slot (by calling set_ios with 'power_mode' == MMC_POWER_ON)
which cause DMA and FIFO reset while another slot is active.
And so on...
Here is my ideas how to fix this:
1) In set_ios function we can simply store parameters
(like clock speed/timings/bus width) to corresponding slot structure and apply
them only in the beginning of __dw_mci_start_request function if current slot is
changed.
Another option is to choose maximum clock which is suitable for both slots
instead of clock switch on every slot change.
2) Do all actions for slot disabling ('power_mode' == MMC_POWER_OFF) only if
others slots are disabled too.
3) Do all actions for slot enabling ('power_mode' == MMC_POWER_ON) only if
no slots are enabled.
Maybe you have any comments or remarks about this?
All comments and suggestions are more than welcome.
--
Eugeniy Paltsev
reply other threads:[~2018-03-30 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1522424259.32101.7.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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).