Re: Source code organization

2022-10-21 Thread Billie Alsup (balsup)
> From: Greg KH > Platform drivers are the "catch all" for where you have to talk to tiny > hardware-specific devices.  That's normally not an i2c controller. I always thought of these as hardware specific devices, as the FPGA images are hardware specific. Yes, the top level is currently a "rea

Re: Source code organization

2022-10-20 Thread Greg KH
On Fri, Oct 21, 2022 at 01:51:48AM +, Billie Alsup (balsup) wrote: > > > From: Greg KH > >    - is this something else?  Then pick a place and submit a patch > >  and people will tell you if you got it wrong :) > > I think this is going to be my strategy, except per a separate re

Re: Source code organization

2022-10-20 Thread Billie Alsup (balsup)
> From: Greg KH >    - is this something else?  Then pick a place and submit a patch >  and people will tell you if you got it wrong :) I think this is going to be my strategy, except per a separate recommendation, I will put it in drivers/platform/cisco, similar to the existing chr

Re: Source code organization

2022-10-20 Thread Greg KH
On Mon, Oct 17, 2022 at 06:00:40PM +, Billie Alsup (balsup) wrote: > I have a set of drivers that I would like to upstream. These are primarily > MFD style drivers supporting Cisco-8000 FPGAs. The devices can be > instantiated through multiple top level drivers, which provide the access > mec

Source code organization

2022-10-17 Thread Billie Alsup (balsup)
I have a set of drivers that I would like to upstream. These are primarily MFD style drivers supporting Cisco-8000 FPGAs. The devices can be instantiated through multiple top level drivers, which provide the access mechanism for the MFD driver. For example, an FPGA can be accessed via PCI, or vi