cc-ing Jin Quian (maintains kernel repo for emulators), Bo Hu & Lingfeng Yang from Google Hi Rob, thank you for taking the time to review the patches. Let me try to answer some of your comments and concerns: > This isn't even supported in Google's common kernel tree. If it's not > important enough for it, why should it be for mainline kernel? Goldfish PIC controller driver is used and maintained currently in a separate kernel repo Google uses for Android emulator support: [1] https://android.googlesource.com/kernel/goldfish.git The referenced device also exist and is maintained in the official Android emulator repo. This device/driver has been successfully used for the past many years by MIPS for driving interrupts to other virtual devices which make Android emulation possible. I'll try to quote Google on their plans and let Jin correct me if I'm wrong. The idea is to have the emulator support in the Googles common kernel repo for all architectures and stop maintaining a separate one just for emulation. Currently there is emulator kernel support in common repo for Intel & ARM platforms, MIPS emulator support is still maintained in [1]. The effort of mainlining MIPS Ranchu virtual platform is because we want to eventually have MIPS emulator support in Googles common kernel repo backported from upstream in some of their next rebases. Also, having the emulator support in the upstream kernel would help picking up the latest fixes. In the matter of fact, many fixes for the MIPS kernel came from Android testing in the emulator. > To put it another way, why does goldfish need a special interrupt > controller. Just use one of the many that are already supported in the > kernel and emulated by qemu. The reason we are using Goldfish PIC for MIPS emulation is because it is pretty simple Interrupt controller which is easily maintained and the infrastructure for it in Android emulator is in place and continuously tested. > Same comments apply to the RTC patch. Same reasons apply as for Goldfish PIC. Kind regards, Miodrag ________________________________________ From: Rob Herring [robh+dt@xxxxxxxxxx] Sent: Friday, June 30, 2017 1:17 AM To: Aleksandar Markovic Cc: Linux-MIPS; Aleksandar Markovic; Miodrag Dinic; Goran Ferenc; David S. Miller; devicetree@xxxxxxxxxxxxxxx; Douglas Leung; Greg Kroah-Hartman; James Hogan; Jason Cooper; linux-kernel@xxxxxxxxxxxxxxx; Marc Zyngier; Mark Rutland; Martin K. Petersen; Mauro Carvalho Chehab; Paul Burton; Petar Jovanovic; Raghu Gandham; Thomas Gleixner Subject: Re: [PATCH v2 03/10] Documentation: Add device tree binding for Goldfish PIC driver On Wed, Jun 28, 2017 at 10:46 AM, Aleksandar Markovic <aleksandar.markovic@xxxxxxxxx> wrote: > From: Aleksandar Markovic <aleksandar.markovic@xxxxxxxxxx> > > Add documentation for DT binding of Goldfish PIC driver. The compatible > string used by OS for binding the driver is "google,goldfish-pic". This isn't even supported in Google's common kernel tree. If it's not important enough for it, why should it be for mainline kernel? To put it another way, why does goldfish need a special interrupt controller. Just use one of the many that are already supported in the kernel and emulated by qemu. Same comments apply to the RTC patch. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
