All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Tutorial for "drivers/mmc/*"?
Date: Thu, 7 Jan 2021 15:54:19 -0500	[thread overview]
Message-ID: <20210107205419.GG2094049@errol.ini.cmu.edu> (raw)

Hi,

I'm debugging a driver for a (fpga-based soft core) microSD card Linux
device, and the existing driver (in drivers/mmc/host/...) makes sense
at first sight, but, either due to shortcomings in the softcore
(Verilog by way of Migen) "hardware", or the actual Linux driver
itself, suffers from intermittent data transfer errors.

I find myself wishing I could get a top-down idea of how the Linux mmc
layer is put together, so I could examine the driver in question with
a critical eye, rather than my current approach, which is best described
as "blind-man attempts to comprehend an elephant by touching various
locations on its body, hoping the collected experiences will suddenly
come into focus and begin to make sense". :D

This latter approach gives me information that makes sense on first
sight, when taken uncritically, but doesn't help me figure out the
"unknown unknowns" :)

The alternative, of course, would be to read the actual source code in
"drivers/mmc/core/..." until I "know it by heart", and then look at my
(and a few other existing) drivers in "drivers/mmc/host/..." to try and
get an idea of what I'm missing.

I'll go with the latter if necessary, but would prefer a gentler
introduction to "drivers/mmc". Any (link, pointer to) a tutorial,
assuming one exists, would be MUCH appreciated!

Thanks,
--Gabriel

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2021-01-07 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 20:54 Gabriel L. Somlo [this message]
2021-01-09  4:27 ` Tutorial for "drivers/mmc/*"? Randy Dunlap
2021-01-09  4:27   ` Randy Dunlap

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=20210107205419.GG2094049@errol.ini.cmu.edu \
    --to=gsomlo@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.