Dong, Chuanxiao had written, on 10/28/2010 02:46 AM, the following:
Upstream status:
Patch 0001: implemented eMMC4.4 hardware reset feature in MMC core
layer.
http://marc.info/?t=128801640800002&r=1&w=2
Patch 0002: implemented hardware reset callback for sdhci layer.
cant seem to find this :(
Patch 0003: implemented the real reset eMMC card part in sdhci host
controller
driver.
neither this.
I did send them out. Maybe they go into your junk mail...Sorry for that.
I am personally not subscribed to linux-mmc list, I just checked the
linux-mmc archive with the subject
patch2:
http://marc.info/?l=linux-mmc&w=2&r=1&s=implemented+hardware+reset+callba
ck&q=t
Patch3:
http://marc.info/?l=linux-mmc&w=2&r=1&s=implemented+the+real+reset+eMMC
&q=t
maybe you could post the
https://patchwork.kernel.org/project/linux-mmc/list/ link instead to
help us- I am probably going blind now a days with caffeine and cant
seem to find it :(
Several days ago I just submitted one patch to linux-mmc mail list which is
[Wrapping the email for mail clients such as mine :)]
>the same with this submission but without the patch3. You can find it by
> https://patchwork.kernel.org/patch/267032/. By sending this patch to
https://patchwork.kernel.org/patch/267032/ ==
http://marc.info/?t=128801640800002&r=1&w=2
>linux-mmc list, I want to get some advice on whether it is suitable for
>driver to set RST_n_FUNCTION bit in ext_csd register. But till now I did
>not get any response. Hope this would be also helpful to you.
yeah I can guess, given that it is 2.6.37-rc1 merge window, maintainers
and folks are bit busy pushing to Linus their changes.
Interestingly I do see MMC 4.4 spec patch here:
http://marc.info/?l=linux-mmc&m=127866033408381&w=2
Unfortunately, am personally just a newbie on mmc, cant help much
specifically on it, except that the discussion probably should take
place in linux-mmc ML and probably not on MeeGo list ;)..
my only concern being:
http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors - quote:
"The MeeGo project really wants Device drivers and other kernel code to
be developed for, and integrated in, the kernel.org kernel as maintained
by Linus Torvalds. Every patch we carry has a cost for us, and we do not
want to carry long term patches.
So if you want to develop a device driver for MeeGo, please develop your
driver for, and submit your driver to, the kernel.org Linux kernel. In
fact, this is a requirement for MeeGo! "
It is a good approach - we dont take patches to MeeGo kernel which are
not posted upstream, aka if there are review comments there, we'd have
to fix them anyways - as they are relevant to us in MeeGo as well, in
effect it implies that a patch would be in some shape upstream-able
before getting into MeeGo kernel - much larger review base, much better
quality, albiet a bit slower..
Relevance of my above rambling is this: patch2&3 is not posted upstream,
and not got real quality reviews - may not be good for us in MeeGo perhaps?
--
Regards,
Nishanth Menon
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
