Mark, Quite honestly, I have no idea how both of those capes you're showing data on work. Each peripheral module between the two have different base addresses. Offset width, I can understand being different, but device module base address ? . . .I'm confused.
On Mon, Feb 8, 2016 at 5:58 PM, William Hermans <yyrk...@gmail.com> wrote: > *We could also add the alias to the am33xx.dtsi:* >> >> * >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi#n20 >> <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi#n20>* >> >> * like:* >> >> * >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=70f97128a158a596aeb82140ffacc8c18657baee >> <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=70f97128a158a596aeb82140ffacc8c18657baee>* >> > > Yeah, but would that help with the given problem with what Mark is > currently facing ? Look at the two capes, and base address, and mode each > pwm chip is placed in. > > On Mon, Feb 8, 2016 at 5:50 PM, Robert Nelson <robertcnel...@gmail.com> > wrote: > >> On Mon, Feb 8, 2016 at 6:36 PM, Mark A. Yoder <mark.a.yo...@gmail.com> >> wrote: >> > Yup, here's the mappings depending on which dts file is used: >> > >> > # universaln >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 -> >> > ../../devices/platform/ocp/48300000.epwmss/48300200.ehrpwm/pwm/pwmchip0 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip2 -> >> > ../../devices/platform/ocp/48302000.epwmss/48302200.ehrpwm/pwm/pwmchip2 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip4 -> >> > ../../devices/platform/ocp/48300000.epwmss/48300100.ecap/pwm/pwmchip4 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip5 -> >> > ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip5 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip6 -> >> > ../../devices/platform/ocp/48304000.epwmss/48304200.ehrpwm/pwm/pwmchip6 >> > >> > >> > # cape-emmc >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:01 pwmchip0 -> >> > ../../devices/platform/ocp/48300000.epwmss/48300100.ecap/pwm/pwmchip0 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:01 pwmchip1 -> >> > ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip1 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:01 pwmchip2 -> >> > ../../devices/platform/ocp/48300000.epwmss/48300200.ehrpwm/pwm/pwmchip2 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:01 pwmchip4 -> >> > ../../devices/platform/ocp/48302000.epwmss/48302200.ehrpwm/pwm/pwmchip4 >> > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:01 pwmchip6 -> >> > ../../devices/platform/ocp/48304000.epwmss/48304200.ehrpwm/pwm/pwmchip6 >> > >> > Yes, the addresses are there, so I need to find a place that maps the >> > addresses to the header pin numbers. >> >> We could also add the alias to the am33xx.dtsi: >> >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi#n20 >> >> like: >> >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=70f97128a158a596aeb82140ffacc8c18657baee >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
