Hi,
On Wednesday 29 June 2016 11:44 PM, Hans de Goede wrote:
> Hi Kishon,
>
> The "USB: Fix of_usb_get_dr_mode_by_phy with a shared phy block"
> patch on which this series depends is in usb-next now:
>
>
Nice work.
Sure i will try your path, last time i tried otg i had kernel exception when
loading musb driver.
I would like setup usb otg in device mode as g_ether or cdrom drive emulation
to loading bootable iso with gpio sw for iso selection yes i dream :)
But for now I try to translate audio
Hi,
On Wed, Jun 29, 2016 at 08:16:39PM +0200, Hans de Goede wrote:
> Hi Bin Liu,
>
> The "USB: Fix of_usb_get_dr_mode_by_phy with a shared phy block"
> patch on which this patch indirectly depends is in usb-next now:
>
>
On 29.6.2016 22:45, Maxime Ripard wrote:
> Hi,
>
> On Sat, Jun 25, 2016 at 04:50:24PM +0200, Ondřej Jirman wrote:
>> On 25.6.2016 09:02, Maxime Ripard wrote:
>>> On Sat, Jun 25, 2016 at 09:02:48AM +0800, Chen-Yu Tsai wrote:
On Sat, Jun 25, 2016 at 6:51 AM, Ondřej Jirman
Hi,
On Sat, Jun 25, 2016 at 04:50:24PM +0200, Ondřej Jirman wrote:
> On 25.6.2016 09:02, Maxime Ripard wrote:
> > On Sat, Jun 25, 2016 at 09:02:48AM +0800, Chen-Yu Tsai wrote:
> >> On Sat, Jun 25, 2016 at 6:51 AM, Ondřej Jirman wrote:
> >>> Hello,
> >>>
> >>> comments below.
>
Hi,
On Wed, Jun 29, 2016 at 08:46:59PM +0200, Hans de Goede wrote:
> The auxtek t004 has its otg usb vbus hardwired to 5v (likely in case
> people use it to power the board instead of the dedicated power micro
> usb connector), it does have an id pin, so it allows full otg
> functionality.
I
On Wed, Jun 29, 2016 at 08:47:02PM +0200, Hans de Goede wrote:
> The a10s mk802 uses a rtl8189es sdio wifi chip, add a node enabling
> the mmc1 controller, this enables using the wifi chip (together with
> an out of tree sdio driver for it).
>
> Signed-off-by: Hans de Goede
On Wed, Jun 29, 2016 at 08:47:01PM +0200, Hans de Goede wrote:
> Add a node describing the axp152 pmic to the mk802 dts, note there are
> no regulator nodes as we do not yet support the regulators on the
> axp152.
>
> Signed-off-by: Hans de Goede
Applied, thanks!
Maxime
--
On Wed, Jun 29, 2016 at 08:47:00PM +0200, Hans de Goede wrote:
> Enable the otg controller, the id pin is not connected so enable
> it in peripheral only mode.
>
> Signed-off-by: Hans de Goede
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel
On Wednesday, June 29, 2016 10:54:38 PM CEST Priit Laes wrote:
> On Wed, 2016-06-29 at 21:33 +0200, Arnd Bergmann wrote:
> > What is the size of this nvram file? As it's board specific, I wonder
> > if we can simply include it inside of the DT verbatim. I remember
> > doing that (in the pre-dtb
On Wed, 2016-06-29 at 21:33 +0200, Arnd Bergmann wrote:
> On Wednesday, June 29, 2016 8:51:44 PM CEST Arend Van Spriel wrote:
> > > Typical wifi devices will have some sort of non volatile storage
> > > on board to not only store the ethernet(mac) address, but also
> > > to contain e.g. info about
Does anyone have any info on how Broadcom 5Ghz chipsets work with the
new FCC rules about locked down firmware? Is it possible to get FCC
certification at 5Ghz without being forced to lock down the whole
kernel?
On Wednesday, June 29, 2016 8:51:44 PM CEST Arend Van Spriel wrote:
> > Typical wifi devices will have some sort of non volatile storage
> > on board to not only store the ethernet(mac) address, but also
> > to contain e.g. info about the antenna gain so that the firmware
> > and/or the driver can
On 29-6-2016 20:51, Arend Van Spriel wrote:
> On 29-6-2016 20:01, Hans de Goede wrote:
>> Hi,
>>
>> On 29-06-16 19:00, Kalle Valo wrote:
>>> Hans de Goede writes:
>>>
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
> Hi,
>
> On 29 June 2016 at 16:04,
On 29-6-2016 20:01, Hans de Goede wrote:
> Hi,
>
> On 29-06-16 19:00, Kalle Valo wrote:
>> Hans de Goede writes:
>>
>>> Hi,
>>>
>>> On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
> Add a
The a10s mk802 uses a rtl8189es sdio wifi chip, add a node enabling
the mmc1 controller, this enables using the wifi chip (together with
an out of tree sdio driver for it).
Signed-off-by: Hans de Goede
---
arch/arm/boot/dts/sun5i-a10s-mk802.dts | 9 +
1 file
The auxtek t004 has its otg usb vbus hardwired to 5v (likely in case
people use it to power the board instead of the dedicated power micro
usb connector), it does have an id pin, so it allows full otg
functionality.
Signed-off-by: Hans de Goede
---
Enable the otg controller, the id pin is not connected so enable
it in peripheral only mode.
Signed-off-by: Hans de Goede
---
arch/arm/boot/dts/sun5i-a10s-mk802.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i-a10s-mk802.dts
Add a node describing the axp152 pmic to the mk802 dts, note there are
no regulator nodes as we do not yet support the regulators on the
axp152.
Signed-off-by: Hans de Goede
---
arch/arm/boot/dts/sun5i-a10s-mk802.dts | 14 ++
1 file changed, 14 insertions(+)
Hi Bin Liu,
The "USB: Fix of_usb_get_dr_mode_by_phy with a shared phy block"
patch on which this patch indirectly depends is in usb-next now:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next=ce15ed4c5dfb3f7757e6611902aed5db253af977
Can you please merge this now?
Hi Kishon,
The "USB: Fix of_usb_get_dr_mode_by_phy with a shared phy block"
patch on which this series depends is in usb-next now:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next=ce15ed4c5dfb3f7757e6611902aed5db253af977
Can you please merge this series?
Regards,
The A31 companion pmic (axp221) does not generate vbus change interrupts
when the board is driving vbus, so we must poll when using the pmic for
vbus-det _and_ we're driving vbus.
Signed-off-by: Hans de Goede
Acked-by: Kishon Vijay Abraham I
---
Changes in
Use the new of_usb_get_dr_mode_by_phy() function to get the dr_mode
from the musb controller node instead of assuming that having an id_det
gpio means otg mode, and not having one means host mode.
Implement peripheral-only mode by adding a sun4i_usb_phy0_get_id_det
helper which looks at the
HI,
On 29-06-16 19:01, Kalle Valo wrote:
Hans de Goede writes:
The cubietruck uses an ap6210 sdio wifi module, set brcm,nvram_file_name
to brcmfmac43362-ap6210.txt so that we can ship the ap6210 specific
nvram file in linunx-firmware to get the wifi to work out of the
Hi,
On 29-06-16 19:00, Kalle Valo wrote:
Hans de Goede writes:
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename
Hans de Goede writes:
> The cubietruck uses an ap6210 sdio wifi module, set brcm,nvram_file_name
> to brcmfmac43362-ap6210.txt so that we can ship the ap6210 specific
> nvram file in linunx-firmware to get the wifi to work out of the box
> without users needing to download
Hans de Goede writes:
> Hi,
>
> On 29-06-16 16:42, Jonas Gorski wrote:
>> Hi,
>>
>> On 29 June 2016 at 16:04, Hans de Goede wrote:
>>> Add a brcm,nvram_file_name dt property to allow overruling the default
>>> nvram filename for sdio devices. The idea
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename for sdio devices. The idea is that we can specify a
board specific nvram file, e.g.
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
> Add a brcm,nvram_file_name dt property to allow overruling the default
> nvram filename for sdio devices. The idea is that we can specify a
> board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
> with an
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename for sdio devices. The idea is that we can specify a
board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
with an ap6210 wifi sdio module and ship this in linux-firmware, so
that wifi will work out
The auxtek t004 uses a toc9002 sdio wifi module, the android nvram file
for this is for an older firmware which does not work with the mainline
kernel driver.
So we set brcm,nvram_file_name to brcmfmac43362-ap6210.txt which
works fine for this wifi module.
Setting brcm,nvram_file_name allows us
The wits pro uses an ap6476 sdio wifi module, we do not have a nvram file
for this, so set brcm,nvram_file_name to brcmfmac43362-ap6210.txt which
works fine for this wifi module.
Setting brcm,nvram_file_name allows us to ship the ap6210 specific nvram
file in linux-firmware to get the wifi to
Hi,
On 23-06-16 11:33, Hans de Goede wrote:
Hi,
On 23-06-16 00:25, Rob Herring wrote:
On Wed, Jun 22, 2016 at 12:59 PM, Hans de Goede wrote:
Some devices need a while to boot their firmware after providing clks /
de-asserting resets before they are ready to receive sdio
On Tue, 28 Jun 2016 22:45:02 +0200
Maxime Ripard wrote:
> On Tue, Jun 28, 2016 at 05:37:35PM +0200, Jean-Francois Moine wrote:
> > +/* --- prepare / enable --- */
> > +int ccu_prepare(struct clk_hw *hw)
> > +{
> > + struct ccu *ccu = hw2ccu(hw);
> > +
> > +
34 matches
Mail list logo