From: Ryusuke Sakato <ryusuke.sakato.bx@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] arm: shmobile: Lager Add USB and SATA support
Date: Wed, 10 Sep 2014 07:15:25 +0000 [thread overview]
Message-ID: <540FFA8D.6060602@renesas.com> (raw)
In-Reply-To: <1387370660-20481-1-git-send-email-valentine.barshak@cogentembedded.com>
Hi Hiep-san,
I believe that I should unite the conditions of the performance test of "CONFIG_CPU_FREQ is not set" on Upstream-v3.16-rc5,
and "CONFIG_CPU_FREQ=y" on uptream-v3.17-rc2.
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> ondemand
In order that you may not be subject to the influence of cpufreq, you should change
"CONFIG_CPU_FREQ is not set", or should perform the following setup.
 echo -n performance > /sys/device/system/cpu/cpu0/cpufreq/scaling_governor
 echo -n performance > /sys/device/system/cpu/cpu1/cpufreq/scaling_governor
 echo -n performance > /sys/device/system/cpu/cpu2/cpufreq/scaling_governor
 echo -n performance > /sys/device/system/cpu/cpu3/cpufreq/scaling_governor
Thank you,
Sakato.
(2014/09/10 14:18), カオ ミン ヒェップ wrote:
> Hi Sakato-san
>
> Thanks for your comment.
>
> On 09/10/2014 10:21 AM, Ryusuke Sakato wrote:
>> Hi Hiep-san,
>>
>> Can you check as CONFIG_CPU_FREQ is not set?
>>
>> When you perform a benchmark, you should check a /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>> setup of your userland.
> CONFIG_CPU_FREQ=y on default config,
> And I have just checked /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> Before writing:
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> ondemand
> just after writing:
> #cp /tmp/file-350mb /mnt/ ; cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
> ondemand
>
>
> Best regards,
> Cao Minh Hiep
>
>> Thank you,
>> Sakato.
>>
>> (2014/09/09 19:48), カオ ミン ヒェップ wrote:
>>> Hello,
>>>
>>> We are testing Serial-ATA driver on linux uptream-v3.17-rc2 on Lager(R8a7790 SoC),
>>> On this version Serial-ATA's Writing speed on HDD is about 42.61MB/s.
>>> This writing speed|| seems good, but on Upstream-v3.16-rc5 the writing speed was up to 66MB/s,
>>> Please see it when you have time.
>>>
>>> Best Regards,
>>> Jinso/Cao Minh Hiep.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 12/18/2013 09:44 PM, Valentine Barshak wrote:
>>>> I've decided to bundle USB and SATA patches together, since I've done SATA on top of USB.
>>>> Most of the SATA/USBHS/PCI USB host support patches for Lager are available in the respective
>>>> susbsystem git trees (for 3.14) but are still missing from the Renesas tree.
>>>>
>>>> So, in order to test these, the following patches from other subsystem trees are needed:
>>>> USB:
>>>> https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-rcar&idû178d8b2fab3f2a9f203c13ffe80cfd6e01bdf1
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?idÈba8115a21226fba3211085f570b128fa271e31
>>>> https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?h=next&idÃe5d2985ef720cbbdc63546a5c545ac4450d96e
>>>> https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id\x103e127d1f8f985e8a662da6537ebc5e08902ee3
>>>> https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id\x1ae5799ef63176cc75ec10e545cb65f620a82747
>>>>
>>>> SATA:
>>>> https://git.kernel.org/cgit/linux/kernel/git/tj/libata.git/commit/?h=for-3.14&idæ7adb4e669db834c1f95cbdf99bb4e9ec8455b3
>>>>
>>>> The USB channel 0 (CN6) is configured as PCI USB host if USB_RENESAS_USBHS_UDC is disabled.
>>>> Otherwise it is configured as USBHS device.
>>>> Please note that the following switches have to be set correctly as well:
>>>> PCI USB Host: SW5 - pin1; SW6 - pin1
>>>> USBHS device: SW5 - neutral; SW6 - pin3
>>>>
>>>> Valentine Barshak (5):
>>>> arm: shmobile: r8a7790: Add PCI USB host clock support
>>>> arm: shmobile: r8a7790: Add SATA clock
>>>> arm: shmobile: lager: Add USBHS support
>>>> arm: shmobile: lager: Add internal PCI support
>>>> arm: shmobile: lager: Add SATA support
>>>>
>>>> arch/arm/mach-shmobile/board-lager.c | 203 +++++++++++++++++++++++++++++++++
>>>> arch/arm/mach-shmobile/clock-r8a7790.c | 25 +++-
>>>> 2 files changed, 227 insertions(+), 1 deletion(-)
>>>>
>>>
>>
>
> .
>
next prev parent reply other threads:[~2014-09-10 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 12:44 [PATCH 0/5] arm: shmobile: Lager Add USB and SATA support Valentine Barshak
2013-12-19 10:09 ` Magnus Damm
2013-12-19 13:02 ` Valentine
2013-12-19 17:56 ` Valentine
2013-12-20 14:07 ` Valentine
2014-09-10 1:21 ` Ryusuke Sakato
2014-09-10 5:18 ` カオ ミン ヒェップ
2014-09-10 7:15 ` Ryusuke Sakato [this message]
2014-09-10 9:16 ` カオ ミン ヒェップ
2014-09-10 9:32 ` Khiem Nguyen
2014-09-11 9:35 ` カオ ミン ヒェップ
2014-09-11 10:20 ` Khiem Nguyen
2014-09-11 11:26 ` カオ ミン ヒェップ
2014-09-12 0:39 ` Khiem Nguyen
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=540FFA8D.6060602@renesas.com \
--to=ryusuke.sakato.bx@renesas.com \
--cc=linux-sh@vger.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 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).