From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Julian Margetson <runaway@candw.ms>,
"contact@a-eon.com" <contact@a-eon.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: [FSL P5020 P5040 PPC] Onboard SD card doesn't work anymore after the 'mmc-v5.4-2' updates
Date: Mon, 20 Jan 2020 10:17:31 +0100 [thread overview]
Message-ID: <fda179eb-df5f-ba87-aaf0-524fffca745b@xenosoft.de> (raw)
In-Reply-To: <CAPDyKFoydOuSE=Eaq168=2_Ycouo7hzyw+RZXhGq7q4D4Qe8TQ@mail.gmail.com>
Am 16.01.20 um 16:46 schrieb Ulf Hansson:
> On Thu, 16 Jan 2020 at 12:18, Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>> Hi All,
>>
>> We still need the attached patch for our onboard SD card interface
>> [1,2]. Could you please add this patch to the tree?
> No, because according to previous discussion that isn't the correct
> solution and more importantly it will break other archs (if I recall
> correctly).
>
> Looks like someone from the ppc community needs to pick up the ball.
I am not sure if the ppc community have to fix this issue because your
updates (mmc-v5.4-2) are responsible for this issue. If nobody wants to
fix this issue then we will lost the onboard SD card support in the
future. PLEASE check the 'mmc-v5.4-2' updates again.
>
>> Thanks,
>> Christian
>>
>> [1] https://www.spinics.net/lists/linux-mmc/msg56211.html
> I think this discussion even suggested some viable solutions, so it
> just be a matter of sending a patch :-)
>
>> [2]
>> http://forum.hyperion-entertainment.com/viewtopic.php?f=58&t=4349&start=20#p49012
>>
> Kind regards
> Uffe
next prev parent reply other threads:[~2020-01-20 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200108093903.57620-1-hdegoede@redhat.com>
[not found] ` <20200108093903.57620-2-hdegoede@redhat.com>
[not found] ` <61bc9265-ece0-eeb6-d4a1-4631138ecf29@intel.com>
[not found] ` <8d67882d-04a8-0607-be4e-c1430b7fda21@redhat.com>
[not found] ` <84a32714-ba08-74a0-0c76-3c36db44dd68@intel.com>
[not found] ` <93446e09-5f12-800a-62fa-bf3ecea7273d@redhat.com>
[not found] ` <399ac7d5-2518-799a-595e-f6b6878cf4ab@intel.com>
2020-01-16 11:05 ` [FSL P5020 P5040 PPC] Onboard SD card doesn't work anymore after the 'mmc-v5.4-2' updates Christian Zigotzky
2020-01-16 15:46 ` Ulf Hansson
2020-01-20 9:17 ` Christian Zigotzky [this message]
2020-01-20 11:18 ` Ulf Hansson
2020-01-24 11:42 ` Michael Ellerman
2020-01-25 13:26 ` Christian Zigotzky
2020-01-28 11:55 ` Michael Ellerman
2020-01-28 7:58 ` [PASEMI PA6T PPC] Onboard CF card device with new SanDisk High (>8G) CF cards Christian Zigotzky
2020-01-28 8:08 ` Christoph Hellwig
2020-01-28 14:16 ` Rob Herring
2020-01-28 14:48 ` Christian Zigotzky
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=fda179eb-df5f-ba87-aaf0-524fffca745b@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=contact@a-eon.com \
--cc=darren@stevens-zone.net \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
--cc=runaway@candw.ms \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).