On Thu, 2019-02-14 at 09:14 +0100, Ulf Hansson wrote:
> On Thu, 14 Feb 2019 at 03:14, Chaotian Jing
> wrote:
> >
> > On Wed, 2019-02-13 at 13:08 +0100, Ulf Hansson wrote:
> > > On Wed, 13 Feb 2019 at 10:07, Chaotian Jing
> > > wrote:
> > > >
> > > > mmc_hs400_to_hs200() begins with the card and
On Thu, 14 Feb 2019 at 03:14, Chaotian Jing wrote:
>
> On Wed, 2019-02-13 at 13:08 +0100, Ulf Hansson wrote:
> > On Wed, 13 Feb 2019 at 10:07, Chaotian Jing
> > wrote:
> > >
> > > mmc_hs400_to_hs200() begins with the card and host in HS400 mode.
> > > Therefore, any commands sent to the card sho
On Wed, 2019-02-13 at 13:08 +0100, Ulf Hansson wrote:
> On Wed, 13 Feb 2019 at 10:07, Chaotian Jing
> wrote:
> >
> > mmc_hs400_to_hs200() begins with the card and host in HS400 mode.
> > Therefore, any commands sent to the card should use HS400 timing.
> > reduce clock frequency to 50Mhz but with
On Wed, 13 Feb 2019 at 10:07, Chaotian Jing wrote:
>
> mmc_hs400_to_hs200() begins with the card and host in HS400 mode.
> Therefore, any commands sent to the card should use HS400 timing.
> reduce clock frequency to 50Mhz but without host timming change
> may cause CMD6 response CRC error. becaus
mmc_hs400_to_hs200() begins with the card and host in HS400 mode.
Therefore, any commands sent to the card should use HS400 timing.
reduce clock frequency to 50Mhz but without host timming change
may cause CMD6 response CRC error. because host still running at
hs400 mode, and it's hard to find a su
5 matches
Mail list logo