All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	"paulus@samba.org" <paulus@samba.org>,
	"tiago.brusamarello@datacom.ind.br" 
	<tiago.brusamarello@datacom.ind.br>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fsl_espi errors on v5.7.15
Date: Fri, 14 Aug 2020 08:19:29 +0200	[thread overview]
Message-ID: <c43a23bd-33ec-4ef2-2ca5-730342248db3@gmail.com> (raw)
In-Reply-To: <3f48e5fb-33c9-8046-0f80-236eed163c16@alliedtelesis.co.nz>

On 14.08.2020 04:48, Chris Packham wrote:
> Hi,
> 
> I'm seeing a problem with accessing spi-nor after upgrading a T2081 
> based system to linux v5.7.15
> 
> For this board u-boot and the u-boot environment live on spi-nor.
> 
> When I use fw_setenv from userspace I get the following kernel logs
> 
> # fw_setenv foo=1
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> ...
> 

This error reporting doesn't exist yet in 4.4. So you may have an issue
under 4.4 too, it's just not reported.
Did you verify that under 4.4 fw_setenv actually has an effect?

> If I run fw_printenv (before getting it into a bad state) it is able to 
> display the content of the boards u-boot environment.
> 

This might indicate an issue with spi being locked. I've seen related
questions, just use the search engine of your choice and check for
fw_setenv and locked.

> If been unsuccessful in producing a setup for bisecting the issue. I do 
> know the issue doesn't occur on the old 4.4.x based kernel but that's 
> probably not much help.
> 
> Any pointers on what the issue (and/or solution) might be.
> 
> Thanks,
> Chris
> 

Heiner

WARNING: multiple messages have this Message-ID (diff)
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	"paulus@samba.org" <paulus@samba.org>,
	"tiago.brusamarello@datacom.ind.br"
	<tiago.brusamarello@datacom.ind.br>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: fsl_espi errors on v5.7.15
Date: Fri, 14 Aug 2020 08:19:29 +0200	[thread overview]
Message-ID: <c43a23bd-33ec-4ef2-2ca5-730342248db3@gmail.com> (raw)
In-Reply-To: <3f48e5fb-33c9-8046-0f80-236eed163c16@alliedtelesis.co.nz>

On 14.08.2020 04:48, Chris Packham wrote:
> Hi,
> 
> I'm seeing a problem with accessing spi-nor after upgrading a T2081 
> based system to linux v5.7.15
> 
> For this board u-boot and the u-boot environment live on spi-nor.
> 
> When I use fw_setenv from userspace I get the following kernel logs
> 
> # fw_setenv foo=1
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but SPIE_DON isn't set!
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> fsl_espi ffe110000.spi: Transfer done but rx/tx fifo's aren't empty!
> fsl_espi ffe110000.spi: SPIE_RXCNT = 1, SPIE_TXCNT = 32
> ...
> 

This error reporting doesn't exist yet in 4.4. So you may have an issue
under 4.4 too, it's just not reported.
Did you verify that under 4.4 fw_setenv actually has an effect?

> If I run fw_printenv (before getting it into a bad state) it is able to 
> display the content of the boards u-boot environment.
> 

This might indicate an issue with spi being locked. I've seen related
questions, just use the search engine of your choice and check for
fw_setenv and locked.

> If been unsuccessful in producing a setup for bisecting the issue. I do 
> know the issue doesn't occur on the old 4.4.x based kernel but that's 
> probably not much help.
> 
> Any pointers on what the issue (and/or solution) might be.
> 
> Thanks,
> Chris
> 

Heiner

  reply	other threads:[~2020-08-14  6:19 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  2:48 fsl_espi errors on v5.7.15 Chris Packham
2020-08-14  2:48 ` Chris Packham
2020-08-14  6:19 ` Heiner Kallweit [this message]
2020-08-14  6:19   ` Heiner Kallweit
2020-08-16 21:09   ` Chris Packham
2020-08-16 21:09     ` Chris Packham
2020-08-18 22:44     ` Chris Packham
2020-08-18 22:44       ` Chris Packham
2020-08-19  6:15       ` Heiner Kallweit
2020-08-19  6:15         ` Heiner Kallweit
2020-08-19 21:08         ` Chris Packham
2020-08-19 21:08           ` Chris Packham
2020-08-24 22:04           ` Chris Packham
2020-08-24 22:04             ` Chris Packham
2020-08-25  3:54             ` Chris Packham
2020-08-25  3:54               ` Chris Packham
2020-08-25  7:22               ` Heiner Kallweit
2020-08-25  7:22                 ` Heiner Kallweit
2020-08-25 22:22                 ` Chris Packham
2020-08-25 22:22                   ` Chris Packham
2020-08-26  1:48                   ` Chris Packham
2020-08-26  1:48                     ` Chris Packham
2020-08-26  6:07                     ` Chris Packham
2020-08-26  6:07                       ` Chris Packham
2020-08-26  6:38                       ` Heiner Kallweit
2020-08-26  6:38                         ` Heiner Kallweit
2020-08-26 22:26                         ` Chris Packham
2020-08-26 22:26                           ` Chris Packham
2020-08-27  7:12                         ` Nicholas Piggin
2020-08-27  7:12                           ` Nicholas Piggin
2020-08-27 22:07                           ` Chris Packham
2020-08-27 22:07                             ` Chris Packham
2020-08-30 12:30                             ` Nicholas Piggin
2020-08-30 12:30                               ` Nicholas Piggin
2020-08-30 13:55                               ` Heiner Kallweit
2020-08-30 13:55                                 ` Heiner Kallweit
2020-08-30 21:00                               ` Chris Packham
2020-08-30 21:00                                 ` Chris Packham
2020-08-30 21:41                                 ` Heiner Kallweit
2020-08-30 21:41                                   ` Heiner Kallweit
2020-08-30 21:59                                   ` Chris Packham
2020-08-30 21:59                                     ` Chris Packham
2020-08-31 12:33                                     ` Heiner Kallweit
2020-08-31 12:33                                       ` Heiner Kallweit
2020-09-01  1:25                                       ` Chris Packham
2020-09-01  1:25                                         ` Chris Packham
2020-09-01  6:14                                         ` Nicholas Piggin
2020-09-01  6:14                                           ` Nicholas Piggin
2020-09-01 23:29                                           ` Chris Packham
2020-09-01 23:29                                             ` Chris Packham
2020-09-01 23:31                                             ` Chris Packham
2020-09-01 23:31                                               ` Chris Packham
2020-09-03 23:58                                           ` Chris Packham
2020-09-03 23:58                                             ` Chris Packham
2020-09-04 17:23                                             ` Heiner Kallweit
2020-09-06 20:59                                               ` Chris Packham
2020-09-06 21:03                                               ` Chris Packham
2020-09-06 21:03                                                 ` Chris Packham
2020-09-07  9:53                                             ` Joakim Tjernlund
2020-09-07  9:53                                               ` Joakim Tjernlund
2020-09-07 15:38                                               ` Joakim Tjernlund
2020-09-07 15:38                                                 ` Joakim Tjernlund
2020-09-01  2:52                                       ` Chris Packham
2020-09-01  2:52                                         ` Chris Packham
2020-09-01  7:38                                         ` Heiner Kallweit
2020-09-01  7:38                                           ` Heiner Kallweit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c43a23bd-33ec-4ef2-2ca5-730342248db3@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=benh@kernel.crashing.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=tiago.brusamarello@datacom.ind.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.