From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: devicetree@vger.kernel.org, Drew Fustini <drew@beagleboard.org>,
Faiz Abbas <faiz_abbas@ti.com>,
Jason Kridner <jkridner@beagleboard.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: am335x-bone-common: Fix mmc0 Write Protect
Date: Mon, 2 Jul 2018 23:24:19 -0700 [thread overview]
Message-ID: <20180703062419.GB112168@atomide.com> (raw)
In-Reply-To: <20180702202143.25343-1-robertcnelson@gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [180702 20:24]:
> Mainline Commit b74c2b21e1551018af53ee6c1efc051dfce2d788 added the pinmux
> settings for mmc1, however this pin (0x9a0) is routed to P9_42 on the cape
> header. Thus any BeagleBone cape that utilizes P9_42 triggers mmc0's Write
> Protect.
Thanks applying into omap-for-v4.18/fixes. I'll also add a Fixes tag for
it.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am335x-bone-common: Fix mmc0 Write Protect
Date: Mon, 2 Jul 2018 23:24:19 -0700 [thread overview]
Message-ID: <20180703062419.GB112168@atomide.com> (raw)
In-Reply-To: <20180702202143.25343-1-robertcnelson@gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [180702 20:24]:
> Mainline Commit b74c2b21e1551018af53ee6c1efc051dfce2d788 added the pinmux
> settings for mmc1, however this pin (0x9a0) is routed to P9_42 on the cape
> header. Thus any BeagleBone cape that utilizes P9_42 triggers mmc0's Write
> Protect.
Thanks applying into omap-for-v4.18/fixes. I'll also add a Fixes tag for
it.
Regards,
Tony
next prev parent reply other threads:[~2018-07-03 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 20:21 [PATCH] ARM: dts: am335x-bone-common: Fix mmc0 Write Protect Robert Nelson
2018-07-02 20:21 ` Robert Nelson
2018-07-03 6:24 ` Tony Lindgren [this message]
2018-07-03 6:24 ` Tony Lindgren
2018-07-03 6:31 ` Faiz Abbas
2018-07-03 6:31 ` Faiz Abbas
2018-07-03 10:23 ` Robert Nelson
2018-07-03 10:23 ` Robert Nelson
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=20180703062419.GB112168@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=faiz_abbas@ti.com \
--cc=jkridner@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.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.