From: Drew Fustini <drew@beagleboard.org>
To: Tony Lindgren <tony@atomide.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Jason Kridner" <jkridner@beagleboard.org>,
"Robert Nelson" <robertcnelson@gmail.com>
Subject: Re: [PATCH V2] ARM: dts: am335x-pocketbeagle: Fix mmc0 Write Protect
Date: Tue, 16 Jun 2020 18:19:39 +0200 [thread overview]
Message-ID: <20200616161939.GA4007093@x1> (raw)
In-Reply-To: <20200616161024.GC37466@atomide.com>
On Tue, Jun 16, 2020 at 09:10:24AM -0700, Tony Lindgren wrote:
> * Drew Fustini <drew@beagleboard.org> [200609 14:46]:
> > AM3358 pin mcasp0_aclkr (ZCZ ball B13) [0] is routed to P1.31 header [1]
> > Mode 4 of this pin is mmc0_sdwp (SD Write Protect). A signal connected
> > to P1.31 may accidentally trigger mmc0 write protection. To avoid this
> > situation, do not put mcasp0_aclkr in mode 4 (mmc0_sdwp) by default.
> >
> > [0] http://www.ti.com/lit/ds/symlink/am3358.pdf
> > [1] https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual#531_Expansion_Headers
> >
> > Fixes: 047905376a16 (ARM: dts: Add am335x-pocketbeagle)
> > Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
> > Signed-off-by: Drew Fustini <drew@beagleboard.org>
> > ---
> > V2 change:
> > - correct P1.13 to P1.31, apologies for not catching that in V1
>
> Thanks (manually) applying into fixes. Your outgoing mail server has replaced
> the tabs in the patch with spaces making it not apply FYI.
>
> Regards,
>
> Tony
Thanks, Tony.
That is werid about the spaces. I use mutt to send mail via smtp.google.com
(beagleboard.org is gsuite). I'll inspect more closely next time.
prev parent reply other threads:[~2020-06-16 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 21:45 [PATCH V2] ARM: dts: am335x-pocketbeagle: Fix mmc0 Write Protect Drew Fustini
2020-06-16 16:10 ` Tony Lindgren
2020-06-16 16:19 ` Drew Fustini [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=20200616161939.GA4007093@x1 \
--to=drew@beagleboard.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@beagleboard.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@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