From: Kumar Gala <galak@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] driver core: Add ability for arch code to setup pdev_archdata
Date: Fri, 8 Jul 2011 00:16:20 -0500 [thread overview]
Message-ID: <A300A787-C750-44BF-B2EB-E09A3534058B@kernel.crashing.org> (raw)
In-Reply-To: <20110708042235.GA26357@kroah.com>
On Jul 7, 2011, at 11:22 PM, Greg KH wrote:
> On Thu, Jul 07, 2011 at 11:00:41PM -0500, Kumar Gala wrote:
>> On some architectures we need to setup pdev_archdata before we add the
>> device. Waiting til a bus_notifier is too late since we might need the
>> pdev_archdata in the bus notifier. One example is setting up of dma_mask
>> pointers such that it can be used in a bus_notifier.
>>
>> We add weak noop version of arch_setup_pdev_archdata() and allow the arch
>> code to override with access the full definitions of struct device,
>> struct platform_device, and struct pdev_archdata.
>>
>> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>> ---
>> v4:
>> * Move to use a weak function based on comments from Greg
>> v3:
>> * Add more comments and add missing call to arch_setup_pdev_archdata in
>> platform_device_register
>> v2:
>> * Added license, and comments about arch_setup_pdev_archdata()
>> per Mike's comments
>>
>> drivers/base/platform.c | 22 ++++++++++++++++++++++
>> include/linux/platform_device.h | 1 +
>> 2 files changed, 23 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
>> index 1c291af..060686d 100644
>> --- a/drivers/base/platform.c
>> +++ b/drivers/base/platform.c
>> @@ -32,6 +32,26 @@ struct device platform_bus = {
>> EXPORT_SYMBOL_GPL(platform_bus);
>>
>> /**
>> + * arch_setup_pdev_archdata - Allow manipulation of archdata before its used
>> + * @dev: platform device
>> + *
>> + * This is called before platform_device_add() such that any pdev_archdata may
>> + * be setup before the platform_notifier is called. So if a user needs to
>> + * manipulate any relevant information in the pdev_archdata they can do:
>> + *
>> + * platform_devic_alloc()
>> + * ... manipulate ...
>> + * platform_device_add()
>> + *
>> + * And if they don't care they can just call platform_device_register() and
>> + * everything will just work out.
>> + */
>> +void __weak arch_setup_pdev_archdata(struct platform_device *pdev)
>> +{
>> + return ;
>> +}
>
> The "return" isn't needed, nor is the extra ' ' there, right? :)
yep, removed the ';' as well ;)
> Change that and you can take this through the ppc tree and add a:
> Acked-by: Greg Kroah-Hartman
> to them.
Ack added to all.
thanks
- k
prev parent reply other threads:[~2011-07-08 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 4:00 Kumar Gala
2011-07-08 4:00 ` [PATCH v4 2/3] powerpc: implement arch_setup_pdev_archdata Kumar Gala
2011-07-08 4:00 ` [PATCH v4 3/3] powerpc: Dont require a dma_ops struct to set dma mask Kumar Gala
2011-07-08 4:22 ` [PATCH v4 1/3] driver core: Add ability for arch code to setup pdev_archdata Greg KH
2011-07-08 5:16 ` Kumar Gala [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=A300A787-C750-44BF-B2EB-E09A3534058B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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®