Age | Commit message (Collapse) | Author |
|
The driver with the config option NFC_NXP_NCI_I2C now uses
devm_gpiod_get_index() with 4 arguments which is not supported in
backports.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
NFC_PN544_I2C uses devm_gpiod_get_index() now which is not available in
kernel < 3.17.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
NFC_NXP_NCI_I2C uses the linux/gpio/consumer.h which is not available
in kernel version < 3.13
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
VIDEO_FB_IVTV uses arch_phys_wc_add(), arch_phys_wc_del() and
pat_enabled() now which are not available in older kernel versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The driver VIDEO_ADP1653 now includes linux/gpio/consumer.h which is
not available in kernel versions < 3.13. This patch makes the driver
depend on kernel version >= 3.13.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The VIDEO_ADV7604 driver now makes use of
devm_gpiod_get_index_optional() which gets less parameters in older
kernel versions. This makes the driver depend on kernel >= 3.17. In
addition also the VIDEO_COBALT has to depend on this kernel version
because it selects VIDEO_ADV7604.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The drivers MEDIA_TUNER_FC2580 and MEDIA_TUNER_TUA9001 are using
devm_regmap_init_i2c() which is only believable on kernel >= 3.3, add a
dependency to the driver.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The drivers DVB_M88DS3103 and DVB_TS2020 are accessing some member in
struct regmap_config which is not available in kernel version < 3.8.
These drivers are getting selected by some other drivers, which are now
also depending on kernel >= 3.8, otherwise KConfig would ignore the
dependency on kernel >= 3.8
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
VIDEO_COBALT selects VIDEO_ADV7604, but VIDEO_ADV7604 should only be
build on kernel versions >= 3.13. On older kernel versions this causes
this warning which makes Kconfig ignore the dependency on kernel version
>= 3.13.
warning: (VIDEO_COBALT) selects VIDEO_ADV7604 which has unmet direct
dependencies (MEDIA_SUPPORT && !KERNEL_3_13 && m && <choice> &&
VIDEO_V4L2 && I2C && VIDEO_V4L2_SUBDEV_API && GPIOLIB)
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
devm_gpiod_get_optional() was not backported to older kernel versions
and the devm_gpiod_get_optional() function in kernel 3.16 has less
parameters.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This wifi driver was missing before.
This driver uses the cfg80211 so we should ship it.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The DVB_RTL2830 and DVB_RTL2832 driver are using the new regmap API
since commit b410dae and d101658 which we did not backport. Deactivate
this driver on affected kernel versions for now. In addition the
DVB_USB_RTL28XXU driver has to be deactivated because it depends on
these two modules.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
drivers/nfc/pn544/i2c.c includes linux/gpio/consumer.h since commit
0a5942c8, which we can not backport. Deactivate this driver on affected
kernel versions for now.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
netdev_rss_key_fill() uses net_get_random_once() and since
this depends on static keys and we've decided to only backport
that only down to 3.5 as that is when static key stuff settled we
only backport netdev_rss_key_fill() down to 3.5 as well. For details
on the net_get_random_once() / static key stuff refer to backports
commit 8cb8816d.
Backporting netdev_rss_key_fill requires us to throw in the
netdev_rss_key within our own backports module. We don't backport
the ability to query this *yet though*, but if we really wanted to
we can provide an interface for that:
For *packaging* [0] we have no other option but to currently provide
our own querying interface, that's silly though, in the future
if we extend sysctl interfaces to allow dynamic extensions we
could just peg what we need also within the backports module to
allow seemless integration. With shiny new *kernel integration*
support [1] though we can enable cherry picking the sysctl components,
and apply it to the older kernel -- however this would pose a change
in compartamentalized backporting strategy as currently used. It would
seem a allowing dynamic extensions to an existing sysctl interface
would be more efficient and would allow packaging to also take
advantage of this effort.
[0] https://backports.wiki.kernel.org/index.php/Documentation/packaging
[1] https://backports.wiki.kernel.org/index.php/Documentation/integration
commit 960fb622f85180f36d3aff82af53e2be3db2f888
Author: Eric Dumazet <edumazet@google.com>
Date: Sun Nov 16 06:23:05 2014 -0800
net: provide a per host RSS key generic infrastructure
RSS (Receive Side Scaling) typically uses Toeplitz hash and a 40 or 52 bytes
RSS key.
Some drivers use a constant (and well known key), some drivers use a random
key per port, making bonding setups hard to tune. Well known keys increase
attack surface, considering that number of queues is usually a power of two.
This patch provides infrastructure to help drivers doing the right thing.
netdev_rss_key_fill() should be used by drivers to initialize their RSS key,
even if they provide ethtool -X support to let user redefine the key later.
A new /proc/sys/net/core/netdev_rss_key file can be used to get the host
RSS key even for drivers not providing ethtool -x support, in case some
applications want to precisely setup flows to match some RX queues.
Tested:
myhost:~# cat /proc/sys/net/core/netdev_rss_key
11:63:99:bb:79:fb:a5:a7:07:45:b2:20:bf:02:42:2d:08:1a:dd:19:2b:6b:23:ac:56:28:9d:70:c3:ac:e8:16:4b:b7:c1:10:53:a4:78:41:36:40:74:b6:15:ca:27:44:aa:b3:4d:72
myhost:~# ethtool -x eth0
RX flow hash indirection table for eth0 with 8 RX ring(s):
0: 0 1 2 3 4 5 6 7
RSS hash key:
11:63:99:bb:79:fb:a5:a7:07:45:b2:20:bf:02:42:2d:08:1a:dd:19:2b:6b:23:ac:56:28:9d:70:c3:ac:e8:16:4b:b7:c1:10:53:a4:78:41
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
mcgrof@drvbp1 ~/backports (git::master)$ time ./gentree.py \
/home/mcgrof/linux-next /home/mcgrof/build/backports-20141117
Copy original source files ...
Applying patches from patches to /home/mcgrof/build/backports-20141117
...
Modify Kconfig tree ...
Rewrite Makefiles and Kconfig files ...
Done!
real 1m28.499s
user 13m25.112s
sys 0m47.804s
mcgrof@drvbp1 ~/build/backports-20141117 $ time \
/home/mcgrof/backports/devel/ckmake --allyesconfig
1 3.0.101 [ OK ]
2 3.1.10 [ OK ]
3 3.2.62 [ OK ]
4 3.3.8 [ OK ]
5 3.4.104 [ OK ]
6 3.5.7 [ OK ]
7 3.6.11 [ OK ]
8 3.7.10 [ OK ]
9 3.8.13 [ OK ]
10 3.9.11 [ OK ]
11 3.10.58 [ OK ]
12 3.11.10 [ OK ]
13 3.12.31 [ OK ]
14 3.13.11 [ OK ]
15 3.14.22 [ OK ]
16 3.15.10 [ OK ]
17 3.16.6 [ OK ]
18 3.17.1 [ OK ]
19 3.18-rc1 [ OK ]
real 42m18.874s
user 1179m40.500s
sys 138m54.452s
Cc: Eric Dumazet <edumazet@google.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
This driver depends on gpio consumer.h, that depends on some
built-in kernel functionality and while we can now backport
built-in stuff we'd need to make that depend on BACKPORT_INTEGRATE
and then figure out how to backport that functionality on integration.
This doesn't seem like a good candidate to test that with though.
Let's wait for something more desirable.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
It looks hard to backport IEEE802154 to older kernels, because it now
uses the new member ieee802154_ptr in struct net_device. This code was
added in upstream commit 98a18b6ffc7 "netdevice: add ieee802154_ptr to
net_device"
If someone knows how to backport this stuff please do so and revert
this patch.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
MEDIA_TUNER_M88RS6000T now uses devm_regmap_init_i2c()
One of the tuners DVB_SMIPCIE selects uses regmap_bulk_write()
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
During development of kernel integration support using CONFIG_BACKPORT
was evaluated as a prefix over CPTCFG even for packaging backports,
for some reason this change lifted some restrictions one some device
drivers which was present before and as such requires some changes to
the dependencies map file to ensure correct compilation for respective
kernel versions.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
IR_HIX5HD2 needs syscon, this has to be added to the Kconfig file and
on kernel < 3.7 it is completely missing.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Deactivate SOC_CAMERA because of missing backport for vb2_expbuf() in
kernel < 3.5.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
pt3 needs kthread_freezable_should_stop() which is not available on
these old kernels.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Deactivate all drivers using regmap_bulk_write() on kernel < 3.4.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
On kernel < 3.4 compiling ath10k with tracing results in huge compile
errors. Just deactivate it till someone fixes the problems. The same
compile error occurs in ath module with kernel 3.0.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
These drivers need regmap_bulk_write(), which was added in 3.4
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
It looks like no one is using the regulator drivers and maintaining
them costs some time because they often break. When someone needs
a specific driver please send a patch adding this one specific driver,
maintaining a small subset is not a problem, but maintaining all is a
big task.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This driver needs a new header file, which is not in the kernel < 3.17.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
AT86RF230 needs the devm_regmap_init_spi() function.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
These driver need clk_prepare_enable(), clk_disable_unprepare(),
devm_regulator_bulk_get() or devm_regmap_init_i2c()
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
They are depending in some headers only available in more recent kernel
versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This adds the cc2520.h and disables the driver on kernel < 3.5.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
While doing a make allmodconfig I noticed the following:
CC [M] /dev/shm/backports-next/drivers/media/i2c/adv7604.o
/dev/shm/backports-next/drivers/media/i2c/adv7604.c:31:33: fatal error: linux/gpio/consumer.h: No such file or directory
linux/gpio/consumer.h cannot be backported currently, as functions rely
on in-kernel functionality (GPIO_DEVRES). Bumping the minimum required
kernel version for ADV7604 to 3.13 where the header got introduced.
Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
[add comment with reason]
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The regulator palmas driver makes use of the new struct regulator_desc
enable_val and disable_val added via commit ca5d1b352 on v3.15 to help
overcome an issue on assumptions on how regulator drivers enable /
disable the regulator with only one value / mask. We can't port this
so just require at least v3.15 for it.
mcgrof@ergon ~/linux (git::master)$ git describe --contains ca5d1b352
v3.15-rc1~148^2~4^3
commit ca5d1b3524b4d90a2e2f1f71583c1dca6b96fd92
Author: Carlo Caione <carlo@caione.org>
Date: Wed Mar 5 22:11:29 2014 +0100
regulator: helpers: Modify helpers enabling multi-bit control
This patch extends the regulator helpers to account for device that use
multiple bits for control when using regmap enable/disable/bypass ops.
The actual regulator helpers wrongly assume that the regulator control
is always performed using single bits, using in the regulator_desc
struct only two parameters *_reg and *_mask defining register and mask
for control.
This patch extends this struct and introduces the helpers to take into
account devices where control is performed using multiple bits and
specific multi-bit values are used for enabling/disabling/bypassing the
regulator.
Signed-off-by: Carlo Caione <carlo@caione.org>
Signed-off-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The function devm_gpio_request_one() was backported some time ago.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
These drivers got new and not so easy backportable dependencies.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
These new drivers are compile tested only.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Compiling with older kernel versions causes some problems.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
mcgrof@drvbp1 ~/backports (git::master)$ time ./gentree.py --clean
/home/mcgrof/linux-next /home/mcgrof/build/next-20140409
Copy original source files ...
Apply patches ...
Modify Kconfig tree ...
Rewrite Makefiles and Kconfig files ...
Done!
real 1m30.186s
user 9m25.180s
sys 0m24.428s
mcgrof@drvbp1 ~/build/next-20140409 $ time ckmake --allyesconfig
1 3.0.101 [ OK ]
2 3.1.10 [ OK ]
3 3.2.54 [ OK ]
4 3.3.8 [ OK ]
5 3.4.79 [ OK ]
6 3.5.7 [ OK ]
7 3.6.11 [ OK ]
8 3.7.10 [ OK ]
9 3.8.13 [ OK ]
10 3.9.11 [ OK ]
11 3.10.29 [ OK ]
12 3.11.10 [ OK ]
13 3.12.10 [ OK ]
14 3.13.2 [ OK ]
15 3.14-rc1 [ OK ]
real 26m54.859s
user 744m15.764s
sys 83m47.440s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
IR_IMG is a new driver added by James via 160a8f8a and letter
integrated into the build via commit 54b29120 as of linux-next
tag next-20140320 which may make it to Linux through v3.15. This
new driver makes use of devm_clk_get() but this was added via
a8a97db9 and that get merged as of v3.5. It seems we can easily
backport a8a97db9 but these days I'm starting to leave this up to the
folks interested in the drivers to choose / participate and only
they would know if this is worth it. Is 3.5 a good starting point
kernel to require for drivers which depend on the new clock APIs?
mcgrof@ergon ~/linux-next (git::master)$ git describe --contains a8a97db9
v3.5-rc1~183^2~2
Cc: James Hogan <james.hogan@imgtec.com>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Mark Brown <broonie@linaro.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
IEEE802154_AT86RF230 has gotten some gpio changes lately
and since we are not backporting all those gpio changes in
practice this driver only compiles down to 3.3 so add that
requirement.
Cc: Alexander Aring <alex.aring@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
NFC_TRF7970A requires devm_gpio_request_one() but since
gpio infrastructure has been strongly shuffled around
we require drivers to use the in-kernel gpio
infrastructure so just bump NFC_TRF7970A to 3.5.
CC: Erick Macias <emacias@ti.com>
CC: Felipe Balbi <balbi@ti.com>
Cc: Mark A. Greer <mgreer@animalcreek.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Commit bcf43393 as of linux-next next-20140320 added this Makefile
header extension:
ccflags-y += -I$(srctree)/drivers/staging/media/rtl2832u_sdr
This ends up calling a staging exported symbol rtl2832_sdr_attach().
Let's not pollute driver code with staging code or dependencies.
Folks, can this be cleaned up? This sets a precedent for doing more
of this, and this can get hairy. Its also not fair for folks who
don't want to carry over any staging code. This forces them to, and
its not just a header file, its a full exported symbol. What about
synchronization with differen trees? Was this addressed with Greg?
commit bcf43393579e3d4069e75a9200a87703185bcf11
Author: Antti Palosaari <crope@iki.fi>
Date: Tue Sep 10 00:13:57 2013 -0300
[media] rtl28xxu: attach SDR extension module
With that extension module it supports SDR.
Signed-off-by: Antti Palosaari <crope@iki.fi>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Antti Palosaari <crope@iki.fi>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
These depend on include/linux/mfd/samsung/s2mps14.h which
other mfd drivers / platform code can depend on, skip
unless we backport all the dependencies which we don't
right now.
The affected drivers are:
* REGULATOR_S2MPS11
* REGULATOR_S2MPA01
* REGULATOR_TPS65217
The mfd files which we don't backport that uses this are:
* drivers/mfd/sec-core.c
* drivers/mfd/sec-irq.c
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Commit 633fc86ff62 added the ieee802154_6lowpan namespace
and 7240cdec60b extended it (as on linux-next next-20140311).
Its important to note though that 633fc86ff62 also extends the
global net namespace. Since we cannot extend the global net
namespace we define our own backport namespace for 6lowpan
that can be used only be used by our backported subsystems,
nothing more. Since ieee802154_6lowpan requires support for
net_get_random_once() which uses static keys and a slew of
new skb fragment support we simply require at least 3.5 to
use 6lowpan. I did my best effort to backport this to kernels
older than 3.5 but quickly ran into a slew of hairy issues.
The last thing we needed to address was usage of the helper
inet_frag_evictor() added by Alexander via commit 6b102865e7
through v3.7. Since we can't backport that with macros or
inline helpers we add a patch to carry the changes there. If
that grows we can consider using Coccinelle.
If you are going to try to backport 6lowpan to kernels older
than 3.5 be warned that the litmus test for patches will be
to pass ckmake --allyesconfig for all supported kernels for
every patch you provide.
Cc: Alexander Aring <alex.aring@gmail.com>
Cc: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Amerigo Wang <amwang@redhat.com>
Cc: linux-zigbee-devel@lists.sourceforge.net
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Drivers that depend on I2C bus segments behind multiplexers to
have a class require quite a bit of collateral changes that I
don't have time to address. For those interested in trying to backport
this see commit eee543e8. This bumps the drivers that depend on this
that we carry to require at least v3.7 when this collateral evolution
was introduced. One driver is affected, rtl2832 -- defined under
CONFIG_DVB_RTL2832.
mcgrof@ergon ~/linux (git::master)$ git describe --contains eee543e82481
v3.7-rc1~92^2~14
commit eee543e8248150e8fb833943c71f40c7b1724600
Author: Jean Delvare <khali@linux-fr.org>
Date: Fri Oct 5 22:23:51 2012 +0200
i2c-mux: Add support for device auto-detection
Let I2C bus segments behind multiplexers have a class. This allows for
device auto-detection on these segments. As long as parent segments
don't share the same class, it should be fine.
I implemented support in drivers i2c-mux-gpio and i2c-mux-pca954x. I
left i2c-mux-pca9541 and i2c-mux-pinctrl alone for the moment as I
don't know if this feature makes sense for the use cases of these
drivers.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Peter Korsgaard <peter.korsgaard@barco.com>
Cc: David Daney <david.daney@cavium.com>
Cc: Michael Lawnick <ml.lawnick@gmx.de>
Cc: Rodolfo Giometti <giometti@linux.it>
Cc: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
There has been quite a bit of updates to the gpio driver library,
and while we can backport some of this it doesn't make much sense
as folks using this driver are expected to be carrying over the
required architecture changes. In particular the GPIO_DEVRES has
been tucked under GPIO_LIB and later removed from depending on it
(see b69ac5244 and 6a89a314a)
mcgrof@ergon ~/linux-next (git::master)$ git describe --contains 6a89a314a
v3.9-rc1~76^2~12^2~13
mcgrof@ergon ~/linux-next (git::master)$ git describe --contains b69ac5244
v3.13-rc1~120^2~7
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The WL1251_SPI driver now depends on EPROBE_DEFER and others which
we canot backports that pushes it to require 3.4 but since it also
relies on devm_gpio_request_one() we bump it to 3.5. The gpio layer
has received quite a bit of updates and it doesn't make sense to
backport them separately.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This driver needs some additional struct members in struct
sec_regulator_data which are not available in a kernel < 3.15
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Add defconfig and necessary files to copy-list.
Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
drivers/bcma/driver_gpio.c calls irq_set_chip_and_handler() when
BCMA_HOST_SOC is activated. irq_set_chip_and_handler() gets exported on
kernel >= 3.7, we should not activate this on any older kernel.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|