On 8 January 2015 at 23:33, Dylan Reid <dgreid@xxxxxxxxxxxx> wrote: > On Wed, Jan 7, 2015 at 11:54 PM, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: >> On 7 January 2015 at 17:27, Simon Glass <sjg@xxxxxxxxxxxx> wrote: >>> Hi Tomeu, >>> >>> On 7 January 2015 at 06:02, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: >>>> >>>> On 4 December 2014 at 14:31, Simon Glass <sjg@xxxxxxxxxxxx> wrote: >>>> > Add support for Tegra124 Nyan-big. Pinmux is based on norrin with a single >>>> > change for the reset GPIO. >>>> >>>> Hi Simon, >>>> >>>> do you have a similar patch for the blaze? >>>> >>>> Thanks, >>>> >>>> Tomeu >>> >>> No I don't sorry. I suppose it is similar but I'm not sure who did the >>> pinmux for it. >> >> I have found some non-trivial differences when comparing the pinmux >> programming for the two boards in the chromeos kernel, that's why I >> would prefer if we had the complete data in tegra-pinmux-scripts. > > The differences between Big and Blaze are small. Four pins I think. > What differences were you seeing? So far I have had to change programming of usb_vbus_en2_pff1 and sdmmc1_clk_pz0. >> Dylan, Rhyland, git-blame points to both of you, do you have the >> spreadsheet for the blaze or know who could have it? > > We didn't derive the pinmux from a spreadsheet for Big or Blaze. Big > was so similar to Norrin that the few changes were made manually. Ah, that's cool, was kind of fearing that I would be finding more and more pins that need to be changed but without an authoritative source I would be wasting quite some time. Regards, Tomeu > Thanks for looking at this! > > Dylan > >> >> Thanks, >> >> Tomeu -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
