devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sicelo <absicsz@gmail.com>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	"B. Niedermayr" <benedikt.niedermayr@siemens.com>,
	krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
	rogerq@kernel.org, tony@atomide.com
Subject: Re: gpmc wait pin regression from 89aed3cd5cb9
Date: Wed, 4 Jan 2023 06:38:03 +0200	[thread overview]
Message-ID: <Y7UCq+umIJScfQ16@tp440p.steeds.sam> (raw)
In-Reply-To: <Y7SoIxhkOiCS+BFj@colin-ia-desktop>

Hi Colin

On Tue, Jan 03, 2023 at 02:11:47PM -0800, Colin Foster wrote:
> 
> After commit 89aed3cd5cb9 ("memory: omap-gpmc: wait pin additions") the
> SMSC stops working because existing device trees don't have a default
> "gpmc,wait-pin" defined.
> 
> I fixed the issue for myself by adding this to my .dtsi, but I imagine
> any existing device trees that use the OMAP / SMSC combination will be
> similarly broken in 6.2-rc2.
> 
> My latest DT submission shows the use of the omap-gpmc-smsc9221.dtsi
> without the addition of gpmc,wait-pin which worked in 6.1:

I also had the same issue in 6.2-rc2. However, I found the problem has
already been fixed at:

https://lore.kernel.org/linux-omap/20221209123147.591982-1-benedikt.niedermayr@siemens.com/

Hope this helps you

Sicelo

      reply	other threads:[~2023-01-04  4:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 22:11 gpmc wait pin regression from 89aed3cd5cb9 Colin Foster
2023-01-04  4:38 ` Sicelo [this message]

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=Y7UCq+umIJScfQ16@tp440p.steeds.sam \
    --to=absicsz@gmail.com \
    --cc=benedikt.niedermayr@siemens.com \
    --cc=colin.foster@in-advantage.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).