From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] : Suggestions for SPI driver pusher
Date: Fri, 9 Aug 2013 08:04:01 -0400 [thread overview]
Message-ID: <5204DAB1.2010606@ti.com> (raw)
In-Reply-To: <5204ACE7.6080203@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/09/2013 04:48 AM, Jagan Teki wrote:
> Hi,
>
> FYI: I am trying to prepare the spi driver code to more readable.
> As each spi driver has a common set of calls.
>
> << header file inclusion >> << Register bit masks >>
>
> << MISC macro definitions >>
>
> << controller reg structure >>
>
> << controller private slave structure >>
>
> << inline func defination >>
>
> << spi_xfer_sub() >>
>
> << spi_setup_slave_sub >>
>
> << spi_cs_is_valid >>
>
> << spi_cs_activate >>
>
> << spi_cs_deactivate >>
>
> << spi_init >>
>
> << spi_setup_slave >> { spi_setup_slave_sub() }
>
> << spi_free_slave >>
>
> << spi_claim_bus >>
>
> << spi_release_bus >>
>
> << spi_xfer code >> { spi_xfer_sub() }
>
> I am just trying to do the above format at-least from the drivers
> which are pushing now onwards.
>
> Please see the reff driver
> http://git.denx.de/?p=u-boot/u-boot-spi.git;a=commitdiff;h=1465d055f9d7a81edacf30c9d20a1b51dfcbfa8d
Sounds
>
>
like a good idea to me.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSBNqxAAoJENk4IS6UOR1WFQ0P/RfYjz+GucnlBJHAlwJZCiRZ
OImki6N+lMdYdQZKPJ93parZlWXcv+txSNxXhzDcpgKkm40nTYLlu606Ucw10yXW
YcGm3IjBgT3d2/T3QcXgYD0wlfUCwOIyu0HpbfOG6VuFvd2XkePY1iVWObEMcREU
xqr5bab0LM9QsPaggylYb7wm1oBy+SXrCJnVxKWqiMVTohI3LHNHqZgxMUoIxcba
/pWEviQdQzwq4KROYZq6IDKUZfsATgnsWhxzhfy4CEMmmzdgPxYczvsSo5IcED37
SJ6m4luA664oUorU9VnJs66mRNz+3nreY+W7/QjqrgY7PiWMiKOt72qSPvbNiqWi
VlCqBkqLTGs0T8THKN2E4JfzcYCBwD48+xItJpQ8ZrIWLRxHhI2pQXhx5Ov7qUsT
iHbi/NZ/oyvTcdDfZ/Ohles1x5r+u/rI7Ya/Q+uKCg/kZnJHKlwgExLM9MlmXG6q
Edhra+hNvWaWwFVXJE5/tfa0UQCJg9pLDM5mVCoSbaftpiCpemgt1/xIMGhfPSwj
dwc+2iA2V8zIgJZVXoppGBmp2WJN46ztb81gcu+inYpaAPsYE8FIf8ilZa5gBHUl
HKCijZ1wpQ4I2KkGMJhdlyIw3Nul1l9QH5Q3kMECZt8CeD1sfh+qBE0ULcgTJd8U
g6VkFlFo5lHHDTke7RMZ
=MMJh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-08-09 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 8:48 [U-Boot] : Suggestions for SPI driver pusher Jagan Teki
2013-08-09 12:04 ` Tom Rini [this message]
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=5204DAB1.2010606@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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.