Message ID | 87bmzqbilu.fsf@free-electrons.com |
---|---|
State | New |
Headers | show |
On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote: > mvebu soc for 4.9 (part 1) > > - irq cleanup for old mvebu SoC > - Convert orion5x based SoC Netgear WNR854T to devicetree > Pulled into next/soc, thanks! Arnd
On Monday, September 19, 2016 11:46:22 PM CEST Arnd Bergmann wrote: > On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote: > > mvebu soc for 4.9 (part 1) > > > > - irq cleanup for old mvebu SoC > > - Convert orion5x based SoC Netgear WNR854T to devicetree > > > > Pulled into next/soc, thanks! Sorry, backed out again after seeing the PCI stuff on the WNR854T in there. I thought the plan was to leave out PCI support from the DT based machine file, and leave the old board in place, or am I missing something? Arnd
Hi Arnd, On lun., sept. 19 2016, Arnd Bergmann <arnd@arndb.de> wrote: > On Monday, September 19, 2016 11:46:22 PM CEST Arnd Bergmann wrote: >> On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote: >> > mvebu soc for 4.9 (part 1) >> > >> > - irq cleanup for old mvebu SoC >> > - Convert orion5x based SoC Netgear WNR854T to devicetree >> > >> >> Pulled into next/soc, thanks! > > Sorry, backed out again after seeing the PCI stuff on the WNR854T in > there. I thought the plan was to leave out PCI support from the DT > based machine file, and leave the old board in place, or am I > missing something? I might have overlooked the thread, I thouhgt the state of the patch was OK as is, and further changes can be done later. So it seems that it will be 4.10 material. Gregory
On Tuesday, September 20, 2016 9:25:51 AM CEST Gregory CLEMENT wrote: > Hi Arnd, > > On lun., sept. 19 2016, Arnd Bergmann <arnd@arndb.de> wrote: > > > On Monday, September 19, 2016 11:46:22 PM CEST Arnd Bergmann wrote: > >> On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote: > >> > mvebu soc for 4.9 (part 1) > >> > > >> > - irq cleanup for old mvebu SoC > >> > - Convert orion5x based SoC Netgear WNR854T to devicetree > >> > > >> > >> Pulled into next/soc, thanks! > > > > Sorry, backed out again after seeing the PCI stuff on the WNR854T in > > there. I thought the plan was to leave out PCI support from the DT > > based machine file, and leave the old board in place, or am I > > missing something? > > I might have overlooked the thread, I thouhgt the state of the patch was > OK as is, and further changes can be done later. > > So it seems that it will be 4.10 material. > We have gained a little more time since Linus delayed the merge window by another week, so I think there is still a chance to respin this. I also really want the NO_IRQ changes to get merged ;-) Just drop the patch removing wnr854t-setup.c, and add another patch on top to remove the PCI initialization from wrt350n-v2-setup.c, and I'll take it. Arnd
Hi Arnd, On mar., sept. 20 2016, Arnd Bergmann <arnd@arndb.de> wrote: > On Tuesday, September 20, 2016 9:25:51 AM CEST Gregory CLEMENT wrote: >> Hi Arnd, >> >> On lun., sept. 19 2016, Arnd Bergmann <arnd@arndb.de> wrote: >> >> > On Monday, September 19, 2016 11:46:22 PM CEST Arnd Bergmann wrote: >> >> On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote: >> >> > mvebu soc for 4.9 (part 1) >> >> > >> >> > - irq cleanup for old mvebu SoC >> >> > - Convert orion5x based SoC Netgear WNR854T to devicetree >> >> > >> >> >> >> Pulled into next/soc, thanks! >> > >> > Sorry, backed out again after seeing the PCI stuff on the WNR854T in >> > there. I thought the plan was to leave out PCI support from the DT >> > based machine file, and leave the old board in place, or am I >> > missing something? >> >> I might have overlooked the thread, I thouhgt the state of the patch was >> OK as is, and further changes can be done later. >> >> So it seems that it will be 4.10 material. >> > > We have gained a little more time since Linus delayed the merge window > by another week, so I think there is still a chance to respin this. > > I also really want the NO_IRQ changes to get merged ;-) > > Just drop the patch removing wnr854t-setup.c, and add another patch > on top to remove the PCI initialization from wrt350n-v2-setup.c, > and I'll take it. Do you mean board-wnr854t.c? If it is the case then I can just drop the patch adding this file because the only things done in this file are about the PCI. Gregory > > Arnd
On Tuesday, September 20, 2016 6:43:34 PM CEST Gregory CLEMENT wrote: > > Do you mean board-wnr854t.c? Yes. > If it is the case then I can just drop the patch adding this file because > the only things done in this file are about the PCI. Ah, that's perfect. Just for more background, I think it shouldn't be too hard to convert the existing orion5x PCI support into a proper host driver, and I can assist anyone willing to work on this and test it. I think the steps here would roughly be: - change PCI (not PCIe) host initialization to call pci_scan_root_bus() directly, bypassing the pci_common_init logic - move PCI code into a separate file - change PCI code into a driver by adding platform_device based probing - add DT support for that driver. For the PCIe code, the obvious strategy is to replace it with the existing pcie-mvebu driver, adding any missing parts in the process. Arnd