From: Felipe Balbi <balbi@ti.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Balbi, Felipe" <balbi@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
linux-main <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 3/3] drivers: cleanup Kconfig stuff
Date: Tue, 19 Oct 2010 14:28:17 +0300 [thread overview]
Message-ID: <20101019112817.GK31170@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <AANLkTikmc1DmHZuhySM1gourjETsaXoCvgfqk7p-b6aQ@mail.gmail.com>
Hi,
On Tue, Oct 19, 2010 at 05:52:10AM -0500, Felipe Contreras wrote:
>I see, but is it possible that in a board you have the two? If not,
Yes. N900 is one of them :-) It has twl4030-usb for VBUS/ID (id isn't
used) and isp1707 for data lines. It's insane but it's becoming more and
more common to see a HW with two transceivers.
>there must be a way to find the correct transceiver based on the
>configuration. If yes, then there must be a way to select a sensible
>one by default, rather than not having any.
True, but currently that's not the case. We needed a real usb
transceiver "class" (or something else) where you have something like:
struct usb_xceiv {
struct list_head head;
struct device dev;
unsigned capabilities;
...
};
then you define a transceiver with:
struct usb_xceiv twl4030_usb {
.name = "twl4030-usb",
.capabilities = USB_XCEIV_CAP_VBUS
| USB_XCEIV_CAP_DETECT_CHARGER
| USB_XCEIV_CAP_DATA
| USB_XCEIV_CAP_WHATEVER_BOARD_NEEDS,
...
};
capabilities will also be board-specific in most cases, so you could
bring that from platform_data. Currently there's no such thing and I'm
too busy with musb/ehci/ohci/UDC Class to start that.
BTW, this also means the otg_transceiver is a mis-name as a transceiver
is needed in any connection is isn't TLL (transceiver-less link), so you
have usb transceiver in host-only and gadget-only configurations too.
If nobody starts the usb_xceiv class, I'll do it at some point and while
doing that drivers/usb/otg will be renamed to drivers/usb/xceiv together
with all structures and headers. Drivers/usb/otg will hold real otg
peculiarities.
>This way, for example it would be possible to get rid of some lines in
>a minimal n900_defconfig (used in MeeGo[1]), and eventually hopefully
>get rid of all of them (except CONFIG_SND_OMAP_SOC_RX51=y).
true, it would also allow you to have one binary for all your products
:-) althought not so optimal, it's good to ease development/testing.
--
balbi
prev parent reply other threads:[~2010-10-19 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 8:04 [PATCH 0/3] usb: geneirc Kconfig fixes Felipe Contreras
2010-10-19 8:04 ` [PATCH 1/3] usb: fix Kconfig warning Felipe Contreras
2010-10-19 8:20 ` Felipe Balbi
2010-10-19 8:04 ` [PATCH 2/3] usb: trivial Kconfig cleanups Felipe Contreras
2010-10-19 8:15 ` Felipe Balbi
2010-10-19 8:25 ` Felipe Contreras
2010-10-19 8:29 ` Felipe Balbi
2010-10-19 8:04 ` [PATCH 3/3] drivers: cleanup Kconfig stuff Felipe Contreras
2010-10-19 8:18 ` Felipe Balbi
2010-10-19 8:34 ` Felipe Contreras
2010-10-19 9:01 ` Felipe Balbi
2010-10-19 9:55 ` Felipe Contreras
2010-10-19 10:12 ` Felipe Balbi
2010-10-19 10:52 ` Felipe Contreras
2010-10-19 11:28 ` Felipe Balbi [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=20101019112817.GK31170@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=felipe.contreras@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®