From: Krzysztof Kozlowski <krzk@kernel.org>
To: Richard Leitner <richard.leitner@skidata.com>
Cc: Linux USB List <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Richard Leitner <dev@g0hl1n.net>,
Stephen Boyd <stephen.boyd@linaro.org>
Subject: Re: Microchip USB Hub Driver Harmonization
Date: Wed, 17 May 2017 18:01:52 +0200 [thread overview]
Message-ID: <20170517160152.t34t43ocbzebpkfg@kozik-lap> (raw)
In-Reply-To: <ff5e74e7-a2b3-374e-63b0-d125105f437c@skidata.com>
On Wed, May 17, 2017 at 12:58:38PM +0200, Richard Leitner wrote:
> Hello,
> due to the fact (all?) the Microchip (former SMSC) USB hubs share the
> same I2C configuration interface, I'm currently working on harmonizing
> those USB Hub drivers. Currently this affects the usb251xb, usb3503 and
> usb4604 drivers. To avoid preventable efforts (and patch versions) I
> have some question on the preferred implementation:
>
> 1. Currently usb251xb uses i2c_smbus_*, usb3503 uses regmap_* and
> usb4604 uses i2c_master_* functions for the hub configuration. What
> would be the preferred solution?
regmap? It is already widely used for I2C drivers. I think most (or even
all?) new I2C drivers use regmap. It hides the real bus between common
regmap API.
> 2. What would be a good prefix for common headers/functions/macros/etc.?
> I thought of "mcusbhub"... Would that be OK? Or are there any
> conventions/better proposals on that?
If you are going to develop one driver for entire family, then you could
even choose just one name. Let's say the most generic.
I don't quite understand the meaning behind "harmonizing drivers".
> 3. Currently only usb3503 supports "platform data". Is this still needed
> or may it be removed?
I think it is still used, e.g. by:
arch/arm/boot/dts/exynos5250-spring.dts
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-05-17 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 10:58 Richard Leitner
2017-05-17 16:01 ` Krzysztof Kozlowski [this message]
2017-05-18 5:33 ` Richard Leitner
2017-05-18 7:46 ` Krzysztof Kozlowski
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=20170517160152.t34t43ocbzebpkfg@kozik-lap \
--to=krzk@kernel.org \
--cc=dev@g0hl1n.net \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=richard.leitner@skidata.com \
--cc=stephen.boyd@linaro.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®