IPQ807x_64 Button problem

Installing and Using OpenWrt
1

Hello,
Kernel - 4.4.60

I am using the target ipq807x_64.
I have the issue in the button, When the button is pushed there is not event.

Can you help me where is exactly problem please??

Waiting for you reply,

2
3

Thank you for your reply,

I tried everything but no success , I dont understand where is the exact problem.

4

Sounds like you're using an older OpenWrt based vendor SDK? Kernel 4.4 was a while ago.

Nor does the target sound like one that current or past OpenWrt codebases support?

5

so the button will not work in this kernel??

6

All depends on the framework used. You're not using a vanilla OpenWrt it looks like, you'll need to dig a bit and at least show some code and error messages.

7

That's not the issue,

the question is whether the functionality is implemented, if it's not an OpenWRT release, but a 3rd party.

8

/sys/firmware/devicetree/base/soc/pinctrl@1000000/button_pins
/sys/firmware/devicetree/base/soc/pinctrl@1000000/button_pins/reset_button
/sys/firmware/devicetree/base/soc/pinctrl@1000000/button_pins/ok_button
/sys/firmware/devicetree/base/soc/gpio_keys/button@1
/sys/firmware/devicetree/base/soc/gpio_keys/button@2

9

Are the buttons defined in your DTS?

10

I can see the button in the device tree but i dont know how its work .. I have implemented the hotplug scripts but no events when button is pressed...

I am using the openwrt...

11

which version ?

12 
&soc {
+	gpio_keys {
+		compatible = "gpio-keys";
+		pinctrl-0 = <&button_pins>;
+		pinctrl-names = "default";
+
+		button@1 {
+			label = "ok";
+			linux,code = <KEY_OK>;
+			gpios = <&tlmm 34 GPIO_ACTIVE_LOW>;
+			linux,input-type = <1>;
+			debounce-interval = <60>;
+		};
+
+		button@2 {
+			label = "reset";
+			linux,code = <KEY_CONFIG>;
+			gpios = <&tlmm 52 GPIO_ACTIVE_LOW>;
+			linux,input-type = <1>;
+			debounce-interval = <60>;
+		};
+	};
13

I think everything is renamed so i cannot find the version of openwrt, i only found this BusyBox v1.30.1 () built-in shell (ash)

14

what device is it then ?

15

I am afraid , I cannot disclosed the product name...Sorry...

But I can provide you the details what you need to analyze the button...

Please I am stuck for 2 days and able to identify the problem.

16

not able to identify the problem***

17

Then we'll probably be unable to disclose the solution :wink:

And since you don't appear to be using the official code base of OpenWrt, you're pretty much on your own.

18

Ahh please, as I dont know much about the product as I am new ...

thats why I cannot able to say to you...

Can we see where is the exact problem, please??

19

You can check dmesg or logread for pointers, even better would be to run logread -f in one terminal while pushing your button(s) in another and sharing those logs here. Just what it prints when you push those buttons is enough (if it prints anything).