All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: SATA AHCI controller detection during PCI enumeration
Date: Wed, 25 Jun 2014 10:25:27 -0400	[thread overview]
Message-ID: <53AADBD7.4070302@ti.com> (raw)
In-Reply-To: <CAHM4w1kSH0C3N3rfy9yCBNwUXZTJmzZt5rnsLBbgjG9DLY9L2A@mail.gmail.com>

On 06/25/2014 12:01 AM, Pratyush Anand wrote:
> On Tue, Jun 24, 2014 at 7:56 PM, Murali Karicheri<m-karicheri2@ti.com>  wrote:
>> All,
>>
>> I have a board with PCI controller connected to a Marvell AHCI controller,
>> 88SE9182 connected to a PCIe bus and the PCI scan doesn't show up the SATA
>> end point. My question is in order to detect the EP,
>> is it expected to have a hard drive connected to the SATA port?
>
> No
>
>> Currently with and without the SATA connected, the PCI scan doesn't
>> show up the device. Also is there any other requirements at the
>> hardware level to detect this SATA controller.
>
> Does this PCIe2SATA card work with standard PC?
>
> I do not know about this Marvell controller, but I remember one
> silicon image controller which worked with only Gen1 host port.
> You may ask card vendor if there is any such limitation.
>
Pratyush,

Thanks for the reply. I will touch base with the Vendor on this.

Murali

> ~Pratyush
>
>>
>> Thanks in advance for your reply.
>>
>> Murali
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2014-06-25 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 14:26 SATA AHCI controller detection during PCI enumeration Murali Karicheri
2014-06-25  4:01 ` Pratyush Anand
2014-06-25 14:25   ` Murali Karicheri [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=53AADBD7.4070302@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=pratyush.anand@gmail.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.