Merge branch 'v3.8-samsung-fixes-3' of...

	return 0; /* a negative value on error, 0 on success. */

}

static void __devexit

static void

my_remove               (struct pci_dev *               pci_dev)

{

	my_device *my = pci_get_drvdata (pci_dev);

	/* Describe me. */

}

static int __devinit

static int

my_probe                (struct pci_dev *               pci_dev,

			 const struct pci_device_id *   pci_id)

{

	.id_table = my_pci_device_ids,

	.probe    = my_probe,

	.remove   = __devexit_p (my_remove),

	.remove   = my_remove,

	/* Power management functions. */

	.suspend  = my_suspend,

Following piece of code illustrates the usage of the SR-IOV API.

static int __devinit dev_probe(struct pci_dev *dev, const struct pci_device_id *id)

static int dev_probe(struct pci_dev *dev, const struct pci_device_id *id)

{

	pci_enable_sriov(dev, NR_VIRTFN);

	return 0;

}

static void __devexit dev_remove(struct pci_dev *dev)

static void dev_remove(struct pci_dev *dev)

{

	pci_disable_sriov(dev);

	.name =		"SR-IOV Physical Function driver",

	.id_table =	dev_id_table,

	.probe =	dev_probe,

	.remove =	__devexit_p(dev_remove),

	.remove =	dev_remove,

	.suspend =	dev_suspend,

	.resume =	dev_resume,

	.shutdown =	dev_shutdown,

			initializes.

	__exit		Exit code. Ignored for non-modular drivers.

	__devinit	Device initialization code.

			Identical to __init if the kernel is not compiled

			with CONFIG_HOTPLUG, normal function otherwise.

	__devexit	The same for __exit.

Tips on when/where to use the above attributes:

	o The module_init()/module_exit() functions (and all

	  initialization functions called _only_ from these)

	o Do not mark the struct pci_driver.

	o The ID table array should be marked __devinitconst; this is done

	  automatically if the table is declared with DEFINE_PCI_DEVICE_TABLE().

	o The probe() and remove() functions should be marked __devinit

	  and __devexit respectively.  All initialization functions

	  exclusively called by the probe() routine, can be marked __devinit.

	  Ditto for remove() and __devexit.

	o If mydriver_remove() is marked with __devexit(), then all address

	  references to mydriver_remove must use __devexit_p(mydriver_remove)

	  (in the struct pci_driver declaration for example).

	  __devexit_p() will generate the function name _or_ NULL if the

	  function will be discarded.  For an example, see drivers/net/tg3.c.

	o Do NOT mark a function if you are not sure which mark to use.

	  Better to not mark the function than mark the function wrong.

			.acpi_match_table  ACPI_PTR(mpu3050_acpi_match),

		},

		.probe		= mpu3050_probe,

		.remove		= __devexit_p(mpu3050_remove),

		.remove		= mpu3050_remove,

		.id_table	= mpu3050_ids,

	};

CSR SiRFprimaII pinmux controller

Required properties:

- compatible	: "sirf,prima2-pinctrl"

- reg		: Address range of the pinctrl registers

- interrupts    : Interrupts used by every GPIO group

- gpio-controller : Indicates this device is a GPIO controller

- interrupt-controller  : Marks the device node as an interrupt controller

Optional properties:

- sirf,pullups : if n-th bit of m-th bank is set, set a pullup on GPIO-n of bank m

- sirf,pulldowns : if n-th bit of m-th bank is set, set a pulldown on GPIO-n of bank m

Please refer to pinctrl-bindings.txt in this directory for details of the common

pinctrl bindings used by client devices.

SiRFprimaII's pinmux nodes act as a container for an abitrary number of subnodes.

Each of these subnodes represents some desired configuration for a group of pins.

Required subnode-properties:

- sirf,pins : An array of strings. Each string contains the name of a group.

- sirf,function: A string containing the name of the function to mux to the

  group.

  Valid values for group and function names can be found from looking at the

  group and function arrays in driver files:

  drivers/pinctrl/pinctrl-sirf.c

For example, pinctrl might have subnodes like the following:

 uart2_pins_a: uart2@0 {

         uart {

                 sirf,pins = "uart2grp";

                 sirf,function = "uart2";

         };

 };

 uart2_noflow_pins_a: uart2@1 {

         uart {

                 sirf,pins = "uart2_nostreamctrlgrp";

                 sirf,function = "uart2_nostreamctrl";

         };

 };

For a specific board, if it wants to use uart2 without hardware flow control,

it can add the following to its board-specific .dts file.

uart2: uart@0xb0070000 {

	pinctrl-names = "default";

	pinctrl-0 = <&uart2_noflow_pins_a>;

}