All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frieder Schrempf <frieder.schrempf@exceet.de>
To: Peter Chen <peter.chen@nxp.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] usb: chipidea: Add minimal support for HSIC interface on i.MX6QDL
Date: Wed, 10 Oct 2018 14:52:07 +0200	[thread overview]
Message-ID: <e13ac59e-6698-8ef2-685e-75cd5ed35d98@exceet.de> (raw)
In-Reply-To: <VI1PR04MB5327D0F4AA27C5AED5C535388BE70@VI1PR04MB5327.eurprd04.prod.outlook.com>

Hi Peter,

On 09.10.2018 03:24, Peter Chen wrote:
>   
>>
>> The topic has been discussed before: [1] And there is some implementation in the
>> vendor kernel: [2]
>>
>> It seems like two things need to be done:
>>
>> 1. Switch the pinmux of the strobe signal to use a pullup after
>>     the core has been initialized.
>> 2. Enable HSIC mode and HSIC clock
>>
>> This patch only implements these basics in a minimal approach.
>> You need to have an additional pinmux setting "active" in the dt, that sets the pullup.
>>
>> It was tested with the SMSC LAN9730 USB Ethernet adapter on the iMXceet Solo S
>> board.
>>
> 
> Thanks, I should do it earlier, I could not find a suitable board with HSIC support at mainline kernel.
> It is very kind that you could help on it and test function at real board. My suggestion is
> follow all flows in Link [2] since we need to cover suspend/resume and remote wakeup.

It seems like power management and other things in the linux-imx kernel 
are not fully implemented in mainline so there are quite a few differences.

My knowledge of USB, etc. is very limited, so I guess this is currently 
beyond my skills. Can you or someone else provide a patch to get 
started? I could help with testing, reviewing, etc.

Or maybe you can point out what needs to be done in more detail?

Thanks,
Frieder

WARNING: multiple messages have this Message-ID (diff)
From: Frieder Schrempf <frieder.schrempf@exceet.de>
To: Peter Chen <peter.chen@nxp.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC] usb: chipidea: Add minimal support for HSIC interface on i.MX6QDL
Date: Wed, 10 Oct 2018 14:52:07 +0200	[thread overview]
Message-ID: <e13ac59e-6698-8ef2-685e-75cd5ed35d98@exceet.de> (raw)

Hi Peter,

On 09.10.2018 03:24, Peter Chen wrote:
>   
>>
>> The topic has been discussed before: [1] And there is some implementation in the
>> vendor kernel: [2]
>>
>> It seems like two things need to be done:
>>
>> 1. Switch the pinmux of the strobe signal to use a pullup after
>>     the core has been initialized.
>> 2. Enable HSIC mode and HSIC clock
>>
>> This patch only implements these basics in a minimal approach.
>> You need to have an additional pinmux setting "active" in the dt, that sets the pullup.
>>
>> It was tested with the SMSC LAN9730 USB Ethernet adapter on the iMXceet Solo S
>> board.
>>
> 
> Thanks, I should do it earlier, I could not find a suitable board with HSIC support at mainline kernel.
> It is very kind that you could help on it and test function at real board. My suggestion is
> follow all flows in Link [2] since we need to cover suspend/resume and remote wakeup.

It seems like power management and other things in the linux-imx kernel 
are not fully implemented in mainline so there are quite a few differences.

My knowledge of USB, etc. is very limited, so I guess this is currently 
beyond my skills. Can you or someone else provide a patch to get 
started? I could help with testing, reviewing, etc.

Or maybe you can point out what needs to be done in more detail?

Thanks,
Frieder

  reply	other threads:[~2018-10-10 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 13:29 [RFC] usb: chipidea: Add minimal support for HSIC interface on i.MX6QDL Frieder Schrempf
2018-10-08 13:29 ` Frieder Schrempf
2018-10-09  1:24 ` Peter Chen
2018-10-09  1:24   ` Peter Chen
2018-10-10 12:52   ` Frieder Schrempf [this message]
2018-10-10 12:52     ` Frieder Schrempf
2018-10-12  1:19     ` Peter Chen
2018-10-12  1:19       ` Peter Chen
2018-10-15 10:28       ` Frieder Schrempf
2018-10-15 10:28         ` Frieder Schrempf

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=e13ac59e-6698-8ef2-685e-75cd5ed35d98@exceet.de \
    --to=frieder.schrempf@exceet.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@nxp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.