From: Wolfram Sang <wsa@the-dreams.de>
To: Erico Nunes <erico.nunes@datacom.ind.br>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] i2c-dev: switch from register_chrdev to cdev API
Date: Fri, 27 May 2016 13:17:45 +0200 [thread overview]
Message-ID: <20160527111745.GA1663@katana> (raw)
In-Reply-To: <1462301143-6084-1-git-send-email-erico.nunes@datacom.ind.br>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
On Tue, May 03, 2016 at 03:45:43PM -0300, Erico Nunes wrote:
> i2c-dev had never moved away from the older register_chrdev interface to
> implement its char device registration. The register_chrdev API has the
> limitation of enabling only up to 256 i2c-dev busses to exist.
>
> Large platforms with lots of i2c devices (i.e. pluggable transceivers)
> with dedicated busses may have to exceed that limit.
> In particular, there are also platforms making use of the i2c bus
> multiplexing API, which instantiates a virtual bus for each possible
> multiplexed selection.
>
> This patch removes the register_chrdev usage and replaces it with the
> less old cdev API, which takes away the 256 i2c-dev bus limitation.
> It should not have any other impact for i2c bus drivers or user space.
>
> This patch has been tested on qemu x86 and qemu powerpc platforms with
> the aid of a module which adds and removes 5000 virtual i2c busses, as
> well as validated on an existing powerpc hardware platform which makes
> use of the i2c bus multiplexing API.
> i2c-dev busses with device minor numbers larger than 256 have also been
> validated to work with the existing i2c-tools.
>
> Signed-off-by: Erico Nunes <erico.nunes@datacom.ind.br>
Applied to for-next, thanks! I'll try to still get it into v4.7.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-27 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 18:45 [PATCH 1/1] i2c-dev: switch from register_chrdev to cdev API Erico Nunes
2016-05-27 11:17 ` Wolfram Sang [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=20160527111745.GA1663@katana \
--to=wsa@the-dreams.de \
--cc=erico.nunes@datacom.ind.br \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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