All of lore.kernel.org
 help / color / mirror / Atom feed
From: m.silentcreek@gmail.com (m.silentcreek at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG - Bananapi USB not working on Mainline
Date: Sat, 19 Dec 2015 13:39:36 -0800 (PST)	[thread overview]
Message-ID: <ed63cc0b-fb90-4947-ab4c-b89655538a1a@googlegroups.com> (raw)
In-Reply-To: <ec8d762c-3e2b-4438-a43e-ae2740f8a5f3@googlegroups.com>

Hi,

Am Samstag, 19. Dezember 2015 20:38:08 UTC+1 schrieb Hans de Goede:
> The sunxi usb-phy driver now requires extcon (due to the added otg support), maybe the defconfig is not enabling extcon and thereby you are not getting the sunxi usb-phy driver build, or not build-in at least ?
> 
> Can you edit .config after the make defconfig and see what the value for CONFIG_PHY_SUN4I_USB is ?

I found the solution! The problem is CONFIG_AXP20X_POWER which was introduced in 4.4-rc1 but defaults to no and not set in sunxi_defconfig. Adding CONFIG_AXP20X_POWER=y to sunxi_defconfig solves that and get's my USB devices working again on linux 4.4-rc5. I actually brought that up on IRC once, but at that time nobody seemed to know so I forgot it again.

Anyway, wouldn't it be a better to just have it automatically be selected when e.g. CONFIG_PHY_SUN4I_USB or something else that depends on it is enabled?

Regards,

Timo

  parent reply	other threads:[~2015-12-19 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOP4N=_Ux0FPSRep7AfBVovd59LeDTbBjH=LBdfWDb6Mc3e=Fg@mail.gmail.com>
2015-12-18 20:22 ` BUG - Bananapi USB not working on Mainline m.silentcreek at gmail.com
2015-12-19 19:15   ` m.silentcreek at gmail.com
     [not found] ` <ec8d762c-3e2b-4438-a43e-ae2740f8a5f3@googlegroups.com>
2015-12-19 21:39   ` m.silentcreek at gmail.com [this message]
     [not found]     ` <CAOP4N=98cjUYVAvEngdOXXdXeive7HB_ChC4B+uAASG5tKP1dg@mail.gmail.com>
2015-12-22 14:42       ` [linux-sunxi] " m.silentcreek at gmail.com
2015-12-27 21:40         ` Maxime Ripard

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=ed63cc0b-fb90-4947-ab4c-b89655538a1a@googlegroups.com \
    --to=m.silentcreek@gmail.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 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.