License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 21:07:57 +07:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2006-01-05 00:17:11 +07:00
|
|
|
/*
|
|
|
|
|
* arch/arm/mach-ixp4xx/nas100d-setup.c
|
|
|
|
|
*
|
|
|
|
|
* NAS 100d board-setup
|
|
|
|
|
*
|
2008-02-03 18:05:49 +07:00
|
|
|
* Copyright (C) 2008 Rod Whitby <rod@whitby.id.au>
|
|
|
|
|
*
|
|
|
|
|
* based on ixdp425-setup.c:
|
2006-01-05 00:17:11 +07:00
|
|
|
* Copyright (C) 2003-2004 MontaVista Software, Inc.
|
2008-02-03 18:05:49 +07:00
|
|
|
* based on nas100d-power.c:
|
|
|
|
|
* Copyright (C) 2005 Tower Technologies
|
|
|
|
|
* based on nas100d-io.c
|
|
|
|
|
* Copyright (C) 2004 Karen Spearel
|
2006-01-05 00:17:11 +07:00
|
|
|
*
|
|
|
|
|
* Author: Alessandro Zummo <a.zummo@towertech.it>
|
|
|
|
|
* Author: Rod Whitby <rod@whitby.id.au>
|
|
|
|
|
* Maintainers: http://www.nslu2-linux.org/
|
|
|
|
|
*
|
|
|
|
|
*/
|
2011-07-26 16:53:52 +07:00
|
|
|
#include <linux/gpio.h>
|
2008-02-02 06:04:05 +07:00
|
|
|
#include <linux/if_ether.h>
|
2008-02-03 18:05:49 +07:00
|
|
|
#include <linux/irq.h>
|
|
|
|
|
#include <linux/jiffies.h>
|
|
|
|
|
#include <linux/timer.h>
|
2006-01-05 00:17:11 +07:00
|
|
|
#include <linux/serial.h>
|
|
|
|
|
#include <linux/serial_8250.h>
|
2006-06-23 04:21:01 +07:00
|
|
|
#include <linux/leds.h>
|
2008-02-03 18:05:49 +07:00
|
|
|
#include <linux/reboot.h>
|
2008-01-29 06:38:44 +07:00
|
|
|
#include <linux/i2c.h>
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
#include <linux/gpio/machine.h>
|
2008-09-06 18:10:45 +07:00
|
|
|
#include <linux/io.h>
|
2006-01-05 00:17:11 +07:00
|
|
|
#include <asm/mach-types.h>
|
|
|
|
|
#include <asm/mach/arch.h>
|
|
|
|
|
#include <asm/mach/flash.h>
|
|
|
|
|
|
2009-11-16 22:06:47 +07:00
|
|
|
#define NAS100D_SDA_PIN 5
|
|
|
|
|
#define NAS100D_SCL_PIN 6
|
|
|
|
|
|
|
|
|
|
/* Buttons */
|
|
|
|
|
#define NAS100D_PB_GPIO 14 /* power button */
|
|
|
|
|
#define NAS100D_RB_GPIO 4 /* reset button */
|
|
|
|
|
|
|
|
|
|
/* Power control */
|
|
|
|
|
#define NAS100D_PO_GPIO 12 /* power off */
|
|
|
|
|
|
|
|
|
|
/* LEDs */
|
|
|
|
|
#define NAS100D_LED_WLAN_GPIO 0
|
|
|
|
|
#define NAS100D_LED_DISK_GPIO 3
|
|
|
|
|
#define NAS100D_LED_PWR_GPIO 15
|
|
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
static struct flash_platform_data nas100d_flash_data = {
|
|
|
|
|
.map_name = "cfi_probe",
|
|
|
|
|
.width = 2,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct resource nas100d_flash_resource = {
|
|
|
|
|
.flags = IORESOURCE_MEM,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct platform_device nas100d_flash = {
|
|
|
|
|
.name = "IXP4XX-Flash",
|
|
|
|
|
.id = 0,
|
|
|
|
|
.dev.platform_data = &nas100d_flash_data,
|
|
|
|
|
.num_resources = 1,
|
|
|
|
|
.resource = &nas100d_flash_resource,
|
|
|
|
|
};
|
|
|
|
|
|
2008-01-29 06:38:44 +07:00
|
|
|
static struct i2c_board_info __initdata nas100d_i2c_board_info [] = {
|
|
|
|
|
{
|
2008-04-30 04:11:40 +07:00
|
|
|
I2C_BOARD_INFO("pcf8563", 0x51),
|
2008-01-29 06:38:44 +07:00
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
|
2008-02-02 06:03:56 +07:00
|
|
|
static struct gpio_led nas100d_led_pins[] = {
|
2006-06-23 04:21:01 +07:00
|
|
|
{
|
2007-10-31 21:00:07 +07:00
|
|
|
.name = "nas100d:green:wlan",
|
2008-02-02 06:03:56 +07:00
|
|
|
.gpio = NAS100D_LED_WLAN_GPIO,
|
|
|
|
|
.active_low = true,
|
2006-06-23 04:21:01 +07:00
|
|
|
},
|
|
|
|
|
{
|
2007-10-31 21:00:07 +07:00
|
|
|
.name = "nas100d:blue:power", /* (off=flashing) */
|
2008-02-02 06:03:56 +07:00
|
|
|
.gpio = NAS100D_LED_PWR_GPIO,
|
|
|
|
|
.active_low = true,
|
2006-06-23 04:21:01 +07:00
|
|
|
},
|
|
|
|
|
{
|
2007-10-31 21:00:07 +07:00
|
|
|
.name = "nas100d:yellow:disk",
|
2008-02-02 06:03:56 +07:00
|
|
|
.gpio = NAS100D_LED_DISK_GPIO,
|
|
|
|
|
.active_low = true,
|
2006-06-23 04:21:01 +07:00
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
|
2008-02-02 06:03:56 +07:00
|
|
|
static struct gpio_led_platform_data nas100d_led_data = {
|
|
|
|
|
.num_leds = ARRAY_SIZE(nas100d_led_pins),
|
|
|
|
|
.leds = nas100d_led_pins,
|
|
|
|
|
};
|
|
|
|
|
|
2006-06-23 04:21:01 +07:00
|
|
|
static struct platform_device nas100d_leds = {
|
2008-02-02 06:03:56 +07:00
|
|
|
.name = "leds-gpio",
|
2006-06-23 04:21:01 +07:00
|
|
|
.id = -1,
|
2008-02-02 06:03:56 +07:00
|
|
|
.dev.platform_data = &nas100d_led_data,
|
2006-06-23 04:21:01 +07:00
|
|
|
};
|
|
|
|
|
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
static struct gpiod_lookup_table nas100d_i2c_gpiod_table = {
|
2018-05-26 23:37:34 +07:00
|
|
|
.dev_id = "i2c-gpio.0",
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
.table = {
|
|
|
|
|
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", NAS100D_SDA_PIN,
|
2017-09-11 04:03:32 +07:00
|
|
|
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", NAS100D_SCL_PIN,
|
2017-09-11 04:03:32 +07:00
|
|
|
NULL, 1, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
},
|
2006-01-05 00:17:11 +07:00
|
|
|
};
|
|
|
|
|
|
2008-01-28 00:14:46 +07:00
|
|
|
static struct platform_device nas100d_i2c_gpio = {
|
|
|
|
|
.name = "i2c-gpio",
|
2006-01-05 00:17:11 +07:00
|
|
|
.id = 0,
|
2008-01-28 00:14:46 +07:00
|
|
|
.dev = {
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
.platform_data = NULL,
|
2008-01-28 00:14:46 +07:00
|
|
|
},
|
2006-01-05 00:17:11 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct resource nas100d_uart_resources[] = {
|
|
|
|
|
{
|
|
|
|
|
.start = IXP4XX_UART1_BASE_PHYS,
|
|
|
|
|
.end = IXP4XX_UART1_BASE_PHYS + 0x0fff,
|
|
|
|
|
.flags = IORESOURCE_MEM,
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
.start = IXP4XX_UART2_BASE_PHYS,
|
|
|
|
|
.end = IXP4XX_UART2_BASE_PHYS + 0x0fff,
|
|
|
|
|
.flags = IORESOURCE_MEM,
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct plat_serial8250_port nas100d_uart_data[] = {
|
|
|
|
|
{
|
|
|
|
|
.mapbase = IXP4XX_UART1_BASE_PHYS,
|
|
|
|
|
.membase = (char *)IXP4XX_UART1_BASE_VIRT + REG_OFFSET,
|
|
|
|
|
.irq = IRQ_IXP4XX_UART1,
|
|
|
|
|
.flags = UPF_BOOT_AUTOCONF,
|
|
|
|
|
.iotype = UPIO_MEM,
|
|
|
|
|
.regshift = 2,
|
|
|
|
|
.uartclk = IXP4XX_UART_XTAL,
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
.mapbase = IXP4XX_UART2_BASE_PHYS,
|
|
|
|
|
.membase = (char *)IXP4XX_UART2_BASE_VIRT + REG_OFFSET,
|
|
|
|
|
.irq = IRQ_IXP4XX_UART2,
|
|
|
|
|
.flags = UPF_BOOT_AUTOCONF,
|
|
|
|
|
.iotype = UPIO_MEM,
|
|
|
|
|
.regshift = 2,
|
|
|
|
|
.uartclk = IXP4XX_UART_XTAL,
|
|
|
|
|
},
|
|
|
|
|
{ }
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct platform_device nas100d_uart = {
|
|
|
|
|
.name = "serial8250",
|
|
|
|
|
.id = PLAT8250_DEV_PLATFORM,
|
|
|
|
|
.dev.platform_data = nas100d_uart_data,
|
|
|
|
|
.num_resources = 2,
|
|
|
|
|
.resource = nas100d_uart_resources,
|
|
|
|
|
};
|
|
|
|
|
|
2008-02-02 06:04:05 +07:00
|
|
|
/* Built-in 10/100 Ethernet MAC interfaces */
|
|
|
|
|
static struct eth_plat_info nas100d_plat_eth[] = {
|
|
|
|
|
{
|
|
|
|
|
.phy = 0,
|
|
|
|
|
.rxq = 3,
|
|
|
|
|
.txreadyq = 20,
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct platform_device nas100d_eth[] = {
|
|
|
|
|
{
|
|
|
|
|
.name = "ixp4xx_eth",
|
|
|
|
|
.id = IXP4XX_ETH_NPEB,
|
|
|
|
|
.dev.platform_data = nas100d_plat_eth,
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
static struct platform_device *nas100d_devices[] __initdata = {
|
2008-01-28 00:14:46 +07:00
|
|
|
&nas100d_i2c_gpio,
|
2006-01-05 00:17:11 +07:00
|
|
|
&nas100d_flash,
|
2006-06-23 04:21:01 +07:00
|
|
|
&nas100d_leds,
|
2008-02-02 06:04:05 +07:00
|
|
|
&nas100d_eth[0],
|
2006-01-05 00:17:11 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void nas100d_power_off(void)
|
|
|
|
|
{
|
|
|
|
|
/* This causes the box to drop the power and go dead. */
|
|
|
|
|
|
2013-09-10 16:19:55 +07:00
|
|
|
/* enable the pwr cntl gpio and assert power off */
|
|
|
|
|
gpio_direction_output(NAS100D_PO_GPIO, 1);
|
2006-01-05 00:17:11 +07:00
|
|
|
}
|
|
|
|
|
|
2008-02-03 18:05:49 +07:00
|
|
|
/* This is used to make sure the power-button pusher is serious. The button
|
|
|
|
|
* must be held until the value of this counter reaches zero.
|
|
|
|
|
*/
|
|
|
|
|
static int power_button_countdown;
|
|
|
|
|
|
|
|
|
|
/* Must hold the button down for at least this many counts to be processed */
|
|
|
|
|
#define PBUTTON_HOLDDOWN_COUNT 4 /* 2 secs */
|
|
|
|
|
|
2017-08-29 01:28:21 +07:00
|
|
|
static void nas100d_power_handler(struct timer_list *unused);
|
2017-10-05 06:27:04 +07:00
|
|
|
static DEFINE_TIMER(nas100d_power_timer, nas100d_power_handler);
|
2008-02-03 18:05:49 +07:00
|
|
|
|
2017-08-29 01:28:21 +07:00
|
|
|
static void nas100d_power_handler(struct timer_list *unused)
|
2008-02-03 18:05:49 +07:00
|
|
|
{
|
|
|
|
|
/* This routine is called twice per second to check the
|
|
|
|
|
* state of the power button.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
if (gpio_get_value(NAS100D_PB_GPIO)) {
|
|
|
|
|
|
|
|
|
|
/* IO Pin is 1 (button pushed) */
|
|
|
|
|
if (power_button_countdown > 0)
|
|
|
|
|
power_button_countdown--;
|
|
|
|
|
|
|
|
|
|
} else {
|
|
|
|
|
|
|
|
|
|
/* Done on button release, to allow for auto-power-on mods. */
|
|
|
|
|
if (power_button_countdown == 0) {
|
|
|
|
|
/* Signal init to do the ctrlaltdel action,
|
|
|
|
|
* this will bypass init if it hasn't started
|
|
|
|
|
* and do a kernel_restart.
|
|
|
|
|
*/
|
|
|
|
|
ctrl_alt_del();
|
|
|
|
|
|
|
|
|
|
/* Change the state of the power LED to "blink" */
|
2013-09-10 16:19:55 +07:00
|
|
|
gpio_set_value(NAS100D_LED_PWR_GPIO, 0);
|
2008-02-03 18:05:49 +07:00
|
|
|
} else {
|
|
|
|
|
power_button_countdown = PBUTTON_HOLDDOWN_COUNT;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
mod_timer(&nas100d_power_timer, jiffies + msecs_to_jiffies(500));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static irqreturn_t nas100d_reset_handler(int irq, void *dev_id)
|
|
|
|
|
{
|
|
|
|
|
/* This is the paper-clip reset, it shuts the machine down directly. */
|
|
|
|
|
machine_power_off();
|
|
|
|
|
|
|
|
|
|
return IRQ_HANDLED;
|
|
|
|
|
}
|
|
|
|
|
|
2013-09-10 16:19:55 +07:00
|
|
|
static int __init nas100d_gpio_init(void)
|
|
|
|
|
{
|
|
|
|
|
if (!machine_is_nas100d())
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* The power button on the Iomega NAS100d is on GPIO 14, but
|
|
|
|
|
* it cannot handle interrupts on that GPIO line. So we'll
|
|
|
|
|
* have to poll it with a kernel timer.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* Request the power off GPIO */
|
|
|
|
|
gpio_request(NAS100D_PO_GPIO, "power off");
|
|
|
|
|
|
|
|
|
|
/* Make sure that the power button GPIO is set up as an input */
|
|
|
|
|
gpio_request(NAS100D_PB_GPIO, "power button");
|
|
|
|
|
gpio_direction_input(NAS100D_PB_GPIO);
|
|
|
|
|
|
|
|
|
|
/* Set the initial value for the power button IRQ handler */
|
|
|
|
|
power_button_countdown = PBUTTON_HOLDDOWN_COUNT;
|
|
|
|
|
|
|
|
|
|
mod_timer(&nas100d_power_timer, jiffies + msecs_to_jiffies(500));
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
device_initcall(nas100d_gpio_init);
|
|
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
static void __init nas100d_init(void)
|
|
|
|
|
{
|
2008-02-02 06:04:05 +07:00
|
|
|
uint8_t __iomem *f;
|
|
|
|
|
int i;
|
|
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
ixp4xx_sys_init();
|
|
|
|
|
|
2006-03-09 06:45:10 +07:00
|
|
|
/* gpio 14 and 15 are _not_ clocks */
|
|
|
|
|
*IXP4XX_GPIO_GPCLKR = 0;
|
|
|
|
|
|
2006-01-06 03:59:29 +07:00
|
|
|
nas100d_flash_resource.start = IXP4XX_EXP_BUS_BASE(0);
|
|
|
|
|
nas100d_flash_resource.end =
|
|
|
|
|
IXP4XX_EXP_BUS_BASE(0) + ixp4xx_exp_bus_size - 1;
|
|
|
|
|
|
i2c: gpio: Convert to use descriptors
This converts the GPIO-based I2C-driver to using GPIO
descriptors instead of the old global numberspace-based
GPIO interface. We:
- Convert the driver to unconditionally grab two GPIOs
from the device by index 0 (SDA) and 1 (SCL) which
will work fine with device tree and descriptor tables.
The existing device trees will continue to work just
like before, but without any roundtrip through the
global numberspace.
- Brutally convert all boardfiles still passing global
GPIOs by registering descriptor tables associated with
the devices instead so this driver does not need to keep
supporting passing any GPIO numbers as platform data.
There is no stepwise approach as elegant as this, I
strongly prefer this big hammer over any antsteps for this
conversion. This way the old GPIO numbers go away and
NEVER COME BACK.
Special conversion for the different boards utilizing
I2C-GPIO:
- EP93xx (arch/arm/mach-ep93xx): pretty straight forward as
all boards were using the same two GPIO lines, just define
these two in a lookup table for "i2c-gpio" and register
these along with the device. None of them define any
other platform data so just pass NULL as platform data.
This platform selects GPIOLIB so all should be smooth.
The pins appear on a gpiochip for bank "G" as pins 1 (SDA)
and 0 (SCL).
- IXP4 (arch/arm/mach-ixp4): descriptor tables have to
be registered for each board separately. They all use
"IXP4XX_GPIO_CHIP" so it is pretty straight forward.
Most board define no other platform data than SCL/SDA
so they can drop the #include of <linux/i2c-gpio.h> and
assign NULL to platform data.
The "goramo_mlr" (Goramo Multilink Router) board is a bit
worrisome: it implements its own I2C bit-banging in the
board file, and optionally registers an I2C serial port,
but claims the same GPIO lines for itself in the board file.
This is not going to work: there will be competition for the
GPIO lines, so delete the optional extra I2C bus instead, no
I2C devices are registered on it anyway, there are just hints
that it may contain an EEPROM that may be accessed from
userspace. This needs to be fixed up properly by the serial
clock using I2C emulation so drop a note in the code.
- KS8695 board acs5k (arch/arm/mach-ks8695/board-acs5.c)
has some platform data in addition to the pins so it needs to
be kept around sans GPIO lines. Its GPIO chip is named
"KS8695" and the arch selects GPIOLIB.
- PXA boards (arch/arm/mach-pxa/*) use some of the platform
data so it needs to be preserved here. The viper board even
registers two GPIO I2Cs. The gpiochip is named "gpio-pxa" and
the arch selects GPIOLIB.
- SA1100 Simpad (arch/arm/mach-sa1100/simpad.c) defines a GPIO
I2C bus, and the arch selects GPIOLIB.
- Blackfin boards (arch/blackfin/bf533 etc) for these I assume
their I2C GPIOs refer to the local gpiochip defined in
arch/blackfin/kernel/bfin_gpio.c names "BFIN-GPIO".
The arch selects GPIOLIB. The boards get spiked with
IF_ENABLED(I2C_GPIO) but that is a side effect of it
being like that already (I would just have Kconfig select
I2C_GPIO and get rid of them all.) I also delete any
platform data set to 0 as it will get that value anyway
from static declartions of platform data.
- The MIPS selects GPIOLIB and the Alchemy machine is using
two local GPIO chips, one of them has a GPIO I2C. We need
to adjust the local offset from the global number space here.
The ATH79 has a proper GPIO driver in drivers/gpio/gpio-ath79.c
and AFAICT the chip is named "ath79-gpio" and the PB44
PCF857x expander spawns from this on GPIO 1 and 0. The latter
board only use the platform data to specify pins so it can be
cut altogether after this.
- The MFD Silicon Motion SM501 is a special case. It dynamically
spawns an I2C bus off the MFD using sm501_create_subdev().
We use an approach to dynamically create a machine descriptor
table and attach this to the "SM501-LOW" or "SM501-HIGH"
gpiochip. We use chip-local offsets to grab the right lines.
We can get rid of two local static inline helpers as part
of this refactoring.
Cc: Steven Miao <realmz6@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Heiko Schocher <hs@denx.de>
Acked-by: Wu, Aaron <Aaron.Wu@analog.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2017-09-10 06:30:46 +07:00
|
|
|
gpiod_add_lookup_table(&nas100d_i2c_gpiod_table);
|
2008-01-29 06:38:44 +07:00
|
|
|
i2c_register_board_info(0, nas100d_i2c_board_info,
|
|
|
|
|
ARRAY_SIZE(nas100d_i2c_board_info));
|
|
|
|
|
|
2007-05-24 04:41:53 +07:00
|
|
|
/*
|
|
|
|
|
* This is only useful on a modified machine, but it is valuable
|
2006-06-23 04:21:01 +07:00
|
|
|
* to have it first in order to see debug messages, and so that
|
|
|
|
|
* it does *not* get removed if platform_add_devices fails!
|
|
|
|
|
*/
|
|
|
|
|
(void)platform_device_register(&nas100d_uart);
|
|
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
platform_add_devices(nas100d_devices, ARRAY_SIZE(nas100d_devices));
|
2008-02-02 06:04:05 +07:00
|
|
|
|
2008-02-03 18:05:49 +07:00
|
|
|
pm_power_off = nas100d_power_off;
|
|
|
|
|
|
|
|
|
|
if (request_irq(gpio_to_irq(NAS100D_RB_GPIO), &nas100d_reset_handler,
|
2014-03-05 03:59:03 +07:00
|
|
|
IRQF_TRIGGER_LOW, "NAS100D reset button", NULL) < 0) {
|
2008-02-03 18:05:49 +07:00
|
|
|
|
|
|
|
|
printk(KERN_DEBUG "Reset Button IRQ %d not available\n",
|
|
|
|
|
gpio_to_irq(NAS100D_RB_GPIO));
|
|
|
|
|
}
|
|
|
|
|
|
2008-02-02 06:04:05 +07:00
|
|
|
/*
|
|
|
|
|
* Map in a portion of the flash and read the MAC address.
|
|
|
|
|
* Since it is stored in BE in the flash itself, we need to
|
|
|
|
|
* byteswap it if we're in LE mode.
|
|
|
|
|
*/
|
|
|
|
|
f = ioremap(IXP4XX_EXP_BUS_BASE(0), 0x1000000);
|
|
|
|
|
if (f) {
|
|
|
|
|
for (i = 0; i < 6; i++)
|
|
|
|
|
#ifdef __ARMEB__
|
|
|
|
|
nas100d_plat_eth[0].hwaddr[i] = readb(f + 0xFC0FD8 + i);
|
|
|
|
|
#else
|
|
|
|
|
nas100d_plat_eth[0].hwaddr[i] = readb(f + 0xFC0FD8 + (i^3));
|
|
|
|
|
#endif
|
|
|
|
|
iounmap(f);
|
|
|
|
|
}
|
2008-10-28 05:59:26 +07:00
|
|
|
printk(KERN_INFO "NAS100D: Using MAC address %pM for port 0\n",
|
|
|
|
|
nas100d_plat_eth[0].hwaddr);
|
2008-02-02 06:04:05 +07:00
|
|
|
|
2006-01-05 00:17:11 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
MACHINE_START(NAS100D, "Iomega NAS 100d")
|
|
|
|
|
/* Maintainer: www.nslu2-linux.org */
|
2011-07-06 09:38:13 +07:00
|
|
|
.atag_offset = 0x100,
|
2006-01-05 00:17:11 +07:00
|
|
|
.map_io = ixp4xx_map_io,
|
2012-03-07 04:01:53 +07:00
|
|
|
.init_early = ixp4xx_init_early,
|
2006-01-05 00:17:11 +07:00
|
|
|
.init_irq = ixp4xx_init_irq,
|
2012-11-09 02:40:59 +07:00
|
|
|
.init_time = ixp4xx_timer_init,
|
2006-01-05 00:17:11 +07:00
|
|
|
.init_machine = nas100d_init,
|
2011-07-06 09:28:09 +07:00
|
|
|
#if defined(CONFIG_PCI)
|
|
|
|
|
.dma_zone_size = SZ_64M,
|
|
|
|
|
#endif
|
2011-11-05 19:10:55 +07:00
|
|
|
.restart = ixp4xx_restart,
|
2006-01-05 00:17:11 +07:00
|
|
|
MACHINE_END
|