devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2-l0cyMroinI0@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	pawel.moll-5wv7dgnIgG8@public.gmane.org,
	mark.rutland-5wv7dgnIgG8@public.gmane.org,
	ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
	galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
	bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 2/2] PCI: keystone: update to support multiple pci ports
Date: Wed, 10 Sep 2014 10:28:32 -0400	[thread overview]
Message-ID: <54106010.8040206@ti.com> (raw)
In-Reply-To: <3814561.AbrslYBNjb@wuerfel>

On 09/10/2014 04:22 AM, Arnd Bergmann wrote:
> On Tuesday 09 September 2014 18:50:13 Murali Karicheri wrote:
>> My mistake. It is the device ID, not vendor ID. The PCI driver supports
>> PCI h/w on K2HK, K2E and K2L SoCs for which PCI device IDs are assigned as
>>
>> +#define PCIE_RC_K2HK           0xb008
>> +#define PCIE_RC_K2E            0xb009
>> +#define PCIE_RC_K2L            0xb00a
>> +
>>
>> and the same driver code runs on all these h/w. The device ID is not
>> filled in by default by the h/w, in the config space of the RC at offset
>> 1000h "VENDOR_DEVICE_ID Vendor and Device Identification Register".
>> Same is available in a seperate SoC register whose offset is specified
>> by index 2. This is read by driver and updated in the config space. The
>> Vendor ID is however set by default.
>>
>> There is a mrrs PCI quirk required for Keystone PCI which depends on
>> this vendor ID to be filled correctly as it match vendor id/ device id
>> of the bridge device to apply the quirk.
>>
>> Hope this clarify your question.
>
> Ok, I understand now. Yes, this makes sense, though I wonder if it would
> have been easier to handle the quirk in a different way based on the
> driver rather than the PCI ID. It's probably not worth revisiting though,
> unless Bjorn wants to see it done differently now.

Bjorn has reviewed the quirk patch and wanted to check the device ID and 
vendor ID to avoid applying the quirck when bridge is non TI and same 
device ID.

So support for two PCI port requires only the PCI device id related 
change. So I will modify the subject and commit log to reflect the same 
and re-send the patch.

Thanks again Arnd for your comments.

Regards,

Murali
>
> 	Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-09-10 14:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 20:17 [PATCH v2 1/2] PCI: keystone: remove handle of PCI mode configuration Murali Karicheri
2014-09-09 20:17 ` [PATCH v2 2/2] PCI: keystone: update to support multiple pci ports Murali Karicheri
2014-09-09 20:28   ` Arnd Bergmann
2014-09-09 20:42     ` Murali Karicheri
2014-09-09 21:09       ` Arnd Bergmann
2014-09-09 21:49         ` Murali Karicheri
2014-09-09 21:51           ` Murali Karicheri
     [not found]           ` <540F75DF.5050904-l0cyMroinI0@public.gmane.org>
2014-09-09 21:52             ` Arnd Bergmann
2014-09-09 22:50               ` Murali Karicheri
2014-09-10  8:22                 ` Arnd Bergmann
2014-09-10 14:28                   ` Murali Karicheri [this message]
2014-09-09 20:22 ` [PATCH v2 1/2] PCI: keystone: remove handle of PCI mode configuration Arnd Bergmann

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=54106010.8040206@ti.com \
    --to=m-karicheri2-l0cymroini0@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).