Dipen Patel [Fri, 12 Jan 2018 21:27:45 +0000 (13:27 -0800)]
Bluetooth: hci_uart: prevent kernel crash due to race condition
There is a race condition during tty close between
cancel_work_sync and hci_uart_tx_wakeup where
hci_uart_write_work may still be scheduled after call
to cancel_work_sync which causes kernel null reference
crash as hci_uart_tty_close frees the required resources
locking out hci_uart_tty_close, hci_uart_tx_wakeup and
work queue along with new flag HCI_UART_PROTO_READY
will prevent kernel crashes and race condition
Mihir Joshi [Mon, 18 Dec 2017 19:23:13 +0000 (11:23 -0800)]
ote_device: reduce verbosity of TLK print
Due to run time TOS detection support, we need to verify whether TLK
node is enabled in the DT or not before any TOS related operation.
For that, get_tlk_device_node() API is used internally. If TLK node is not
present it outputs an error message in dmesg which has no relevance from
end user's POV.
This change reduces verbosity of that message so that it doesn't spam the
UART if non-TLK TOS is flashed.
Josh Kergan [Wed, 25 Oct 2017 01:31:28 +0000 (18:31 -0700)]
drivers:camera: Update cameras to use common init
All cameras were doing the same setup and cleanup. This common
code was moved to camera_common and now all cameras should behave
the same after probe finishes.
Josh Kergan [Tue, 24 Oct 2017 23:12:54 +0000 (16:12 -0700)]
drivers:camera: Provide common setup/tear-down
Currently most cameras do the same steps during camera setup and
then these should be unset when the driver is unloaded. This change
moves the common setup and tear down into camera common. This helps
make the camera drivers cleaner and make extending functionality
for all sensors easier. It also takes care of sensor properties
stored in the DT so that they are parsed during the sensor
initialization rather than during channel setup.
* Create common setup/tear down function for sensors
* Parse DT for sensor properties during sensor initialization
rather than channel setup.
Josh Kergan [Wed, 25 Oct 2017 01:35:01 +0000 (18:35 -0700)]
drivers:camera: Update fmt to be sensor specific
V4L2 driver was providing all the possible color_fmts supported
by the VI, when it should have been providing only the values used
by that sensor. This fix updates the driver to check the formats
supported by the VI with the formats supported by the sensor as
described in the sensor_properties.
The pod governor used to rely on being invoked from nvgpu on every
gk20_busy/idle() call. This was done originally for load-tracking
purposes. This change refactors the code to instead rely on devfreq's
internal polling loop for calling the governor periodically. It also
removes the idle timeout from the podgov code, since devfreq will keep
polling even when the GPU is idle.
Jira NVGPU-20
Change-Id: I767b74c250d199e3cd5f7e249a49736836a54c0d
Reviewed-on: https://git-master/r/1473145
(cherry picked from commit 6080342d3d911112c9c9486c1bbe0f8e38ea3f57) Signed-off-by: Jon McCaffrey <jmccaffrey@nvidia.com> Signed-off-by: Arun Kannan <akannan@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1639682
GVS: Gerrit_Virtual_Submit Reviewed-by: Peter Boonstoppel <pboonstoppel@nvidia.com> Reviewed-by: Hayden Du <haydend@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
This crash is caused because when the 'rt565x-playback' link is not
defined we will still call rt5659_set_jack_detect() but pass a NULL
pointer for the codec handle. Fix this by ensuring we only call
rt5659_set_jack_detect() when the 'rt565x-playback' link is present.
Change-Id: I33aafe40d8848f27cffaca93f6d1afddee932efb Signed-off-by: Terry Wang <terwang@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1636516 Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit Reviewed-by: Hayden Du <haydend@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Change-Id: Ib451feeb931d32caa5a26750491796b1ac0bd1fc Signed-off-by: Clarence.Zhou <clarencez@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1634382
GVS: Gerrit_Virtual_Submit Reviewed-by: Chun Xu <chunx@nvidia.com> Reviewed-by: Bo Yan <byan@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Josh Kergan [Thu, 26 Oct 2017 21:54:49 +0000 (14:54 -0700)]
drivers:camera: Update default Format for OV5693
The sensor ov5693 reports it's default format as RG10
when it really uses BG10, these formats have the same size
so the driver was working, but we should expose the true format.
Jon Hunter [Mon, 8 Jan 2018 22:09:36 +0000 (22:09 +0000)]
ASoC: tegra-alt: Fix error path for rt565x machine driver
The error path of the Tegra210 rt565x machine driver does not call
tegra_alt_asoc_utils_fini() or unregister the headset switch on
failure.
Failure to call tegra_alt_asoc_utils_fini() may leave clocks enabled
and leak references to clock handles.
Failure to unregister the headset switch on failure prevents causes
subsequent calls to register a switch to fail because one is already
registered. Hence, if the probe of the rt565x machine driver is
deferred, for example because the codec is not register yet, this
will cause subsequent probe attempts to fail because a switch is
already registered.
Fix the above issues by calling tegra_alt_asoc_utils_fini() and
unregistering the switch in the error path of the Tegra210 rt565x
machine driver probe. Finally ensure the switch is unregistered
in the removal of the rt565x machine driver.
Ahung Cheng [Wed, 27 Dec 2017 05:29:55 +0000 (13:29 +0800)]
drivers: camera: support syncpt init in channel init
This is specific for vi2 driver to use fixed syncpt id
Using dynamic syncpt id in vi2 driver can cause a side
effect that vi2 might send unexpected syncpt incremental
to a freed syncpt. This can be observed when HDMI-IN
hotplug happened and then application re-start a capture.
If the syncpt got assigned to another nvhost client,
that unexpected increment will cause syncpt timeout
Ian Chang [Thu, 28 Dec 2017 08:49:12 +0000 (16:49 +0800)]
crypto: increase NEON instruction cipher priority
We found issue when enabling file encryption on T210 platform.
After use NEON instruction the issue disappear.So increase
the NEON instruction priority to 400 on T210 platform as WAR.
Bharat Nihalani [Wed, 27 Dec 2017 04:46:42 +0000 (20:46 -0800)]
Revert "arm64: configs: Enable android for loglevel print"
This reverts commit 080d88aaed36043cd0b88ec8270a1e807a15eaf8
since this causes SQA Automation tests to fail because we
don't see "BOOT_COMPLETE" print with this config enabled.
Takashi Iwai [Wed, 10 Feb 2016 11:47:03 +0000 (12:47 +0100)]
UPSTREAM: ALSA: timer: Call notifier in the same spinlock
snd_timer_notify1() is called outside the spinlock and it retakes the
lock after the unlock. This is rather racy, and it's safer to move
snd_timer_notify() call inside the main spinlock.
The patch also contains a slight refactoring / cleanup of the code.
Now all start/stop/continue/pause look more symmetric and a bit better
readable.
Bug 2019915
Change-Id: Ib90099f88c8b04928a8cdd2808cd9e16da6d519c Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Siqi Lin <siqilin@google.com>
Reviewed-on: https://git-master.nvidia.com/r/1615234 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Takashi Iwai [Fri, 2 Jun 2017 13:03:38 +0000 (15:03 +0200)]
ALSA: timer: Fix race between read and ioctl
The read from ALSA timer device, the function snd_timer_user_tread(),
may access to an uninitialized struct snd_timer_user fields when the
read is concurrently performed while the ioctl like
snd_timer_user_tselect() is invoked. We have already fixed the races
among ioctls via a mutex, but we seem to have forgotten the race
between read vs ioctl.
This patch simply applies (more exactly extends the already applied
range of) tu->ioctl_lock in snd_timer_user_tread() for closing the
race window.
Bug 2019915 Reported-by: Alexander Potapenko <glider@google.com> Tested-by: Alexander Potapenko <glider@google.com> Cc: <stable@vger.kernel.org> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Change-Id: I680a4758ace7eb5fb999fce6abb7070242b6c6da
Reviewed-on: https://git-master.nvidia.com/r/1615233 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Ahung Cheng [Tue, 5 Dec 2017 09:37:44 +0000 (17:37 +0800)]
drivers: camera: fix panic for HDMI-CSI bridge
HDMI-CSI bridge doesn't support override control
and doesn't allocate struct for camera_common_data.
When VI driver is access to override control for HDMI-IN,
it is actually to update the memory of mutex pointer.
Mihir Joshi [Mon, 18 Dec 2017 19:36:30 +0000 (11:36 -0800)]
tlk_driver: check TLK node before tlk_restore_keyslots
Currently, we call tlk_restore_keyslots even if TLK node is not enabled in
DTB.
This patch adds a check to not call the TLK SMC if detected TOS is not TLK
Jon Hunter [Mon, 18 Dec 2017 15:38:26 +0000 (15:38 +0000)]
ASoC: tegra-alt: Fix SW reset for Tegra210 ADMAIF9/10
When using ADMAIF9/10 channels for audio playback/capture on Tegra210,
the soft-reset of the ADMAIF is failing when playback finishes ...
Playing WAVE 'rec.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
[ 260.094969] tegra210-ape-admaif tegra210-admaif: Failed at ADMAIF0_TX sw reset
There are a couple issues here ...
1. The ADMAIF that fails is reported as 'ADMAIF0' although in the above
test ADMAIF9 is being used. This is purely an error in the driver
which is using 'dev-id' as the ADMAIF ID instead of 'dai->id'. Hence
the above error message is misleading.
2. The soft reset fails because the regmap configuration for the ADMAIF
registers on T210 is incorrect. In the function,
tegra210_admaif_volatile_reg(), only the ADMAIF registers between
offset 0x000 and 0x500 are considered volatile. The problem is that
the ADMAIF channel registers for T210 actually span 0x000-0x280 (for
RX) and 0x300-0x580 (for TX). This means that for TX, the ADMAIF9/10
channel registers are not considered volatile and hence, polling the
soft reset register is failing.
Fix the above two issues by correcting the ADMAIF ID reported for any
soft reset failures, and correct the address range for ADMAIF volatile
registers.
David Bang [Mon, 18 Dec 2017 18:31:53 +0000 (13:31 -0500)]
drivers: camera: Fix calibration for CSI2
CSI2 mipi lanes calibration is driven by sensor
state. As soon as the mipi pad is powered on the
sensor is also powered/streamed to reach the standby
state for performing the calibration during the
initialization sequence of CSI2 HW.
Address issues with loadable sensor modules, calibration
will be performed only when the sensor is bound.
David Bang [Mon, 18 Dec 2017 17:54:12 +0000 (12:54 -0500)]
drivers: camera: Fix Mipi Calibration sequence
MIPI calibration can happen irrespective of
sensor state by keeping CSI CIL in reset
state. This change adds calibration to complete
when the CSI is powered ON and based on the sensor
settings. By this approach the mipi lanes are
calibrated and are ready as soon as sensor is
turned ON.
The vendor and product buffers are indeed not nul terminated
(see the CEA-861 spec).
So forcing the last byte to be 0 will cut off the last
character when using full-length vendor (8 chars) or
product (16 chars) names.
Jon Hunter [Fri, 17 Nov 2017 11:17:22 +0000 (11:17 +0000)]
ASoC: tegra-alt: Add support for overriding the bclk ratio
To test internal loopback on any I2S interface using various different
sampling frequencies, it is necessary to be able to override the bit
clock ratio. However, rather than adding a kcontrol for each audio
link supported by the machine driver, add a global kcontrol that when
set will control the bit clock ratio for all I2S links.
Jon Hunter [Mon, 27 Nov 2017 12:11:52 +0000 (12:11 +0000)]
ASoC: tegra-alt: Improve Tegra210 support for testing I2S4
On Tegra210 Jetson TX1, the audio path which defines the I2S4 interface
as the CPU DAI, only supports 2-channel 16-bit audio at 48kHz. This
prevents the user from testing other data formats and rates with this
I2S interface.
For Tegra210 Jetson TX1, the I2S4 interface is used by the DAI link
named 'spdif-dit-0'. Improve support for testing the I2S4 interface by
allowing the sampling rate, data format and number of channels for
'spdif-dit-0' DAI link to be updated.
Jon Hunter [Wed, 6 Dec 2017 11:00:18 +0000 (11:00 +0000)]
soc: tegra: Update DMIC maximum frequency
When attempting to capture audio from DMIC3 on Jetson TX1 after boot
with sampling frequencies of 16kHz or greater the following errors
are seen when enabling the DMIC clock and causes the audio capture
to fail.
tegra-dvfs: rate 12287995 too high for dvfs on dmic3
tegra210-dmic tegra210-dmic.2: clk_enable failed: -22
The problem is that the Tegra210 DVFS driver is limiting the DMIC
frequency to 12.19MHz, although the DMIC supports a maximum frequency
of 12.288MHz (48kHz * 256 over-sampling). The 12.19MHz limit came from
the Tegra210 DVFS frequency spreadsheet that describes the maximum
frequencies for all interfaces/peripherals. This spreadsheet is being
updated to increase the maximum frequency for the DMIC to 12.288MHz.
Therefore, update the Tegra210 DVFS driver to align with this new
maximum frequency for the DMIC interfaces.
Change-Id: I44a49013e67b19ee6ba88c71dbf1f83fcff408bf
Reviewed-on: https://git-master.nvidia.com/r/1612395 Reviewed-by: Mohan Kumar D <mkumard@nvidia.com> Reviewed-by: Jonathan Hunter <jonathanh@nvidia.com> Tested-by: Jonathan Hunter <jonathanh@nvidia.com> Reviewed-by: Peter De Schrijver <pdeschrijver@nvidia.com> Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
GVS: Gerrit_Virtual_Submit Reviewed-by: Timo Alho <talho@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Arvind M [Wed, 29 Nov 2017 06:05:51 +0000 (22:05 -0800)]
tty: serial: 8250: supports loglevel print format
1. Introduces KConfig variable SERIAL_8250_CONSOLE_FORCE_FORMAT default to
value 'n'
2. Modifies the UART8250 output format to include kernel loglevel based on
configuration
Jon Hunter [Mon, 27 Nov 2017 13:07:29 +0000 (13:07 +0000)]
ASoC: tegra-alt: Add 32-bit and TDM support for I2S3 on Tegra210
On Tegra210 Jetson TX1, the audio path which defines the I2S3 interface
as the CPU DAI, only supports 16-bit data formats and 2 channel audio.
This prevents the user from testing other data formats and rates with
this I2S interface..
For Tegra210 Jetson TX1, the I2S3 interface is used by the DAI link
named 'spdif-dit-3'. Improve support for testing the I2S3 interface by
allowing the data format and number of channels for 'spdif-dit-3' DAI
link to be updated.
Vladis Dronov [Wed, 2 Aug 2017 17:50:14 +0000 (19:50 +0200)]
xfrm: policy: check policy direction value
The 'dir' parameter in xfrm_migrate() is a user-controlled byte which is used
as an array index. This can lead to an out-of-bound access, kernel lockup and
DoS. Add a check for the 'dir' value.
This was reported many times, and this was even mentioned in commit 52ee2dfdd4f5 "pids: refactor vnr/nr_ns helpers to make them safe" but
somehow nobody bothered to fix the obvious problem: task_tgid_nr_ns()
is not safe because task->group_leader points to nowhere after the
exiting task passes exit_notify(), rcu_read_lock() can not help.
We really need to change __unhash_process() to nullify group_leader,
parent, and real_parent, but this needs some cleanups. Until then we
can turn task_tgid_nr_ns() into another user of __task_pid_nr_ns() and
fix the problem.
Reported-by: Troy Kensinger <tkensinger@google.com> Signed-off-by: Oleg Nesterov <oleg@redhat.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
(cherry picked from commit dd1c1f2f2028a7b851f701fc6a8ebe39dcb95e7c)
Joseph Lo [Thu, 29 Jun 2017 07:00:47 +0000 (15:00 +0800)]
PM / Domains: fix resume sequence in resume_noirq
Like the 'commit 09b4621f1835 ("PM / Domains: fix redundant
genpd_save_dev call in suspend_noirq")', we should fix the same in
resume_noirq. So the resume sequence will just reverse the sequence in
the suspend_noirq call. This avoids missing "genpd_start_dev" call in
resuem_noirq phase with the drivers using "GENPD_FLAG_PM_UPSTREAM" flag.
And no impacts with other drivers not using "GENPD_FLAG_PM_UPSTREAM"
flag.
Josh Kergan [Fri, 10 Nov 2017 23:16:25 +0000 (15:16 -0800)]
drivers:csi:csi2 error reset fix
The csi port code had changed so that only one port
is allocated to a channel no matter how many physical
ports are used. The csi2 error handler was not updated
for this change and was trying to set 2 ports when only
one existed. Change updates the csi to use the port offset
values to index the second csi to clear the buffer after an
error occurs.
Change-Id: Icf497f3d09d5a1aa05d46391469d7704d906738e Cc: <stable@vger.kernel.org> Signed-off-by: Peter Chang <dpf@google.com> Acked-by: Douglas Gilbert <dgilbert@interlog.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-on: https://git-master.nvidia.com/r/1605270
GVS: Gerrit_Virtual_Submit Reviewed-by: Hayden Du <haydend@nvidia.com> Tested-by: Hayden Du <haydend@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Change-Id: I08d9fecf8ad74735021d4e75bbfe7a018c099396 Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: Andrey Konovalov <andreyknvl@google.com> Tested-by: Andrey Konovalov <andreyknvl@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Reviewed-on: https://git-master.nvidia.com/r/1605253
GVS: Gerrit_Virtual_Submit Reviewed-by: Hayden Du <haydend@nvidia.com> Tested-by: Hayden Du <haydend@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Ninad Malwade [Wed, 22 Nov 2017 03:23:53 +0000 (11:23 +0800)]
arm64: configs: add docker related configs
Adding docker related kernel configs.
Currently dockers are not supported on ARM64 ubuntu version,
but as a requirement we are enabling the required kernel
configs to have out of the box support for the same.
Per as mmc host probe is async, but mmc_rescan of host may be
triggered by bcmdhd driver whose probe is not async. So that
regulators of host etc. may not be initialized. Make bcmdhd
WiFi driver as module.
Jon Hunter [Fri, 10 Nov 2017 16:13:59 +0000 (16:13 +0000)]
ASoC: tegra-alt: Add DAPM Headphone and Mic widgets for I2S3
Tegra I2S3 interface on Jetson TX1 is not working because it is
missing the appropriate DAPM widgets to enable it. Add the
appropriate DAPM widgets for I2S3 (which is using prefix 'l' as
defined by device-tree).
Due to this change, a mode update in X causes mode update on
all TTYs. This is not expected as fbconsole needs to retain its
mode. This also caused dc timeouts upon switching between X and
fbconsole due to inconsistent mode update. Hence, reverting
this change.
Jon Hunter [Wed, 8 Nov 2017 17:39:58 +0000 (17:39 +0000)]
clk: tegra: Fix maximum audio sync clock for Tegra210
The maximum frequency supported for I2S on Tegra210 is 24.576MHz.
However, the maximum I2S frequency is limited to 24MHz because that
is the maximum frequency of the audio sync clock. Increase the
maximum audio sync clock frequency to 24.576MHz for Tegra210 in order
to support 24.576MHz for I2S.
Update the tegra_clk_register_sync_source() function so that it does
not set the initial rate for the sync clocks and use the clock init
tables to set the initial rate instead.
Please note that this is a regression from Linux v3.10.
Naveen Kumar S [Mon, 30 Oct 2017 07:11:46 +0000 (12:41 +0530)]
video: fbmem: update vscreeninfo for all ttys
If Framebuffer Console is active, currently only the foreground TTY's
mode is updated as part of FBIOPUT_VSCREENINFO. This causes issues when
foreground TTY is updated to any other available TTYs, as DC's/FB's mode
might be different. To avoid such inconsistency in mode between ttys and
DC/FB, update mode of all TTYs in FBIO_PUTVSCREENINFO.
Alex Frid [Wed, 26 Apr 2017 06:00:27 +0000 (23:00 -0700)]
thermal: tegra: Make sure DFLL cdev is updated
During suspend DFLL driver always applies cold Vmin to guarantee safe
resume. Therefore DFLL cdev must trigger update to current temperature
after resume even if no thermal threshold is crossed while the SoC was
suspended. To assure this cleared cdev update flag in early resume.
Change-Id: I6caa4e1a183073cfbd7779ac5428a761b3a064ad Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/1470836 Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
GVS: Gerrit_Virtual_Submit Reviewed-by: Peter De Schrijver <pdeschrijver@nvidia.com> Reviewed-by: Jon Mayo <jmayo@nvidia.com>
(cherry picked from commit 2a7d43c9da07ca03dc96419adeb47036d63e1c93)
Alex Frid [Fri, 23 Jun 2017 04:06:20 +0000 (21:06 -0700)]
pwm: tegra: Fix DFLL PWM enable order
Enabled DFLL PWM output before PWM pin is enabled by pin controller
(this was done in opposite order that created a time window of low
PWM output, and the respective drop in PWM regulator voltage).
Change-Id: I56ab12932a904315033f2bf3317a5c10080b9b03 Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/1507650
(cherry picked from commit d5888a2fb38bfa740f7eb48e72ceb3d22818bafd)
Reviewed-on: https://git-master.nvidia.com/r/1526626
GVS: Gerrit_Virtual_Submit Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
(cherry picked from commit 4516851cc0d2a1e9e94fda3e458027f3aabc2332)
Laxman Dewangan [Wed, 17 May 2017 14:50:37 +0000 (20:20 +0530)]
pwm: tegra: Add support to select slower parent
If requested minimum frequency from the platform is not possible
from the higher rate parent then change the parent to slow parent
if slow-parent clock information is provided from DT.
This will help to select the lower frequency of PWM signal.
Laxman Dewangan [Tue, 16 May 2017 18:23:35 +0000 (23:53 +0530)]
pwm: tegra: Add support to lower pwm frequency
The PWM output signal depends on the clock source frequency
and PWM divider for period. There is possibility to have lower
PWM frequency which is not possible with higher PWM clock source
and on this case, it is required to have more fine divider of clock
source to get desired lower side frequency.
Add DT property "pwm-minimum-frequency-hz" to findout the platform
specific requirement and adjust the clock source frequency to
support this lower side frequency.
To configure ramp time through sysfs node there is no
dependency with duty cycle and duty cycle parameter is
not required, so remove duty cycle check while
configuring ramp time through sysfs node.
pwm: tegra: add pwm based pmc soft led blink driver
In T210b01 LED breathing(soft led blink) functionality
added and led breathing control is through PWM signal,
add pwm based driver to configure tegar pmc led breathing
parameters.
Lee Jones [Wed, 12 Apr 2017 15:06:05 +0000 (20:36 +0530)]
pwm: Add PWM capture support
Supply a PWM capture callback op in order to pass back information
obtained by running analysis on a PWM signal. This would normally (at
least during testing) be called from the sysfs routines with a view to
printing out PWM capture data which has been encoded into a string.
Naveen Kumar S [Tue, 10 Oct 2017 08:34:58 +0000 (14:04 +0530)]
video: tegra: description for fbcon mode property
Add description and an example for "nvidia,fbcon-default-mode"
DT property. This property can be used to specify mode parameters
for fbconsole in "struct tegra_dc_mode" format. If specified,
this mode will be used as the default mode for fbconsole.
memory allocated to local variable "req" is not freed before returning
from the function for a possible set of conditions.
Free "req" in such a case to avoid resource leak.
drivers: crypto: Avoid use of tainted scalar value
Copy from user may taint the scalar value members in the respective
struct variables.
Add check for verifying the validity of the scalar value members
to avoid undefined behaviour.
projects / hercules2020 / nv-tegra / linux-4.4.git / log