Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-24 Thread Kristian Evensen
Hi, On Tue, May 22, 2018 at 10:33 PM, Rosen Penev wrote: > Looks like it's this commit: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/mt7621-mmc?h=next-20180517&id=b734735fcaca60e8f07b040cd8a700f6fabe5b39 > > Please try reverting. Unfortunately I don

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-23 Thread Andrey Jr. Melnikov
In gmane.comp.embedded.lede.devel Kristian Evensen wrote: > On Wed, May 23, 2018 at 4:09 AM, Andrey Jr. Melnikov > wrote: > > In gmane.comp.embedded.lede.devel Rosen Penev wrote: > >> On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen > >> wrote: > >> > Hi, > >> > > >> > On Tue, May 22, 2018 at

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-23 Thread Kristian Evensen
On Wed, May 23, 2018 at 4:09 AM, Andrey Jr. Melnikov wrote: > In gmane.comp.embedded.lede.devel Rosen Penev wrote: >> On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen >> wrote: >> > Hi, >> > >> > On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: >> >> what exactly is the issue ? breaking co

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-23 Thread Andrey Jr. Melnikov
In gmane.comp.embedded.lede.devel Rosen Penev wrote: > On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen > wrote: > > Hi, > > > > On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: > >> what exactly is the issue ? breaking compat means that rosen either needs > >> to > >> fix the regression o

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread Kristian Evensen
Hi, On Tue, May 22, 2018 at 1:33 PM, Rosen Penev wrote: > Looks like it's this commit: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/mt7621-mmc?h=next-20180517&id=b734735fcaca60e8f07b040cd8a700f6fabe5b39 > > Please try reverting. Unfortunately I don'

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread Rosen Penev
On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen wrote: > Hi, > > On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: >> what exactly is the issue ? breaking compat means that rosen either needs to >> fix the regression or we need to revert the patch. > > The issue I saw is that writing to GPIO

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread Rosen Penev
On Tue, May 22, 2018 at 7:33 AM, John Crispin wrote: > > > On 22/05/18 16:18, Kristian Evensen wrote: >> >> On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: Bisecting further is hard, since the commit is a combination of (a lot of) clean-up and some functional changes. >>>

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread Kristian Evensen
Hi, On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: > what exactly is the issue ? breaking compat means that rosen either needs to > fix the regression or we need to revert the patch. The issue I saw is that writing to GPIO has no effect. On my device (mt7620-based), I can control the power

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread John Crispin
On 22/05/18 16:18, Kristian Evensen wrote: On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: Bisecting further is hard, since the commit is a combination of (a lot of) clean-up and some functional changes. Changes can be viewed on the linux-next tree. It should be as simple as dropping in

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-22 Thread Kristian Evensen
On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: >> Bisecting further is hard, since the >> commit is a combination of (a lot of) clean-up and some functional >> changes. > Changes can be viewed on the linux-next tree. It should be as simple > as dropping in the relevant files to the files-4.1

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-20 Thread Rosen Penev
On Sun, May 20, 2018 at 1:04 PM, Kristian Evensen wrote: > Hello, > > When building and testing nightly on an MT7620-device I have (the > Sanlinking D240), I noticed that changing the state of the two > exported pins (45 and 46) had no effect. The pins are used to control > the power to the two mi

[OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

2018-05-20 Thread Kristian Evensen
Hello, When building and testing nightly on an MT7620-device I have (the Sanlinking D240), I noticed that changing the state of the two exported pins (45 and 46) had no effect. The pins are used to control the power to the two mini-PCIe slots on the board, and the devices connected to the slots we