Message ID | 20230331214549.756660-1-ahalaney@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | Add EMAC3 support for sa8540p-ride | expand |
On Fri, Mar 31, 2023 at 04:45:37PM -0500, Andrew Halaney wrote: > This is a forward port / upstream refactor of code delivered > downstream by Qualcomm over at [0] to enable the DWMAC5 based > implementation called EMAC3 on the sa8540p-ride dev board. > > From what I can tell with the board schematic in hand, > as well as the code delivered, the main changes needed are: > > 1. A new address space layout for /dwmac5/EMAC3 MTL/DMA regs > 2. A new programming sequence required for the EMAC3 base platforms > > This series makes the change for 1 above as well as other housekeeping items > such as converting dt-bindings to yaml, etc. > > As requested[1], it has been split up by compile time / maintainer tree. > I will post a link to the associated devicetree changes that together > with this series get the hardware functioning. As promised: https://lore.kernel.org/netdev/20230331215804.783439-1-ahalaney@redhat.com/T/#t Thanks in advance for any reviews! - Andrew
On Fri, 31 Mar 2023 17:06:13 -0500 Andrew Halaney wrote:
> As promised: https://lore.kernel.org/netdev/20230331215804.783439-1-ahalaney@redhat.com/T/#t
Patch 12 never made it to netdev or lore :(
On Fri, Mar 31, 2023 at 09:55:04PM -0700, Jakub Kicinski wrote: > On Fri, 31 Mar 2023 17:06:13 -0500 Andrew Halaney wrote: > > As promised: https://lore.kernel.org/netdev/20230331215804.783439-1-ahalaney@redhat.com/T/#t > > Patch 12 never made it to netdev or lore :( > Well, that's no good as I definitely want some eyes on that one :( I've already gotten _some_ reviews on the earlier patches in v3, I am going to absorb anything super quick into a v4 today, then send that out, maybe copy pasting larger questions I have yet to respond to? Seems like an ok approach.. not having the full solution in hand is crummy for review. Let me know if you think that's a bad call and just a resend is better. Sorry, not sure where I messed that up Friday evening when writing changelogs etc.