From: Alexander Duyck <alexander.duyck@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH] ixgbe: add new bus type for intergrated I/O interface (IOSF)
Date: Thu, 18 Jun 2015 13:03:25 -0700 [thread overview]
Message-ID: <5583240D.2070909@gmail.com> (raw)
In-Reply-To: <F6FB0E698C9B3143BDF729DF222866469130C37A@ORSMSX110.amr.corp.intel.com>
On 06/18/2015 12:50 PM, Skidmore, Donald C wrote:
>
>> -----Original Message-----
>> From: Alexander Duyck [mailto:alexander.h.duyck at redhat.com]
>> Sent: Thursday, June 18, 2015 12:45 PM
>> To: Skidmore, Donald C; intel-wired-lan at lists.osuosl.org
>> Subject: Re: [Intel-wired-lan] [net-next PATCH] ixgbe: add new bus type for
>> intergrated I/O interface (IOSF)
>>
>> On 06/18/2015 10:24 AM, Donald C Skidmore wrote:
>>> With this patch we add support for a new bus type
>> ixgbe_bus_type_internal.
>>> X550em devices use IOSF and not PCIe bus so this new type is to
>>> accommodate them.
>>>
>>> Signed-off-by: Donald C Skidmore <donald.c.skidmore@intel.com>
>>> ---
>>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 11 ++++++++++-
>>> drivers/net/ethernet/intel/ixgbe/ixgbe_type.h | 1 +
>>> drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 1 +
>>> 3 files changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>>> b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>>> index 5f1b06a..dd53abd 100644
>>> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>>> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>>> @@ -246,11 +246,19 @@ static inline bool ixgbe_pcie_from_parent(struct
>> ixgbe_hw *hw)
>>> static void ixgbe_check_minimum_link(struct ixgbe_adapter *adapter,
>>> int expected_gts)
>>> {
>>> + struct ixgbe_hw *hw = &adapter->hw;
>>> int max_gts = 0;
>>> enum pci_bus_speed speed = PCI_SPEED_UNKNOWN;
>>> enum pcie_link_width width = PCIE_LNK_WIDTH_UNKNOWN;
>>> struct pci_dev *pdev;
>>>
>>> + /* Some devices are not connected over PCIe and thus do not
>> negotiate
>>> + * speed. These devices do not have valid bus info, and thus any
>> report
>>> + * we generate may not be correct.
>>> + */
>>> + if (hw->bus.type == ixgbe_bus_type_internal)
>>> + return;
>>> +
>>> /* determine whether to use the parent device */
>>> if (ixgbe_pcie_from_parent(&adapter->hw))
>>> pdev = adapter->pdev->bus->parent->self; @@ -8844,9
>> +8852,10 @@
>>> skip_sriov:
>>> hw->eeprom.ops.read(hw, 0x2d, &adapter->eeprom_verl);
>>>
>>> /* pick up the PCI bus settings for reporting later */
>>> - hw->mac.ops.get_bus_info(hw);
>>> if (ixgbe_pcie_from_parent(hw))
>>> ixgbe_get_parent_bus_info(adapter);
>>> + else
>>> + hw->mac.ops.get_bus_info(hw);
>>>
>>> /* calculate the expected PCIe bandwidth required for optimal
>>> * performance. Note that some older parts will never have enough
>>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_type.h
>>> b/drivers/net/ethernet/intel/ixgbe/ixgbe_type.h
>>> index 19271e5..37df15f 100644
>>> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_type.h
>>> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_type.h
>>> @@ -3067,6 +3067,7 @@ enum ixgbe_bus_type {
>>> ixgbe_bus_type_pci,
>>> ixgbe_bus_type_pcix,
>>> ixgbe_bus_type_pci_express,
>>> + ixgbe_bus_type_internal,
>>> ixgbe_bus_type_reserved
>>> };
>>>
>> Are there really any parts that are listed as using a pci or pcix type?
>> If not you could probably drop those types from the enum since they don't
>> add any value.
> I really like that idea. :) Still wouldn't that be worth of its own patch, even though it would be really small patch?
>
> Thanks,
> -Don
Yeah, probably doesn't need to block this one, but is something that
should probably be done as a clean-up eventually.
- Alex
next prev parent reply other threads:[~2015-06-18 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 17:24 [Intel-wired-lan] [net-next PATCH] ixgbe: add new bus type for intergrated I/O interface (IOSF) Donald C Skidmore
2015-06-18 19:44 ` Alexander Duyck
2015-06-18 19:50 ` Skidmore, Donald C
2015-06-18 20:03 ` Alexander Duyck [this message]
2015-06-18 20:10 ` Skidmore, Donald C
2015-08-06 17:46 ` Schmitt, Phillip J
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=5583240D.2070909@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=intel-wired-lan@osuosl.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 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.