RE: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-10 Thread Madalin Bucur
> -Original Message- > From: Patrick Havelange > Sent: 10 December 2020 12:06 > To: Madalin Bucur ; David S. Miller > ; Jakub Kicinski ; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net 1/4] net: freescale/fman: Split the main resource

Re: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-10 Thread Patrick Havelange
On 2020-12-10 10:05, Madalin Bucur wrote: -Original Message- From: Patrick Havelange [snipped] But then that change would not be compatible with the existing device trees in already existing hardware. I'm not sure how to handle that case properly. One needs to be backwards

RE: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-10 Thread Madalin Bucur
> -Original Message- > From: Patrick Havelange > Sent: 10 December 2020 10:49 > To: Madalin Bucur ; David S. Miller > ; Jakub Kicinski ; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net 1/4] net: freescale/fman: Split the main resource

Re: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-10 Thread Patrick Havelange
On 2020-12-09 19:55, Madalin Bucur wrote: -Original Message- From: Patrick Havelange Sent: 09 December 2020 16:17 To: Madalin Bucur ; David S. Miller ; Jakub Kicinski ; net...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH net 1/4] net: freescale/fman: Split the main

RE: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-09 Thread Madalin Bucur
> -Original Message- > From: Patrick Havelange > Sent: 09 December 2020 16:17 > To: Madalin Bucur ; David S. Miller > ; Jakub Kicinski ; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net 1/4] net: freescale/fman: Split the main resource

Re: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-09 Thread Patrick Havelange
area. I'm assuming this is the problem you are trying to address here, besides the stack corruption issue. Yes exactly. I did not add this behaviour (having a main region and subdrivers using subregions), I'm just trying to correct what is already there. For example: this is some content of

RE: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-09 Thread Madalin Bucur
> -Original Message- > From: Patrick Havelange > Sent: 08 December 2020 16:56 > To: Madalin Bucur ; David S. Miller > ; Jakub Kicinski ; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net 1/4] net: freescale/fman: Split the main resource

Re: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-08 Thread Patrick Havelange
/fman: Split the main resource region reservation The main fman driver is only using some parts of the fman memory region. Split the reservation of the main region in 2, so that the other regions that will be used by fman-port and fman-mac drivers can be reserved properly and not be in conflict

RE: [PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-03 Thread Madalin Bucur
> -Original Message- > From: Patrick Havelange > Sent: 03 December 2020 15:51 > To: Madalin Bucur ; David S. Miller > ; Jakub Kicinski ; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Cc: Patrick Havelange > Subject: [PATCH net 1/4] net: freescale/fman:

[PATCH net 1/4] net: freescale/fman: Split the main resource region reservation

2020-12-03 Thread Patrick Havelange
The main fman driver is only using some parts of the fman memory region. Split the reservation of the main region in 2, so that the other regions that will be used by fman-port and fman-mac drivers can be reserved properly and not be in conflict with the main fman reservation. Signed-off-by: