public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] any value in moving ATA/SATA stuff from drivers/block to headers?
Date: Mon, 28 Dec 2015 08:02:26 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1512280757550.9197@localhost> (raw)


  currently poking around in drivers/block, adding a driver for
another silicon image drive, and noticed that sata_sil3114.h has some
content that looks more appropriate for a generic ATA/SATA header
file.

 for example, this snippet:

/* Missing ata defines */
#define ATA_CMD_STANDBY                 0xE2
#define ATA_CMD_STANDBYNOW1             0xE0
#define ATA_CMD_IDLE                    0xE3
#define ATA_CMD_IDLEIMMEDIATE   0xE1

seems already covered by include/libata.h, while the earlier structure
definitions in that file:

struct sata_ioports {
... snip ...
};

struct sata_port {
... snip ...
};

also look like they could be moved to a generic SATA-related header
file. does that make any sense or sound like it has any value?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2015-12-28 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 13:02 Robert P. J. Day [this message]
2016-01-14 20:29 ` [U-Boot] any value in moving ATA/SATA stuff from drivers/block to headers? Tom Rini

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=alpine.LFD.2.20.1512280757550.9197@localhost \
    --to=rpjday@crashcourse.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox