Re: [PATCH iwl-next v3 00/15] Introduce iXD driver

[Jacob Keller <jacob.e.keller@intel.com>]

On 5/12/2025 6:21 AM, Larysa Zaremba wrote:
> On Mon, May 12, 2025 at 01:49:06PM +0100, Simon Horman wrote:
>> On Fri, May 09, 2025 at 03:42:57PM +0200, Larysa Zaremba wrote:
>>> This patch series adds the iXD driver, which supports the Intel(R)
>>> Control Plane PCI Function on Intel E2100 and later IPUs and FNICs.
>>> It facilitates a centralized control over multiple IDPF PFs/VFs/SFs
>>> exposed by the same card. The reason for the separation is to be able
>>> to offload the control plane to the host different from where the data
>>> plane is running.
>>>
>>> This is the first phase in the release of this driver where we implement the
>>> initialization of the core PCI driver. Subsequent phases will implement
>>> advanced features like usage of idpf ethernet aux device, link management,
>>> NVM update via devlink, switchdev port representors, data and exception path,
>>> flow rule programming, etc.
>>
>> Hi Larysa,
>>
>> I am having a bit of trouble figuring out where to cleanly apply this
>> series to. Could you help me out?
> 
> Tree did change quite a bit in a short span of time between me fetching and 
> sending, sorry for the trouble.
> 
> The base commit is 10f540c09cf9 "ice: default to TIME_REF instead of TXCO on 
> E825-C". In case you cannot access it, I have pushed the tree to my github.
> 
> https://github.com/walking-machine/linux/commits/ixd_phase1_iwl_v3
> 
> This version is probably much closer to what would be in dev-queue eventually, 
> compared to a properly rebased one. Some patches were pulled out of dev-queue 
> because of validation problems, but should be back pretty soon, as far as I 
> know. Those patches are the reason why I have an additional fix in the github 
> tree.

Thanks for sharing the info!

I think we also have been holding off on putting stuff onto dev-queue
because of the conflicts, and wanting to finish up some of the existing
series. That's resulted in a lot of back and forth as some of the larger
refactors have a lot of places to conflict.