On Fri, 11 Jun 2010 12:25:32 +0900 Kyungmin Park <kmpark@xxxxxxxxxxxxx> wrote: > On Fri, Jun 11, 2010 at 9:42 AM, Ben Dooks <ben-linux@xxxxxxxxx> wrote: > > On Thu, Jun 10, 2010 at 01:43:19PM -0700, akpm@xxxxxxxxxxxxxxxxxxxx wrote: > >> > >> The patch titled > >> __ __ __SDHCI: add no hi-speed bit quirk support > >> has been added to the -mm tree. __Its filename is > >> __ __ __sdhci-add-no-hi-speed-bit-quirk-support.patch > >> > >> Before you just go and hit "reply", please: > >> __ __a) Consider who else should be cc'ed > >> __ __b) Prefer to cc a suitable mailing list as well > >> __ __c) Ideally: find the original patch on the mailing list and do a > >> __ __ __ reply-to-all to that, adding suitable additional cc's > >> > >> *** Remember to use Documentation/SubmitChecklist when testing your code *** > >> > >> See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find > >> out what to do about this > >> > >> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ > >> > >> ------------------------------------------------------ > >> Subject: SDHCI: add no hi-speed bit quirk support > >> From: Kyungmin Park <kmpark@xxxxxxxxxxxxx> > >> > >> Some SDHCI controllers like s5pc110 don't have an HISPD bit in the HOSTCTL > >> register. > > > > It would be nice for someone at Samsung to (a) explain the differences > > from the base SDHCI spec for all their hardware (the databooks are often > > vague in this area) and (b) for the information for the extra registers > > this IP block has to be explained in more detail (and the platform code > > checked for this too). > > I hope also. Going back over this dicussion, I get the impression that nothing really got resolved or finished. So it is far from clear that I should send these: s5pc110-sdhci-s3c-can-override-host-capabilities.patch s5pc110-sdhci-s3c-support-on-s5pc110.patch sdhci-add-no-hi-speed-bit-quirk-support.patch upstream. Could we please revisit all of this ASAP? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html