From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: linux-ide@vger.kernel.org, jon@ngndg.com,
LKML <linux-kernel@vger.kernel.org>,
Saeed Bishara <saeed@marvell.com>
Subject: Re: Sata-MV, Intergated Sata Device Support
Date: Mon, 25 Feb 2008 19:17:09 -0500 [thread overview]
Message-ID: <47C35A85.3020307@garzik.org> (raw)
In-Reply-To: <47C3585D.8070701@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> Jon Li wrote:
>>> Hello,
>>>
>>> I am curious as to whether there are plans to add support for integrated
>>> sata devices. I personally want to add support for a 60x1C0 based
>>> device (pci:id = 0x5182). I think adding support should be relatively
>>> simple, except for a few issues outlined below.
>>>
>>> In the original mvSata.c (ver3.4) that has 0x5182 support, the config
>>> space is as such:
>>>
>>> case MV_SATA_DEVICE_ID_5182:
>>> pAdapter->numberOfChannels = MV_SATA_5182_PORT_NUM;
>>> pAdapter->numberOfUnits = 1;
>>> pAdapter->portsPerUnit = 2;
>>> pAdapter->sataAdapterGeneration = MV_SATA_GEN_IIE;
>>> /*The integrated sata core chip based on 60x1 C0*/
>>> pAdapter->chipIs60X1C0 = MV_TRUE;
>>> pAdapter->hostInterface = MV_HOST_IF_INTEGRATED;
>>> pAdapter->mainMaskOffset = 0x20024; /*the iobaseaddress is
>>> 0x60000*/
>>> pAdapter->mainCauseOffset = 0x20020;
>>> break;
>>>
>>> I have not yet figured out how all these values are defined in sata-mv.c
>>> (ver 0.8). Specifically, where do I define "numberOfChannels" which
>>> should equal 2, and "numberOfUnits" which obviously equals 1?
>>>
>>> I have a current config space (not completed) for sata-mv.c which is:
>>>
>>> { /* chip_5182 */
>>> .sht = &mv_sht,
>>> .flags = (MV_COMMON_FLAGS | MV_6XXX_FLAGS |
>>> MV_FLAG_DUAL_HC),
>>> .pio_mask = 0x1f, /* pio0-4 */
>>> .udma_mask = 0x7f, /* udma0-6 */
>>> .port_ops = &mv6_ops,
>>> },
> ...
>
> Saeed: isn't this what your SOC patches already implemented for us?
> As near as I can tell, sata_mv now already has support for the 60x1C0.
Saeed's stuff didn't support PCI though, and Jon Li is definitely
talking about PCI...
Jeff
next prev parent reply other threads:[~2008-02-26 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 21:51 Sata-MV, Intergated Sata Device Support Jon Li
2008-02-25 23:40 ` Jeff Garzik
2008-02-26 0:07 ` Mark Lord
2008-02-26 0:17 ` Jeff Garzik [this message]
2008-02-26 11:39 ` saeed
2008-02-26 15:55 ` Mark Lord
2008-03-04 18:26 ` Mark Lord
2008-03-04 18:42 ` Byron Bradley
2008-03-04 21:18 ` Mark Lord
2008-03-05 13:07 ` Jeff Garzik
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=47C35A85.3020307@garzik.org \
--to=jeff@garzik.org \
--cc=jon@ngndg.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saeed@marvell.com \
/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.