On 2019-01-30 8:27 p.m., John David Anglin wrote:
> On 2019-01-30 5:38 p.m., Andrew Lunn wrote:
>> I'd suggest you take a look at the datasheet for the 37xx and check
>> what the hardware actually supports. You might need to extend the
>> driver.
> I did look and the GIC does support level interrup
On 2019-01-30 5:38 p.m., Andrew Lunn wrote:
> I'd suggest you take a look at the datasheet for the 37xx and check
> what the hardware actually supports. You might need to extend the
> driver.
I did look and the GIC does support level interrupts. But all the
documentation is in
generic ARM document
On Wed, Jan 30, 2019 at 05:24:53PM -0500, John David Anglin wrote:
> On 2019-01-30 12:28 p.m., Andrew Lunn wrote:
> > You need active low interrupts. Without it, i think you are always
> > going to have race conditions which will cause interrupts to get
> > stuck/lost.
> I don't know if this is a h
On 2019-01-30 12:28 p.m., Andrew Lunn wrote:
> You need active low interrupts. Without it, i think you are always
> going to have race conditions which will cause interrupts to get
> stuck/lost.
I don't know if this is a hardware limitation or not, but currently the
armada 37xx doesn't support
leve
> In /proc/interrupts, the switch interrupts are shown as edge. The only
> place that I see where this
> is potentially set is mv88e6xxx_g2_watchdog_setup() where the call to
> request_threaded_irq() passes
> "IRQF_ONESHOT | IRQF_TRIGGER_FALLING". Does this need to change?
Hi Dave
Device tree d
On 2019-01-30 12:28 p.m., Andrew Lunn wrote:
> On Wed, Jan 30, 2019 at 12:08:39PM -0500, John David Anglin wrote:
>> On 2019-01-22 7:22 p.m., Andrew Lunn wrote:
>>> >From my Espressobin
>>>
>>> cat /proc/interrupts
>>> ...
>>> 44: 0 0 mv88e6xxx-g1 3 Edge mv88e6xxx-g1-atu-
On Wed, Jan 30, 2019 at 12:08:39PM -0500, John David Anglin wrote:
> On 2019-01-22 7:22 p.m., Andrew Lunn wrote:
> > >From my Espressobin
> >
> > cat /proc/interrupts
> > ...
> > 44: 0 0 mv88e6xxx-g1 3 Edge mv88e6xxx-g1-atu-prob
> > 46: 0 0 mv88e6xxx-g
On 2019-01-22 7:22 p.m., Andrew Lunn wrote:
> >From my Espressobin
>
> cat /proc/interrupts
> ...
> 44: 0 0 mv88e6xxx-g1 3 Edge mv88e6xxx-g1-atu-prob
> 46: 0 0 mv88e6xxx-g1 5 Edge mv88e6xxx-g1-vtu-prob
> 48: 38 24 mv88e6xxx-g1
On 2019-01-25 11:48 a.m., Russell King - ARM Linux admin wrote:
> If you don't have any means to reset the card like that, then the only
> workaround is to reduce the maximum speed - and avoid going to 1.8V
> signalling mode.
There is no power controller on espressobin. The regulator only
switches
On Fri, Jan 25, 2019 at 11:30:54AM -0500, John David Anglin wrote:
> This also makes me wonder about this SD interrupt:
> 43: 0 0 GPIO1 3 Edge d00d.sdhci cd
> Many poeple have trouble with SD cards on reboot.
[off topic, but a relevant reply to the above]
Very lik
On 2019-01-22 7:22 p.m., Andrew Lunn wrote:
> >From my Espressobin
>
> cat /proc/interrupts
> ...
> 44: 0 0 mv88e6xxx-g1 3 Edge mv88e6xxx-g1-atu-prob
> 46: 0 0 mv88e6xxx-g1 5 Edge mv88e6xxx-g1-vtu-prob
> 48: 38 24 mv88e6xxx-g1
> > It does not need to. There are two options here:
> >
> > 1) The PHY has no interrupt. phylib will poll the PHY once per second
> >for link changes.
> >
> > 2) The PHY has in interrupt. Link changes will cause the interrupt to
> >fire, and the phylib will then read the current state.
> >
On 2019-01-22 5:36 p.m., Andrew Lunn wrote:
> It does not need to. There are two options here:
>
> 1) The PHY has no interrupt. phylib will poll the PHY once per second
>for link changes.
>
> 2) The PHY has in interrupt. Link changes will cause the interrupt to
>fire, and the phylib will th
On 1/22/19 4:00 PM, John David Anglin wrote:
> On 2019-01-22 6:12 p.m., Andrew Lunn wrote:
>> I just booted my espressobin with net-next. It is running Debian, and
>> i have the following in /etc/network/interfaces
>>
>> source /etc/network/interfaces.d/*
>>
>> # The loopback network interface
>> a
On 2019-01-22 6:12 p.m., Andrew Lunn wrote:
> I just booted my espressobin with net-next. It is running Debian, and
> i have the following in /etc/network/interfaces
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary netw
On 2019-01-22 5:36 p.m., Andrew Lunn wrote:
> In what order? The master interface has to be up first before any
> slave interface is configured up.
Possibly, that's a clue. If I recall, that's determined by the naming
on the .network files in
/etc/systemd/network. The slave interfaces are coming
On 2019-01-22 6:12 p.m., Andrew Lunn wrote:
> I would suggest you manually configure your networking, just to
> test. I would suspect systemd is not doing things correctly.
I have armbian with debian stretch installed. I did find that both
systemd-networkd and
networkmanager were enabled. I disab
On Tue, Jan 22, 2019 at 02:16:09PM -0500, John David Anglin wrote:
> I've been hacking on a espressobin board to try to improve ptp support,
> etc. However, I have
> a big problem with link detection on the wan, lan0 and lan1 ports.
Hi John
I just booted my espressobin with net-next. It is runni
On Tue, Jan 22, 2019 at 04:40:27PM -0500, John David Anglin wrote:
> Hi Andrew,
>
> On 1/22/2019 3:28 PM, Andrew Lunn wrote:
> >Does it make a difference if you do it by hand? Bring up the master
> >interface, wan, lan0, lan1, add any bridge you need, etc.
> >
> >> From power on, none of the wan,
Hi Andrew,
On 1/22/2019 3:28 PM, Andrew Lunn wrote:
Does it make a difference if you do it by hand? Bring up the master
interface, wan, lan0, lan1, add any bridge you need, etc.
From power on, none of the wan, lan0, lan1 or br0 achieve link
(LOWER_UP).
I can explore this but I don't know at t
On Tue, Jan 22, 2019 at 02:16:09PM -0500, John David Anglin wrote:
> I've been hacking on a espressobin board to try to improve ptp support,
> etc. However, I have
> a big problem with link detection on the wan, lan0 and lan1 ports.
>
> I have a standard bridge configuration using systemd-network
I've been hacking on a espressobin board to try to improve ptp support,
etc. However, I have
a big problem with link detection on the wan, lan0 and lan1 ports.
I have a standard bridge configuration using systemd-networkd.
Currently, I'm working with linux
v4.20.2.
From power on, none of the wa
22 matches
Mail list logo
