Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Dmitry Tunin
I tested gpio-keys on dir825b1 and didn't see a noticable change against gpio-keys-polled. Both miss events and work poorly. So no objections for a switch. пн, 5 авг. 2019 г. в 19:27, Dmitry Tunin : > > > This recent Pull Request used gpio-keys on ar7100: > > https://github.com/openwrt/openwrt/pu

[OpenWrt-Devel] Review and cleanup of base packages

2019-08-10 Thread Petr Štetiar
Hi, one of the topics discussed during recent Hamburg meeting was "Review base packages"[1], where we simply talked about: * lack of formal definition for a base package * transfer of base packages which don't fit formal definition into feeds So, how can we define which package should be inclu

[OpenWrt-Devel] [14445.624549] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 0

2019-08-10 Thread Enrico Mioso
Hello all, This is the message I receive everytime I bring down Wi-Fi on my Archer C60 V2. root@C60:/# [14445.574213] device wlan1 left promiscuous mode [14445.579042] br-lan: port 2(wlan1) entered disabled state [14445.588397] device wlan0 left promiscuous mode [14445.593107] br-lan: port 3(wla

[OpenWrt-Devel] [PATCH] treewide: sync bootcount scripts across targets

2019-08-10 Thread Chuanhong Guo
This commit made the following changes to sync all bootcount scripts: 1. use boot() instead of start() This script only needs to be executed once when boot is complete. use boot() to make this explicit. 2. drop sourcing of /lib/functions.sh This is aready done in /etc/rc.common. 3. r

[OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-10 Thread Joan Moreau via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- like TPLink AV2000 or other (with

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-10 Thread Enrico Mioso
Hello! I guess this is in a case-by-case basis - I have a TP-Link RE450 which is supported. I know there are also Wi-Fi-only devices, but don't think OpenWRt supports any of them. I guess this happens also due to the amount of flash and RAM memory those devices have. And - if you're going for

Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread mail
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 11:53 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-

Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Dmitry Tunin
> Can I add your Tested-by? I tested only one target, it makes no sense to add this. And I what about ath9k keys. They are a problem. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Dmitry Tunin
If you will be pushing it some way, remove debounce-interval too. Without it gpio-keys work better. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread mail
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 18:25 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-

Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Dmitry Tunin
> So should it remove the change for ath9k keys and only do the other ones at > the moment? That's a good question. I suggest to leave devices that HAVE some keys attached to ath9k keys using 'gpio-keys-polled'. It makes no sense to use both drivers. _

[OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Adrian Schmutzler
This converts all remaining devices to use interrupt-driven gpio-keys compatible instead of gpio-keys-polled. The poll-interval is removed. Only ar7240_netgear_wnr612-v2 is kept at gpio-keys-polled, as this one is using ath9k keys. Signed-off-by: Adrian Schmutzler --- Changed in v2: - Rebased

Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread Dmitry Tunin
As I mentioned before with 'gpio-keys' debounce-interval is not needed. Default is OK and looks better on ar7161. Maybe testing on other targets is needed. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/l

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-10 Thread Lech Perczak
W dniu 2019-08-10 o 16:30, Enrico Mioso pisze: Hello! I guess this is in a case-by-case basis - I have a TP-Link RE450 which is supported. I know there are also Wi-Fi-only devices, but don't think OpenWRt supports any of them. I guess this happens also due to the amount of flash and RAM memor

Re: [OpenWrt-Devel] [PATCH] ath79: use gpio_hog instead of gpio-export

2019-08-10 Thread mail
Hi, > +    usb { > +        gpio-hog; > +        line-name = "tp-link:power:usb"; > +        gpios = <6 GPIO_ACTIVE_HIGH>; > +        output-high; > }; >  }; As stated earlier, I would prefer calling those blocks usb-power, usb1-power, etc.. > diff --git a/target/linux/ath79/dts/qca9531_yu

Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys

2019-08-10 Thread mail
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 19:47 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to > inter

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-10 Thread Joan Moreau via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- The Powerline system needs a "Lan

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-10 Thread Alberto Bursi
On 11/08/19 02:08, Joan Moreau via openwrt-devel wrote: >The Powerline system needs a "Lan name" in order to synchronize teh devices. >How this is translated in OpenWrt ? RE450 is not a powerline. Only supported device is *https://openwrt.org/toh/hwdata/tp-link/tp-link_tl-wpa8630* and it