All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx
Date: Sat, 20 Jul 2019 21:42:49 -0500	[thread overview]
Message-ID: <0af63198-5a68-2f0d-f14e-2b514580d2d5@lechnology.com> (raw)
In-Reply-To: <20190326181324.32140-2-tony@atomide.com>

On 3/26/19 1:13 PM, Tony Lindgren wrote:
> We can now drop legacy platform data one interconnect target module at
> a time in favor of the device tree based data that has been added earlier.
> 
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---

This breaks wifi on BeagleBone Blue (found via git bisect). In dmesg, I see:

     platform 47810000.mmc: Cannot lookup hwmod 'mmc3'

How can we fix it?

WARNING: multiple messages have this Message-ID (diff)
From: David Lechner <david@lechnology.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx
Date: Sat, 20 Jul 2019 21:42:49 -0500	[thread overview]
Message-ID: <0af63198-5a68-2f0d-f14e-2b514580d2d5@lechnology.com> (raw)
In-Reply-To: <20190326181324.32140-2-tony@atomide.com>

On 3/26/19 1:13 PM, Tony Lindgren wrote:
> We can now drop legacy platform data one interconnect target module at
> a time in favor of the device tree based data that has been added earlier.
> 
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---

This breaks wifi on BeagleBone Blue (found via git bisect). In dmesg, I see:

     platform 47810000.mmc: Cannot lookup hwmod 'mmc3'

How can we fix it?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-07-21  2:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 18:13 [PATCH 0/4] drop selected platform data for am3 and am4 Tony Lindgren
2019-03-26 18:13 ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx Tony Lindgren
2019-03-26 18:13   ` Tony Lindgren
2019-07-21  2:42   ` David Lechner [this message]
2019-07-21  2:42     ` David Lechner
2019-07-22  6:09     ` Tony Lindgren
2019-07-22  6:09       ` Tony Lindgren
2019-07-22  7:54       ` Tony Lindgren
2019-07-22  7:54         ` Tony Lindgren
2019-07-22 14:27         ` David Lechner
2019-07-22 14:27           ` David Lechner
2019-07-23  6:40           ` Tony Lindgren
2019-07-23  6:40             ` Tony Lindgren
2019-07-22 14:54       ` David Lechner
2019-07-22 14:54         ` David Lechner
2019-07-23  6:38         ` Tony Lindgren
2019-07-23  6:38           ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 2/4] ARM: OMAP2+: Drop i2c platform data for am33xx " Tony Lindgren
2019-03-26 18:13   ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 3/4] ARM: OMAP2+: Drop gpio " Tony Lindgren
2019-03-26 18:13   ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 4/4] ARM: OMAP2+: Drop uart " Tony Lindgren
2019-03-26 18:13   ` Tony Lindgren

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=0af63198-5a68-2f0d-f14e-2b514580d2d5@lechnology.com \
    --to=david@lechnology.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.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 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.