Add support for charge pump master and slave power supplies through IIO
devices and properties under them through IIO channels under the device.
Change-Id: I60e4ae948401ce006c731c5cc09334b7aee7ce07
Signed-off-by: Jishnu Prakash <jprakash@codeaurora.org>
Signed-off-by: Ashish Chavan <ashichav@codeaurora.org>
Adding struct definitiond and updating
existing definitions.
Change-Id: I3c894c4a26f7165ca342b5ccb5aa441c7862d094
Acked-by: Eliad Ben Yishay <ebenyish@qti.qualcomm.com>
Signed-off-by: Amir Levy <alevy@codeaurora.org>
Due to SSC (Spread Spectrum) sdcc2 clock wont be 202Mhz but will be
slightly less than 202Mhz (201.99).
For yupik we are using floor ops in clock's driver to take the
floor value for the frequency passed from sdhc driver.
For 201.99Mhz clk_round_rate API will also round to the floor value leading
to 100Mhz for our mclk_freq calculation.
Instead of clk_round_rate and dividing by two logic we can directly
use actual clock which will be supplied to the card in mclk_freq
calculation.
Change-Id: I57a864b98d85573eb9038b6d6f502f83850eed73
Signed-off-by: Sarthak Garg <sartgarg@codeaurora.org>
The MSM SDHCI driver always set the "actual_clock" field to 0. It had
a comment about it not being needed because we weren't using the
standard SDHCI divider mechanism and we'd just fallback to
"host->clock". However, it's still better to provide the actual
clock. Why?
1. It will make timeout calculations slightly better. On one system I
have, the eMMC requets 200 MHz (for HS400-ES) but actually gets 192
MHz. These are close, but why not get the more accurate one.
2. If things are seriously off in the clock driver and it's missing
rates or picking the wrong rate (maybe it's rounding up instead of
down), this will make it much more obvious what's going on.
NOTE: we have to be a little careful here because the "actual_clock"
field shouldn't include the multiplier that sdhci-msm needs
internally.
Change-Id: I16f0ad021209e7a0c2797c695e972888b542246f
Git-Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/
Git-Commit: f16c8fd4449efb4441272af6102e55523b15a7ad
Suggested-by: Adrian Hunter <adrian.hunter@intel.com>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Reviewed-by: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
Signed-off-by: Sarthak Garg <sartgarg@codeaurora.org>
As talked about in commit 5e4b7e82d4 ("clk: qcom: gcc-sdm845: Use
floor ops for sdcc clks"), most clocks handled by the
Qualcomm Technologies, Inc. clock drivers are rounded _up_ by
default instead of down. We should make sure SD/MMC clocks are
always rounded down in the clock drivers.
Let's add a warning in the Qualcomm Technologies, Inc. SDHCI
driver to help catch the problem.
This would have saved a bunch of time [1].
NOTE: this doesn't actually fix any problem, it just makes it obvious
to devs that there is a problem and that should be an indication to
fix the clock driver.
Change-Id: I0d7b15c854eb716383bee54715361d8936b6ad0f
Git-Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/
Git-Commit: a8cd989e1a57dff3994cd113650afb0223c44ec6
Suggested-by: Stephen Boyd <swboyd@chromium.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Signed-off-by: Sarthak Garg <sartgarg@codeaurora.org>
Add support to dump client's GDSC registers when client
passes a regulator(GDSC) handle to clock dump functions.
While at it, increase the GDSC regmap size to include all
GDSC registers.
And for legacy HW, that only supports single GDSCR per GDSC,
'qcom,no-config-gdscr' flag can be specified in GDSC DT node
to decrease the regmap size and map only single GDSCR.
Change-Id: Ia03c647deae9ffe9df93be60abd901bef25c3503
Signed-off-by: Jagadeesh Kona <jkona@codeaurora.org>
Enbale this driver for SoftAP support on sdxlemur.
Change-Id: Ia28c5065223f92c080ce19d45457694bd7a78a20
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
Add new ipc context to log smp2p related logs and put
aggressive logs to appropriate ipc log context to avoid
losing of critical logs.
Change-Id: Ia2a9fb8a9c724e2adc514e618abf9f032ce1ea0a
Signed-off-by: Naman Padhiar <npadhiar@codeaurora.org>
Make change to create and keep memory pool even shmbridge
feature is not supported on certain target, then client can
still suballocte memory from the default bridge.
Change-Id: I134a8d3a31ff6464b25d4c10e1d4c686be2dee12
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
As part of gsi_disable we send zero length packet to the
user space daemons(i.e. QTI/QBI). These daemons when they
receive a ZLP, query for line state to manage the open/close
of their DPM ports. Allow the line state ioctl query irrespective
of gsi connected state.
Change-Id: I4cd50c2b9273ffdeff561dbb1e4cd248cea2139b
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
change the size of vlan_id from uint8_t to uint16_t.
Change-Id: I5fbc35fb49bede3b74b3f6126fd0eab74f50c4d1
Signed-off-by: Rishabh Garg <rishgarg@codeaurora.org>
Add support to dump EPSS registers that aid in debugging
CPUFREQ issues.
Change-Id: Iab15b9debf919b3b3f2dd7428fd0bdff6e04ca41
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Add compatible strings for pmi632 and pm6125 in pinctrl-spmi-gpio
driver to support pmic gpios in 5.4 kernel.
Change-Id: Ic0ccb0e5a8272039dadc29327a2061d2b7cb5213
Signed-off-by: Kavya Nunna <knunna@codeaurora.org>
As snapshot can be recollected and snapshot size can vary on
each recollection if we add snapshot region in minidump during
each recollection then we need to remove it and add it again
to ensure proper snapshot size is captured in minidump. To
avoid this add snapshot region to minidump once and with complete
snapshot memory size. Also, take care of removing it during close
to ensure minidump doesn't try to access already freed memory region.
Change-Id: I5eded015c0544a03eec835da57b6aaf64defc139
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Suppress the log when dcc list on success.
Change-Id: I81de3e360f53e4a2935703c11caf04902b45105b
Signed-off-by: Saurabh Ambulkar <sambulka@codeaurora.org>
With rapid hotplug test case there could be a corner case when the SD card
can go bad and removed quickly even before we try to reset the card as
part of recovery.
This will lead to reset failure with ENOMEDIUM and since recovery failed
so we set the corrupted_card flag and try to remove the card.
Since corrupted_card will be set so as part of rescan we'll remove the
card and return before setting the bus_refs properly leading to card not
getting detected after this.
Only return after setting host->bus_refs properly when card is set as
corrupted.
Change-Id: Id14790f9b28d8fa58d31b034be48db5486ccfcb7
Signed-off-by: Sarthak Garg <sartgarg@codeaurora.org>
Having a global PCI device table share between all PCIe ports
is not necessary. There is potential race conditions if required
locks are present. remove the global PCI device table completely
and utilize the bus list for each PCIe port instead.
Change-Id: I48ebc086fcf56e4b9a9496615e4185c3893ae278
Signed-off-by: Tony Truong <truong@codeaurora.org>
During enumeration, the host can send a clear feature EP_HALT. When
the UDC receives this command, it will cancel any pending requests and
return -ECONNRESET to the function driver. Since the clear EP_HALT
occurs after the cser driver has already submitted the OUT USB reqs,
there is no other method to restart these transfers. Resubmit OUT
reqs specifically when ECONNRESET is seen.
Change-Id: I925170d389048f84579c9b53128effdbef5c9d6a
Signed-off-by: Wesley Cheng <wcheng@codeaurora.org>
If none of the "if" conditions are met, an uninitialized
parb_phase will be used. Initialize parb_phase so that it can
be handled properly.
Change-Id: I682ece7330cd257566ea740c4498bc786ae95588
Signed-off-by: Tony Truong <truong@codeaurora.org>
If a client defines the qcom,iommu-group property, and the iommu group
does not yet exist, of_get_device_group will create a new group with a
refcount of one. The following call to iommu_group_ref_get() increments
the refcount unnecessarily and causes a resource leak.
If a client defines the qcom,iommu-group property, and the iommu group
already exists, modify __bus_lookup_iommu_group() to return with
an additional refcount.
Change-Id: I5c9e62e50737ee4128a591ea2b14a0d47a1be162
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
Fix the compilation issue caused by QCOM_SCM and QCOM_SCM_QCPE
config flags by removing the redundancy of having a separate
qcom_scm-smc_qcpe.c file for adding QCPE support.
Change-Id: Idaa998565464ebeef16990afdc2de2c1a3094a5e
Signed-off-by: katamoni sai abhilash <katamoni@codeaurora.org>
Enable Devfreq monitors, devices, and governors on
sdmsteppeauto target.
Change-Id: I8b206eb3f6efa8e52807352f4edb2f32542c90df
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
Enable core hang detect support on sdmsteppeauto targets.
Change-Id: I992252cda7a5d95cc559fdf3635dec49cca2da7f
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
