On Tue, Jun 24, 2014 at 8:52 AM, Tomasz Figa t.f...@samsung.com wrote:
Hi Daniel,
[adding Ulf, Chris and Mike to the discussion]
On 24.06.2014 11:48, Daniel Drake wrote:
sdhci_s3c_set_clock is called from sdhci_do_set_ios with interrupts
disabled, and this calls into
On 24 June 2014 17:52, Tomasz Figa t.f...@samsung.com wrote:
Hi Daniel,
[adding Ulf, Chris and Mike to the discussion]
On 24.06.2014 11:48, Daniel Drake wrote:
sdhci_s3c_set_clock is called from sdhci_do_set_ios with interrupts
disabled, and this calls into sdhci_s3c_consider_clock().
The
Hi,
It's also related with clock-gating.
Mainline kernel is using the clkgate-delay = 0 by default.
If we use this value, Every request time should be gated/ungated...
Then it may be faced the race-condition...In my experiment, it occasionally
occurred the CRC error or other problem.
And it's
sdhci_s3c_set_clock is called from sdhci_do_set_ios with interrupts
disabled, and this calls into sdhci_s3c_consider_clock().
The patch mmc: sdhci-s3c: Cache bus clock rates addressed some
scheduling while atomic in this function, but there are more issues
here, seen while testing 3.16-rc2 on
Hi Daniel,
[adding Ulf, Chris and Mike to the discussion]
On 24.06.2014 11:48, Daniel Drake wrote:
sdhci_s3c_set_clock is called from sdhci_do_set_ios with interrupts
disabled, and this calls into sdhci_s3c_consider_clock().
The patch mmc: sdhci-s3c: Cache bus clock rates addressed some