From: Tony Lindgren <tony@atomide.com>
To: Yu-Tung Chang <mtwget@gmail.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: am33xx: Fix MMCHS0 dma properties
Date: Mon, 4 Jul 2022 09:25:35 +0300 [thread overview]
Message-ID: <YsKH3xLpWw4X1h2P@atomide.com> (raw)
In-Reply-To: <CAHRgzyOgmxTVV6sqSk_ZWYytergDj5haW=EdFCKCyTg+r6Zd-A@mail.gmail.com>
* Yu-Tung Chang <mtwget@gmail.com> [220701 06:09]:
> Yu-Tung Chang <mtwget@gmail.com> 于2022年7月1日周五 14:04写道：
> >
> > Tony Lindgren <tony@atomide.com> 于2022年6月27日周一 18:54写道：
> >
> > >
> > > Hi,
> > >
> > > * YuTong Chang <mtwget@gmail.com> [220620 15:36]:
> > > > According to technical manual(table 11-24), the DMA of MMCHS0 should be
> > > > direct mapped.
> > >
> > > Could this be a bug in the manual assuming mmchs0 is working? Or does this
> > > fix something for you?
> > >
> > It modified in commit b5e5090660742c838ddc0b5d1a001e6fe3d5bfd5,
> > the dma of mmc1 was changed to edma_xbar and did not explain why it should
> > not match the document.
> > > Regards,
> > >
> > > Tony
> No evidence of any official documentation error, before submitting
> b5e5090660742c838ddc0b5d1a001e6fe3d5bfd5, the mmc1 dma properties
> matches the official documentation.
OK thanks for clarifying. will apply to fixes with a fixes tag.
Regards,
Tony
prev parent reply other threads:[~2022-07-04 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 12:41 [PATCH v2] ARM: dts: am33xx: Fix MMCHS0 dma properties YuTong Chang
2022-06-24 15:37 ` Krzysztof Kozlowski
2022-06-27 10:54 ` Tony Lindgren
2022-07-01 6:04 ` Yu-Tung Chang
2022-07-01 6:14 ` Yu-Tung Chang
2022-07-04 6:25 ` Tony Lindgren [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=YsKH3xLpWw4X1h2P@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mtwget@gmail.com \
--cc=robh+dt@kernel.org \
/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.