From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 36A7BB6F6B for ; Thu, 7 Jul 2011 23:55:54 +1000 (EST) Subject: Re: [PATCH v3 1/3] driver core: Add ability for arch code to setup pdev_archdata Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Kumar Gala In-Reply-To: <20110701220900.GA28971@kroah.com> Date: Thu, 7 Jul 2011 08:55:44 -0500 Message-Id: <597354F4-D1D4-4BC0-9251-FDDC31B1E2A1@kernel.crashing.org> References: <1308744176-24491-1-git-send-email-galak@kernel.crashing.org> <1308828839-27349-1-git-send-email-galak@kernel.crashing.org> <20110701220900.GA28971@kroah.com> To: Greg KH Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Jul 1, 2011, at 5:09 PM, Greg KH wrote: > On Thu, Jun 23, 2011 at 06:33:57AM -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. >>=20 >> We add noop version of arch_setup_pdev_archdata() in >> and allow the arch code to override = with >> access the full definitions of struct device, struct platform_device, = and >> struct pdev_archdata. >=20 > Isn't there some way to use "weak" symbols to keep us from having to > create this .h file in every single arch and then if the arch wants to > define it, it does so? >=20 > That should make this patch simpler, right? >=20 > thanks, >=20 > greg k-h Changing to weak should be doable if we are ok with the additional = function call always happening. - k