On 15:49-20130110, Matt Porter wrote: > On Thu, Jan 10, 2013 at 01:46:53PM -0600, Nishanth Menon wrote: > > On 14:35-20130110, Matt Porter wrote: > > > On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote: > > > > On 10/18/2012 6:56 PM, Matt Porter wrote: [...] > > > > > > + 0x19c 0x13 /* mcasp0_ahclkr.spi1_cs0, OUTPUT_PULLUP | MODE3 */ > > > > > + >; > > > > > > > > Is there a single pinmux setting that provides SPI functionality on the > > > > bone headers? Or this is specific to a cape you tested with? > > > > > > No, there are two usable settings for spi1 and one setting for spi0. > > > I'm dropping this from the series since it's specific to how I wired up > > > the homebrew cape I use for spi testing on the Bone. I publish the > > > branch where all these extra "test-specific" patches (that aren't intended > > > to be merged) are at in the cover letter. Anybody that needs context of > > > how/what worked and was tested can grab them there. > > Possibly dumb question: > > Cant we have pre-usable spi configurations? Like spi1_configuration1_pins, > > spi2_configuration1_pins, spi0_configuration1_pins? If documented with > > P9 pin names in the bone dts, it saves a bit of effort in looking up > > pad offset when dealing with capes. > > Yes, let's introduce these things separately. I plan to reintroduce > patches to fix the incorrect 1-based numbering on many of the AM33xx as > previous ones were dropped...and I think this makes sense on top of > that. sounds good to me. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
