public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: hisilicon fixes for 4.18
Date: Thu, 12 Jul 2018 22:48:37 +0100	[thread overview]
Message-ID: <5B47CCB5.9000009@hisilicon.com> (raw)
In-Reply-To: <CAGoBSJoh0SKMBm=Hgh9rX8G+VcN93C3PxYiA56232OW76AWk-w@mail.gmail.com>

Hi Ryan,

On 2018/7/12 15:39, Ryan Grachek wrote:
> Hi All,
> 
> On Mon, Jul 2, 2018 at 1:06 AM, Wei Xu <xuwei5@hisilicon.com> wrote:
>> Hi Olof,
>>
>> On 2018/6/30 5:08, Olof Johansson wrote:
>>>
>>> On Thu, Jun 28, 2018 at 09:46:58PM +0100, Wei Xu wrote:
>>>>
>>>> Hi Olof, Hi Arnd,
>>>>
>>>> Please help to pull the following fix.
>>>> Thanks!
>>>>
>>>> Best Regards,
>>>> Wei
>>>>
>>>> ---
>>>>
>>>> The following changes since commit
>>>> ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>>>>
>>>>    Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>    git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-4.18
>>>>
>>>> for you to fetch changes up to a30449eb3ac908f26b4bc963a58039a5f2725ffa:
>>>>
>>>>    arm64: dts: hikey960: Define wl1837 power capabilities (2018-06-28
>>>> 17:07:44 +0100)
>>>>
>>>> ----------------------------------------------------------------
>>>> ARM64: hisi fixes for 4.18
>>>>
>>>> - Added power capabilities for the mmc host controller on the
>>>>    hikey and hikey960 boards to avoid broken wifi.
>>>
>>> Thanks, merged. However, this seems to keep wifi power on during suspend?
>>> That
>>> seems suboptimal for suspend power consumption. Any work going on to fix
>>> root
>>> cause?
>>
>>
>> Thanks!
>> I will sync with my colleagues about that issue and hope we can get a fix
>> soon.
>>
>> Best Regards,
>> Wei
>>
>>>
>>> -Olof
>>>
>>> .
>>>
>>
>>
> 
> According to Eyal Reizer from TI, "keep-power-in-suspend" is needed in
> case of planning to use "WoWLAN".
> In hindsight, I see this property was already enabled in the SoC file
> (hi3660.dtsi), so that issue had
> already existed prior to my patch. Should I submit patch to remove the
> property from both the SoC
> and board file?

Thanks! Please :)
I think we can remove it firstly and if the real user want to use the WoWLAN,
they can add it in their dts file.

Best Regards,
Wei

> 
> -Ryan
> 
> .
> 

      reply	other threads:[~2018-07-12 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 20:46 [GIT PULL] arm64: hisilicon fixes for 4.18 Wei Xu
2018-06-29 21:08 ` Olof Johansson
2018-07-02  6:06   ` Wei Xu
2018-07-12 14:39     ` Ryan Grachek
2018-07-12 21:48       ` Wei Xu [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=5B47CCB5.9000009@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.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