From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Robert Baldyga <r.baldyga@samsung.com>,
"balbi@ti.com" <balbi@ti.com>
Subject: Re: [PATCH] i2c: exynos5: register driver early in subsys initcall to avoid probe defer
Date: Thu, 19 Nov 2015 14:46:28 +0100 [thread overview]
Message-ID: <20151119134627.GA1567@katana> (raw)
In-Reply-To: <564DCCA9.3050604@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi Marek,
> This problem is known for ages, there were number of attempts to add
Yes, I heard of it, too.
> support for deferred probe or solve the problem of deferred UDC driver
> probe, but none got accepted so far:
Then they need to be worked on. AFAIK the rejection is based on
implementation details, not because the feature itself is not wanted,
or?
> Till now it worked somehow for boards with older i2c bus drivers, which
> were registered in subsys initcall. Boards, which use newer i2c bus drivers
> cannot be used with usb gadgets compiled-in.
Yes, because the above issue needs to be *fixed*, not workarounded. You
still have the option to carry your patch out-of-tree if fixing the
issue is not an option for you.
We already had problems here when someone tried to revert
subsys_initcall to module_init because of other dependency issues on
another particular board. So, the pain should really go where the fixing
is needed.
I hope you understand,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-19 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:23 [PATCH] i2c: exynos5: register driver early in subsys initcall to avoid probe defer Marek Szyprowski
2015-11-01 16:02 ` Wolfram Sang
2015-11-19 13:20 ` Marek Szyprowski
2015-11-19 13:46 ` 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=20151119134627.GA1567@katana \
--to=wsa@the-dreams.de \
--cc=b.zolnierkie@samsung.com \
--cc=balbi@ti.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=r.baldyga@samsung.com \
/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.