linux-kernel - Re: [PATCH 4.19 02/74] ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190807022635.GR17747@sasha-vm>
Date:   Tue, 6 Aug 2019 22:26:35 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Douglas Anderson <dianders@...omium.org>,
        Heiko Stuebner <heiko@...ech.de>
Subject: Re: [PATCH 4.19 02/74] ARM: dts: rockchip: Make rk3288-veyron-minnie
 run at hs200

On Mon, Aug 05, 2019 at 04:41:12PM +0200, Pavel Machek wrote:
>Hi!
>
>> [ Upstream commit 1c0479023412ab7834f2e98b796eb0d8c627cd62 ]
>>
>> As some point hs200 was failing on rk3288-veyron-minnie.  See commit
>> 984926781122 ("ARM: dts: rockchip: temporarily remove emmc hs200 speed
>> from rk3288 minnie").  Although I didn't track down exactly when it
>> started working, it seems to work OK now, so let's turn it back on.
>>
>> To test this, I booted from SD card and then used this script to
>> stress the enumeration process after fixing a memory leak [1]:
>>   cd /sys/bus/platform/drivers/dwmmc_rockchip
>>   for i in $(seq 1 3000); do
>>     echo "========================" $i
>>     echo ff0f0000.dwmmc > unbind
>>     sleep .5
>>     echo ff0f0000.dwmmc > bind
>>     while true; do
>>       if [ -e /dev/mmcblk2 ]; then
>>         break;
>>       fi
>>       sleep .1
>>     done
>>   done
>>
>> It worked fine.
>
>This may not be suitable for stable. So... hs200 started working in
>mainline sometime. That does not mean it was fixed in all the various
>stable trees, too.
>
>How was this tested in respective -stable releases?

If you know of any other patches required on older stable kernels to
make this work I'll be more than happy to take them...

--
Thanks,
Sasha