Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220620124146.5330-1-mtwget@gmail.com> <YrmMdcz9mJS1sXyS@atomide.com>
 <CAHRgzyOsxaC2HM=xAMxFUadTEdTBk-yiMjC=-Y=UynoiULSXDw@mail.gmail.com>
In-Reply-To: <CAHRgzyOsxaC2HM=xAMxFUadTEdTBk-yiMjC=-Y=UynoiULSXDw@mail.gmail.com>
From:   Yu-Tung Chang <mtwget@gmail.com>
Date:   Fri, 1 Jul 2022 14:14:41 +0800
Message-ID: <CAHRgzyOgmxTVV6sqSk_ZWYytergDj5haW=EdFCKCyTg+r6Zd-A@mail.gmail.com>
Subject: Re: [PATCH v2] ARM: dts: am33xx: Fix MMCHS0 dma properties
To:     Tony Lindgren <tony@atomide.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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Yu-Tung Chang <mtwget@gmail.com> =E4=BA=8E2022=E5=B9=B47=E6=9C=881=E6=97=A5=
=E5=91=A8=E4=BA=94 14:04=E5=86=99=E9=81=93=EF=BC=9A
>
> Tony Lindgren <tony@atomide.com> =E4=BA=8E2022=E5=B9=B46=E6=9C=8827=E6=97=
=A5=E5=91=A8=E4=B8=80 18:54=E5=86=99=E9=81=93=EF=BC=9A
>
> >
> > 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 t=
his
> > fix something for you?
> >
> It modified in commit b5e5090660742c838ddc0b5d1a001e6fe3d5bfd5,
> the dma of mmc1 was changed to edma_xbar and did not explain why it shoul=
d
> not match the document.
> > Regards,
> >
> > Tony
No evidence of any official documentation error, before submitting
b5e5090660742c838ddc0b5d1a001e6fe3d5bfd5, the mmc1 dma properties
matches the official documentation.