Hi Rob, On Thu, Apr 16, 2015 at 12:17 PM, Rob Clark <robdclark@xxxxxxxxx> wrote: > On Thu, Apr 16, 2015 at 11:21 AM, Catalin Marinas > <catalin.marinas@xxxxxxx> wrote: > >> But I'm definitely going to discourage companies like Qualcomm >> deliberately ignoring the existing booting protocols while trying to get >> their code upstream. This patch series is posted by Qualcomm without >> providing any technical reason on why they don't want to/couldn't use >> PSCI (well, I guess there is no technical reason but they may not care >> much about mainline either). > > Sure.. just trying to make sure the wrong people don't end up being > the ones that suffer. I would assume/expect that it is at least > possible for qcom to change firmware/bootloader for their dev boards > and future devices and whatnot, whether they grumble about it or not. > But I guess most of what the general public has are devices w/ signed > fw, which is why "go fix your firmware" is an option that sets off > alarm bells for me. > > I guess the first device where this will matter to me and a large > group of community folks would be the dragonboard 410c.. *hopefully* > it does not require signed firmware or at least qcom could make > available signed firmware which supports psci.. For development boards, one would hope there is a way to sign your own firmware. You can't expect - even for a phone SoC - that the development boards require entering some kind of Faustian contract for development of low-level software. What if someone wants to develop a platform that doesn't require signing? That said most of these dev boards have completely mangled JTAG anyway, and I know Inforce (and Hardkernel, and so on) love their barely-ever-updated custom firmware binaries, so.. The best thing would be to pick up one of those boards and port a PSCI firmware to it (ATF or your own..) and just embarrass the SoC vendor by having better mainline power management support (implemented by 10 lines in a device tree) with the complicated code hidden away behind the scenes there, like it should have been done in the first place.. Ta. Matt Sealey <neko@xxxxxxxxxxxxx> -- 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
