[RFC][WAS:bcmai][PATCH V2] axi: add AXI bus driver

Greg KH greg at kroah.com
Fri Apr 8 18:01:57 EDT 2011


On Fri, Apr 08, 2011 at 09:45:00PM +0200, Rafał Miłecki wrote:
> Cc: Michael Büsch <mb at bu3sch.de>
> Cc: Larry Finger <Larry.Finger at lwfinger.net>
> Cc: George Kashperko <george at znau.edu.ua>
> Cc: Arend van Spriel <arend at broadcom.com>
> Cc: linux-arm-kernel at lists.infradead.org <linux-arm-kernel at lists.infradead.org>
> Cc: Russell King <rmk at arm.linux.org.uk>
> Cc: Arnd Bergmann <arnd at arndb.de>
> Cc: linuxdriverproject <devel at linuxdriverproject.org>
> Cc: linux-kernel at vger.kernel.org <linux-kernel at vger.kernel.org>
> Signed-off-by: Rafał Miłecki <zajec5 at gmail.com>
> ---
> This is second try for introducing new bus driver.
> V2: Rename to axi
>     Use DEFINE_PCI_DEVICE_TABLE in bridge
>     Make use of pr_fmt and pr_*
>     Store core class
>     Rename bridge to not b43 specific
>     Replace magic 0x1000 with BCMAI_CORE_SIZE
>     Remove some old "ssb" names and defines
>     Move BCMAI_ADDR_BASE def
>     Add drvdata field
> TODO:
> - Interrupts
> - Reloading driver

Please add to the TODO list:
	- Documentation/ABI entries for new sysfs files
	- proper Kconfig entry documentation for the different options
	- remove unneeded pcicore_write* wrapper functions that do
	  nothing.


> +static void axi_release_core_dev(struct device *dev)
> +{
> +	kfree(dev);
> +}

This is wrong, unless you are really only creating a 'struct device'.
Why are you doing that instead of embedding struct device in your
structure?

thanks,

greg k-h



More information about the linux-arm-kernel mailing list