On 30 September 2015 at 12:18, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Wed, Sep 30, 2015 at 11:12:58AM -0700, Tyler Baker wrote: >> On 30 September 2015 at 10:31, Mark Brown <broonie@xxxxxxxxxx> wrote: > >> + Peter as he has been submitting u-boot patches recently for the HiKey. > >> Obviously, both UEFI and u-boot can be configured to use either UART, >> and at the moment u-boot defaults to using the on board UART. Whereas >> UEFI is using UART1 on the LS connector. I'm fine with switching the >> console default to use the UART1 on the LS connector as long as there >> is agreement to do so. > > Given that UEFI is switching and the requirement for soldering to get to > the on board UART it does seem to make sense, though it will create some > pain for current users. > >> > While we're at it there was a recent talk which mentioned a fairly large >> > amount of functionality that's apparently already "upstream" for this >> > device but not included in the DT, assuming that means that driver >> > support is there it would be good to add the corresponding DT. > >> Indeed, I think this comment is targeted to toward the d410c though as >> there are drivers for eMMC, and microsd drivers upstream but no DT >> bindings. I do not believe currently this is the case for HiKey. > > My understanding is that it applies to both with slightly different > driver sets, the slides aren't online yet (!) but if you look at 10:52 > or so in the video we should have SD/eMMC on HiKey in v4.1 with thermal > and CPUfreq added in v4.2. It also looks like there's just some DT > additions needed to enable reset, cpuidle and CPU hotplug using generic > code (mainly the constants for PSCI I expect). I just skimmed the video and I see your point. I'll need to investigate a bit but I'm up for sending some follow up patches to get these drivers functioning. First lets get the UART working :) Cheers, Tyler -- 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