linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
Cc: "Cliff Cai" <cliff.cai@analog.com>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	"Dinh Nguyen" <Dinh.Nguyen@freescale.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Nicolas Ferre" <nicolas.ferre@atmel.com>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	"Julia Lawall" <julia@diku.dk>,
	"Philipp Zabel" <philipp.zabel@gmail.com>,
	"Mark Brown" <broonie@opensource.wolfsonmicro.com>,
	"Felipe Balbi" <felipe.balbi@nokia.com>,
	"Andrea Gelmini" <andrea.gelmini@gelma.net>,
	"Robert Jarzmik" <robert.jarzmik@free.fr>,
	"Fabien Chouteau" <fabien.chouteau@barco.com>,
	"Dan Carpenter" <error27@gmail.com>,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	"Vladimir Zapolskiy" <vzapolskiy@gmail.com>,
	"Sergei Shtylyov" <sshtylyov@ru.mvista.com>,
	"Vincent Sanders" <support@simtec.co.uk>,
	"Marc Singer" <elf@buici.com>,
	"André Goddard Rosa" <andre.goddard@gmail.com>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Sean MacLennan" <smaclennan@pikatech.com>,
	"Russell King" <rmk+kernel@arm.linux.org.uk>,
	"Tobias Klauser" <tklauser@distanz.ch>,
	"Marc Kleine-Budde" <m.kleine-budde@pengutronix.de>,
	"Eirik Aanonsen" <eaa@wprmedical.com>,
	"Mike Frysinger" <vapier@gentoo.org>,
	"Thomas Dahlmann" <dahlmann.thomas@arcor.de>,
	linux-geode@lists.infradead.org,
	"Ben Dooks" <ben-linux@fluff.org>,
	"Magnus Damm" <damm@igel.co.jp>,
	"Anton Vorontsov" <avorontsov@ru.mvista.com>,
	"Andrew Victor" <linux@maxim.org.za>,
	linux-arm-kernel@lists.infradead.org,
	"Anatolij Gustschin" <agust@denx.de>,
	"Eric Miao" <eric.y.miao@gmail.com>,
	"Németh Márton" <nm127@freemail.hu>,
	"Jiri Kosina" <jkosina@suse.cz>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	linux-usb@vger.kernel.org, "Harro Haan" <hrhaan@gmail.com>,
	"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
	"H Hartley Sweeten" <hsweeten@visionengravers.com>,
	"Paul Mundt" <lethal@linux-sh.org>, "Tejun Heo" <tj@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Cory Maccarrone" <darkstar6262@gmail.com>
Subject: Re: [PATCH RFC] usb gadget: introduce usb_gadget_probe_driver
Date: Fri, 30 Jul 2010 17:26:02 +0200	[thread overview]
Message-ID: <20100730152602.GA28042@pengutronix.de> (raw)
In-Reply-To: <op.vgnwp8107p4s8u@pikus>

Hello Michał,

On Fri, Jul 30, 2010 at 05:16:46PM +0200, Michał Nazarewicz wrote:
> On Fri, 30 Jul 2010 16:49:14 +0200, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
>
>> This is like usb_gadget_register_driver with the only difference that it
>> gets the bind function as parameter instead of using driver->bind.  This
>> allows fixing section mismatches like
>>
>> 	WARNING: drivers/usb/gadget/g_printer.o(.data+0xc): Section mismatch in
>> 	reference from the variable printer_driver to the function
>> 	.init.text:printer_bind()
>> 	The variable printer_driver references
>> 	the function __init printer_bind()
>>
>> by using usb_gadget_probe_driver with driver->bind = NULL.  When all
>> drivers are fixed to use the new function the bind member of struct
>> usb_gadget_driver can go away.
>>
>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>> Cc: Michal Nazarewicz <m.nazarewicz@samsung.com>
>> Cc: Greg Kroah-Hartman <gregkh@suse.de>
>> ---
>> Hello,
>>
>> there is an alternative patch in Greg's tree [1], but IMHO mine is
>> better as it doesn't need __ref.
>>
>> Thoughts?
>
> Personally I don't see advantage of this over changing the __init to __ref.
> Or am I missing something?  I see your patch as an unnecessary API change.
> The way I understand it, __ref was introduced exactly for cases like this
> one where function is referenced from "normal" data but used only during
> init.  Could you try to clarify for me why you think your solution is
> better then mine?
- Using __ref instead of __init moves all bind functions from .init.text
  to .text and so the code isn't freed after booting or module loading.
  (OK, you could fix this by marking the driver structs as __ref and
  keep __init for the bind functions.)

- Using __ref might hide section mismatches.  (Your patch hasn't this
  problem as the bind functions used to live in .init.text, so any
  reference to .init should be OK assuming that it was OK to live in
  .init.text in the first place.  But when marking the driver structs
  this is an issue.)  That's why I don't like __ref and said my patch
  were better as it doesn't make use of it.

- The bind functions are only called at init time, so there is no need
  to save a pointer to it.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2010-07-30 15:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 14:49 [PATCH RFC] usb gadget: introduce usb_gadget_probe_driver Uwe Kleine-König
2010-07-30 15:14 ` Julia Lawall
2010-07-30 15:28   ` Uwe Kleine-König
2010-07-30 15:16 ` Michał Nazarewicz
2010-07-30 15:26   ` Uwe Kleine-König [this message]
2010-07-30 16:08     ` Michał Nazarewicz
2010-07-30 18:57       ` Uwe Kleine-König
2010-07-30 18:46     ` David Brownell
2010-08-02  9:39 ` Michał Nazarewicz
2010-08-02 12:39   ` [PATCH] usb gadget: don't save bind callback in struct usb_gadget_driver Uwe Kleine-König
2010-08-02 12:51     ` Julia Lawall
2010-08-02 13:12       ` Uwe Kleine-König
2010-08-02 22:54         ` Greg KH
2010-08-02 14:25     ` Michał Nazarewicz

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=20100730152602.GA28042@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=Dinh.Nguyen@freescale.com \
    --cc=agust@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=andre.goddard@gmail.com \
    --cc=andrea.gelmini@gelma.net \
    --cc=avorontsov@ru.mvista.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cliff.cai@analog.com \
    --cc=dahlmann.thomas@arcor.de \
    --cc=damm@igel.co.jp \
    --cc=darkstar6262@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=eaa@wprmedical.com \
    --cc=elf@buici.com \
    --cc=eric.y.miao@gmail.com \
    --cc=error27@gmail.com \
    --cc=fabien.chouteau@barco.com \
    --cc=felipe.balbi@nokia.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=gregkh@suse.de \
    --cc=hrhaan@gmail.com \
    --cc=hsweeten@visionengravers.com \
    --cc=jkosina@suse.cz \
    --cc=julia@diku.dk \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=m.kleine-budde@pengutronix.de \
    --cc=m.nazarewicz@samsung.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=nm127@freemail.hu \
    --cc=philipp.zabel@gmail.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=robert.jarzmik@free.fr \
    --cc=smaclennan@pikatech.com \
    --cc=sshtylyov@ru.mvista.com \
    --cc=stern@rowland.harvard.edu \
    --cc=support@simtec.co.uk \
    --cc=tj@kernel.org \
    --cc=tklauser@distanz.ch \
    --cc=tony@atomide.com \
    --cc=vapier@gentoo.org \
    --cc=vzapolskiy@gmail.com \
    --cc=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).