我正在试验一个脉宽调制驱动的Beaglebone黑色,基于这一个.
当我在元bbb层中使用Yocto时,我不得不重写.dtsi:
&am33xx_pinmux {
bbb_pwm_P8_13_pins: bbb_pwm_P8_13_pins {
pinctrl-single,pins = <0x024 0x4>; /* P8_13 (ZCZ ball T10) | MODE 4 */
};
};
/ {
bbb-pwm@123 {
compatible = "tfe,bbb_pwm-1.00.a";
pwms = <&ehrpwm2 1 0 1>;
pwm-names = "PWM_P8_13";
pinctrl-names = "default";
pinctrl-0 = <&bbb_pwm_P8_13_pins>;
enabled = <0>;
duty = <0>;
status = "okay";
};
};但是,在驱动程序探测功能期间,调用
pwm_test->pwm = devm_pwm_get(&pdev->dev, NULL);返回ENODEV:
[ 7.538249] pinctrl-single 44e10800.pinmux: found group selector 15 for bbb_pwm_P8_13_pins
[ 7.538278] pinctrl-single 44e10800.pinmux: request pin 9 (44e10824.0) for bbb-pwm@123
[ 7.538291] pinctrl-single 44e10800.pinmux: enabling bbb_pwm_P8_13_pins function15
[ 7.538366] Loading bbb_pwm
[ 7.541304] bbb-pwm bbb-pwm@123: obtain a copy of previously claimed pinctrl
[ 7.541321] bbb-pwm bbb-pwm@123: Unable to request PWM (err = -19)我发现错误代码由子呼叫 of devm_pwm_get返回:
static int pwm_device_request(struct pwm_device *pwm, const char *label)
{
/* .... */
if (!try_module_get(pwm->chip->ops->owner))
return -ENODEV;
/* ... */
}然而,由于我对Linux驱动程序相当陌生,我不明白为什么会发生这种情况。有什么线索吗?
发布于 2016-09-19 13:43:57
结果表明,底层PWM驱动程序(EHRPWM)在内核中被禁用.使用menuconfig启用它并确保在设备树中启用EHRPWM和EPWMSS解决了我的问题:
使用元bbb层,我只需通过bitbake访问menuconfig:
bitbake virtual/kernel -c menuconfig并加载位于/meta-bbb/recipes-kernel/linux/linux-stable-4.4/beaglebone/defconfig的defconfig。
我还将以下一行添加到我的local.conf中
PREFERRED_VERSION_linux-stable = "4.4"这是我的dtsi:
&am33xx_pinmux {
bbb_pwm_P8_13_pins: bbb_pwm_P8_13_pins {
pinctrl-single,pins = <0x024 0x4>; /* P8_13 (ZCZ ball T10) | MODE 4 */
};
};
&ehrpwm2 {
status = "okay";
};
&epwmss2 {
status = "okay";
};
/ {
bbb-pwm@123 {
compatible = "tfe,bbb_pwm-1.00.a";
pwms = <&ehrpwm2 1 0 1>;
pwm-names = "PWM_P8_13";
pinctrl-names = "default";
pinctrl-0 = <&bbb_pwm_P8_13_pins>;
enabled = <0>;
duty = <0>;
status = "okay";
};
};https://stackoverflow.com/questions/39438656
复制相似问题