* [PATCH v3 2/3] Input: atmel_mxt_ts: Wait for device be ready for communication
From: Paweł Chmiel @ 2018-07-31 15:18 UTC (permalink / raw)
To: nick
Cc: dmitry.torokhov, robh+dt, mark.rutland, nicolas.ferre,
alexandre.belloni, linux-input, devicetree, linux-arm-kernel,
linux-kernel, Paweł Chmiel
In-Reply-To: <1533050291-11502-1-git-send-email-pawel.mikolaj.chmiel@gmail.com>
According to documentation, device isn't ready for communication,
until firmware asserts the CHG line. Add missing wait for this.
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
index 2cd7f6db6ba9..79e08916359f 100644
--- a/drivers/input/touchscreen/atmel_mxt_ts.c
+++ b/drivers/input/touchscreen/atmel_mxt_ts.c
@@ -202,6 +202,7 @@ enum t100_type {
#define MXT_CRC_TIMEOUT 1000 /* msec */
#define MXT_FW_RESET_TIME 3000 /* msec */
#define MXT_FW_CHG_TIMEOUT 300 /* msec */
+#define MXT_POWERON_DELAY 150 /* msec */
/* Command to unlock bootloader */
#define MXT_UNLOCK_CMD_MSB 0xaa
@@ -3046,6 +3047,16 @@ static int mxt_regulator_enable(struct mxt_data *data)
msleep(MXT_REGULATOR_DELAY);
gpiod_set_value(data->reset_gpio, 1);
msleep(MXT_RESET_INVALID_CHG);
+
+retry_wait:
+ reinit_completion(&data->bl_completion);
+ data->in_bootloader = true;
+ error = mxt_wait_for_completion(data, &data->bl_completion,
+ MXT_POWERON_DELAY);
+ if (error == -EINTR)
+ goto retry_wait;
+
+ data->in_bootloader = false;
}
return 0;
--
2.7.4
^ permalink raw reply related
* [PATCH v3 3/3] Input: atmel_mxt_ts: Document optional voltage regulators
From: Paweł Chmiel @ 2018-07-31 15:18 UTC (permalink / raw)
To: nick
Cc: dmitry.torokhov, robh+dt, mark.rutland, nicolas.ferre,
alexandre.belloni, linux-input, devicetree, linux-arm-kernel,
linux-kernel, Paweł Chmiel
In-Reply-To: <1533050291-11502-1-git-send-email-pawel.mikolaj.chmiel@gmail.com>
Document new optional voltage regulators, which can be used
to power down/up touchscreen.
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Changes from v1:
- Added reviewed-by
---
Documentation/devicetree/bindings/input/atmel,maxtouch.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt b/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
index c88919480d37..17930ecadad3 100644
--- a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
+++ b/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
@@ -31,6 +31,12 @@ Optional properties for main touchpad device:
- reset-gpios: GPIO specifier for the touchscreen's reset pin (active low)
+- avdd-supply: Analog power supply. It powers up the analog channel block
+ of the controller to detect the touches.
+
+- vdd-supply: Digital power supply. It powers up the digital block
+ of the controller to enable i2c communication.
+
Example:
touch@4b {
@@ -38,4 +44,6 @@ Example:
reg = <0x4b>;
interrupt-parent = <&gpio>;
interrupts = <TEGRA_GPIO(W, 3) IRQ_TYPE_LEVEL_LOW>;
+ avdd-supply = <&atsp_reg>;
+ vdd-supply = <&tsp_reg>;
};
--
2.7.4
^ permalink raw reply related
* [PATCH v2] HID: intel_ish-hid: tx_buf memory leak on probe/remove
From: Anton Vasilyev @ 2018-08-01 11:26 UTC (permalink / raw)
To: Srinivas Pandruvada
Cc: Anton Vasilyev, Jiri Kosina, Benjamin Tissoires, Even Xu,
linux-input, linux-kernel, ldv-project
In-Reply-To: <a43b252b84196087d523c97a162461e6883be1ab.camel@linux.intel.com>
ish_dev_init() allocates 512*176 bytes memory for tx_buf and stores it at
&dev->wr_free_list_head.link list on ish_probe().
But there is no deallocation of this memory in ish_remove() and in
ish_probe() error path.
So current intel-ish-ipc provides 88 KB memory leak for each
probe/release.
The patch replaces kzalloc allocation by devm_kzalloc and removes
ishtp_device *dev deallocation by kfree.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Vasilyev <vasilyev@ispras.ru>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
v2: Fix align for multi line statements
---
drivers/hid/intel-ish-hid/ipc/ipc.c | 9 ++++++---
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 2 --
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/hid/intel-ish-hid/ipc/ipc.c b/drivers/hid/intel-ish-hid/ipc/ipc.c
index 9a60ec13cb10..bfbca7ec54ce 100644
--- a/drivers/hid/intel-ish-hid/ipc/ipc.c
+++ b/drivers/hid/intel-ish-hid/ipc/ipc.c
@@ -907,8 +907,9 @@ struct ishtp_device *ish_dev_init(struct pci_dev *pdev)
struct ishtp_device *dev;
int i;
- dev = kzalloc(sizeof(struct ishtp_device) + sizeof(struct ish_hw),
- GFP_KERNEL);
+ dev = devm_kzalloc(&pdev->dev,
+ sizeof(struct ishtp_device) + sizeof(struct ish_hw),
+ GFP_KERNEL);
if (!dev)
return NULL;
@@ -925,7 +926,9 @@ struct ishtp_device *ish_dev_init(struct pci_dev *pdev)
for (i = 0; i < IPC_TX_FIFO_SIZE; ++i) {
struct wr_msg_ctl_info *tx_buf;
- tx_buf = kzalloc(sizeof(struct wr_msg_ctl_info), GFP_KERNEL);
+ tx_buf = devm_kzalloc(&pdev->dev,
+ sizeof(struct wr_msg_ctl_info),
+ GFP_KERNEL);
if (!tx_buf) {
/*
* IPC buffers may be limited or not available
diff --git a/drivers/hid/intel-ish-hid/ipc/pci-ish.c b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
index a2c53ea3b5ed..81d035a480bc 100644
--- a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
+++ b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
@@ -172,7 +172,6 @@ static int ish_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
free_irq(pdev->irq, dev);
free_device:
pci_iounmap(pdev, hw->mem_addr);
- kfree(dev);
release_regions:
pci_release_regions(pdev);
disable_device:
@@ -202,7 +201,6 @@ static void ish_remove(struct pci_dev *pdev)
pci_release_regions(pdev);
pci_clear_master(pdev);
pci_disable_device(pdev);
- kfree(ishtp_dev);
}
static struct device __maybe_unused *ish_resume_device;
--
2.18.0
^ permalink raw reply related
* Re: [PATCH 1/2] HID: redragon: Fix regression in non-Redragon keyboard due to this new driver
From: John S Gruber @ 2018-08-01 20:46 UTC (permalink / raw)
To: Robert Munteanu
Cc: Jiri Kosina, linux-input, benjamin.tissoires, dmitry.torokhov,
linux-kernel
In-Reply-To: <6330995a9313ade9196cadb2e3696d53d4ef9aa8.camel@apache.org>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
Right, Robert.
I tested it and it works to solve the problem I reported.
On Mon, Jul 30, 2018 at 10:05 AM Robert Munteanu <rombert@apache.org> wrote:
> Hi John,
>
> On Sat, 2018-07-28 at 15:53 -0400, John S Gruber wrote:
> > The Redragon keyboard uses the second device being presented, but
> > other
> > devices with the same vendor_id/device_id pair (0x0c45:760b) use the
> > first.
> > Don't cause its deletion. Problem introduced in commit 85455dd906d5
> > ("HID: redragon: Fix modifier keys for Redragon Asura Keyboard")
> >
> > Fixes: 85455dd906d5
> > Signed-off-by: John S Gruber <JohnSGruber@gmail.com>
> > ---
> > drivers/hid/hid-redragon.c | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/drivers/hid/hid-redragon.c b/drivers/hid/hid-redragon.c
> > index daf5957..85a5fbb 100644
> > --- a/drivers/hid/hid-redragon.c
> > +++ b/drivers/hid/hid-redragon.c
> > @@ -55,10 +55,6 @@ static int redragon_probe(struct hid_device *dev,
> > return ret;
> > }
> >
> > - /* do not register unused input device */
> > - if (dev->maxapplication == 1)
> > - return 0;
> > -
> > ret = hid_hw_start(dev, HID_CONNECT_DEFAULT);
> > if (ret) {
> > hid_err(dev, "hw start failed\n");
>
> As I mentioned, this is already fixed by
> dc9b8e85ed95cbe7e3ad0eabb5b48d617bbc365e, scheduled for 4.19, and I
> suggest that we instead add that one to 4.18.
>
> The explanation is that the block you deleted was the whole reason for
> adding the redragon_probe function, so the changes are largely
> equivalent.
>
> Thanks,
>
> Robert
>
>
[-- Attachment #2: Type: text/html, Size: 2225 bytes --]
^ permalink raw reply
* Re: [PATCH 1/3] Input: elan_i2c_smbus - cast sizeof to int for comparison
From: Dmitry Torokhov @ 2018-08-01 23:03 UTC (permalink / raw)
To: Julia Lawall
Cc: joe, Chengguang Xu, kernel-janitors, linux-input, linux-kernel
In-Reply-To: <1530466325-1678-2-git-send-email-Julia.Lawall@lip6.fr>
On Sun, Jul 01, 2018 at 07:32:03PM +0200, Julia Lawall wrote:
> Comparing an int to a size, which is unsigned, causes the int to become
> unsigned, giving the wrong result. i2c_smbus_read_block_data can return the
> result of i2c_smbus_xfer, whih can return a negative error code.
>
> A simplified version of the semantic match that finds this problem is as
> follows: (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> int x;
> expression e,e1;
> identifier f;
> @@
>
> *x = f(...);
> ... when != x = e1
> when != if (x < 0 || ...) { ... return ...; }
> *x < sizeof(e)
> // </smpl>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
Applied, thank you.
> ---
> drivers/input/mouse/elan_i2c_smbus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/mouse/elan_i2c_smbus.c b/drivers/input/mouse/elan_i2c_smbus.c
> index c060d27..88e315d 100644
> --- a/drivers/input/mouse/elan_i2c_smbus.c
> +++ b/drivers/input/mouse/elan_i2c_smbus.c
> @@ -387,7 +387,7 @@ static int elan_smbus_prepare_fw_update(struct i2c_client *client)
> len = i2c_smbus_read_block_data(client,
> ETP_SMBUS_IAP_PASSWORD_READ,
> val);
> - if (len < sizeof(u16)) {
> + if (len < (int)sizeof(u16)) {
> error = len < 0 ? len : -EIO;
> dev_err(dev, "failed to read iap password: %d\n",
> error);
>
--
Dmitry
^ permalink raw reply
* Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
From: Dmitry Torokhov @ 2018-08-02 1:03 UTC (permalink / raw)
To: Andy Shevchenko
Cc: Andy Shevchenko, Alasdair Kergon, Mike Snitzer,
device-mapper development, Shaohua Li, linux-raid, linux-input,
Andrew Morton, Yury Norov, Linux Kernel Mailing List,
Mika Westerberg, Joe Perches
In-Reply-To: <2310fa540b9e5db3b94f4917ecae76dce2a2ca65.camel@linux.intel.com>
On Tue, Jul 24, 2018 at 02:35:53PM +0300, Andy Shevchenko wrote:
> On Thu, 2018-07-05 at 00:30 +0300, Andy Shevchenko wrote:
> > On Sat, Jun 30, 2018 at 11:17 PM, Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > A lot of code is using allocation of bitmaps using BITS_PER_LONG()
> > > macro and
> > > sizeof(unsigned long) operator. The readability suffers because of
> > > this.
> > >
> > > The series introduces three helpers, i.e. bitmap_alloc(),
> > > bitmap_zalloc() and
> > > bitmap_free(), to make it more cleaner.
> > >
> >
> > Dmitry, it seems we are all set now and if you have no objections
> > against this version, it would be nice to see it in your tree followed
> > by upstream.
>
> Gentle ping!
I put the first 3 patches into an immutable branch off 4.17:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git ib/4.17-bitmap
and queued it and the other 2 patches for the next merge window.
Thanks.
--
Dmitry
^ permalink raw reply
* Re: [PATCH v11 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC
From: Lee Jones @ 2018-08-02 8:35 UTC (permalink / raw)
To: Matti Vaittinen
Cc: robh+dt, mark.rutland, eballetbo, linus.walleij, mazziesaccount,
dmitry.torokhov, linux-clk, devicetree, linux-kernel, sboyd,
broonie, linux-input, mikko.mutanen, heikki.haikola
In-Reply-To: <77184f651e5cefb112f1061bc682b759f88144c6.1532946848.git.matti.vaittinen@fi.rohmeurope.com>
On Mon, 30 Jul 2018, Matti Vaittinen wrote:
> ROHM BD71837 PMIC MFD driver providing interrupts and support
> for three subsystems:
> - clk
> - Regulators
> - input/power-key
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> drivers/mfd/Kconfig | 13 ++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/rohm-bd718x7.c | 208 ++++++++++++++++++++++++
> include/linux/mfd/rohm-bd718x7.h | 332 +++++++++++++++++++++++++++++++++++++++
> 4 files changed, 554 insertions(+)
> create mode 100644 drivers/mfd/rohm-bd718x7.c
> create mode 100644 include/linux/mfd/rohm-bd718x7.h
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
^ permalink raw reply
* Re: [PATCH v2] HID: intel-ish-hid: Prevent loading of driver on Mehlow
From: Jiri Kosina @ 2018-08-02 11:27 UTC (permalink / raw)
To: Srinivas Pandruvada; +Cc: benjamin.tissoires, linux-input, linux-kernel
In-Reply-To: <20180718193200.17944-1-srinivas.pandruvada@linux.intel.com>
On Wed, 18 Jul 2018, Srinivas Pandruvada wrote:
> On Mehlow Xeon-E workstation, ISH PCI device is enabled but without ISH
> firmware. Here the ISH device PCI device id was reused for some non Linux
> storage drivers. So this was not done for enabling ISH. But this has a
> undesirable side effect for Linux.
>
> Here the ISH driver will be loaded via PCI enumeration and will try to do
> reset sequence. But reset sequence will wait till timeout as there is no
> real ISH firmware is present to take action. This delay will add to boot
> time of Linux (This platform will still continue to boot after this
> timeout).
>
> To avoid this boot delay we need to prevent loading of ISH drivers on
> this platform. So we need to have hack to avoid treating this device as
> ISH on this platform. To identify this workstation, we need some runtime
> method. Luckily there are special PCI id on this workstation to
> distinguish from the client version of this platform. On client version,
> the ISH is supported using same PCI device id. So this change look for
> the presence of PCI device IDs A309 and A30A and exit.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> v2
> Replaced pci_get_device with pci_dev_present to check in a loop as
> suggested by Benjamin.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
^ permalink raw reply
* Re: [PATCH v2] HID: intel_ish-hid: tx_buf memory leak on probe/remove
From: Jiri Kosina @ 2018-08-02 11:28 UTC (permalink / raw)
To: Anton Vasilyev
Cc: Srinivas Pandruvada, Benjamin Tissoires, Even Xu, linux-input,
linux-kernel, ldv-project
In-Reply-To: <20180801112651.6032-1-vasilyev@ispras.ru>
On Wed, 1 Aug 2018, Anton Vasilyev wrote:
> ish_dev_init() allocates 512*176 bytes memory for tx_buf and stores it at
> &dev->wr_free_list_head.link list on ish_probe().
> But there is no deallocation of this memory in ish_remove() and in
> ish_probe() error path.
> So current intel-ish-ipc provides 88 KB memory leak for each
> probe/release.
>
> The patch replaces kzalloc allocation by devm_kzalloc and removes
> ishtp_device *dev deallocation by kfree.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Anton Vasilyev <vasilyev@ispras.ru>
> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> v2: Fix align for multi line statements
Applied, thanks.
--
Jiri Kosina
SUSE Labs
^ permalink raw reply
* Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
From: Andy Shevchenko @ 2018-08-02 12:07 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: Andy Shevchenko, Alasdair Kergon, Mike Snitzer,
device-mapper development, Shaohua Li, linux-raid, linux-input,
Andrew Morton, Yury Norov, Linux Kernel Mailing List,
Mika Westerberg, Joe Perches
In-Reply-To: <20180802010325.GB184797@dtor-ws>
On Wed, 2018-08-01 at 18:03 -0700, Dmitry Torokhov wrote:
> I put the first 3 patches into an immutable branch off 4.17:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git ib/4.17-
> bitmap
Thank you!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
^ permalink raw reply
* Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.
From: Marek Szyprowski @ 2018-08-03 7:26 UTC (permalink / raw)
To: Ravi Chandra Sadineni, ravisadineni, dmitry.torokhov, dtor
Cc: tbroch, linux-kernel, linux-input, 'Linux Samsung SOC'
In-Reply-To: <20180605224458.62692-1-ravisadineni@chromium.org>
Hi All,
On 2018-06-06 00:44, Ravi Chandra Sadineni wrote:
> Remove the unnecessary check before calling pm_wakeup_event. If the
> device is not wake enabled, this call is no-op anyway.
>
> Signed-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org>
This patch breaks suspend/resume on Samsung Exynos5250 Snow Chromebook.
It looks that it is waiting forever(?) on some cros ec i2c call. With
no_console_suspend and initcall_debug kernel parameters together with
playing with magic-sysrq after suspend/resume cycle I've managed to get
following log:
# rtcwake -s10 -mmem
rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Aug 3 06:13:42 2018
[ 38.359219] PM: suspend entry (deep)
[ 38.362782] PM: Syncing filesystems ... done.
[ 38.379897] Freezing user space processes ... (elapsed 0.002 seconds)
done.
[ 38.382258] OOM killer disabled.
[ 38.382263] Freezing remaining freezable tasks ... (elapsed 0.001
seconds) done.
[ 38.388705] calling input2+ @ 1610, parent: gpio-keys
[ 38.388847] call input2+ returned 0 after 122 usecs
[ 38.388985] calling sound+ @ 1610, parent: platform
[ 38.423739] max98095 7-0011: ASoC: PRE_PMD: LINE Left Out event
failed: -22
[ 38.435718] call sound+ returned 0 after 45628 usecs
[ 38.435746] calling panel+ @ 1610, parent: platform
[ 38.435754] call panel+ returned 0 after 1 usecs
[ 38.435768] calling hdmi-audio-codec.4.auto+ @ 1610, parent:
14530000.hdmi
[ 38.435775] call hdmi-audio-codec.4.auto+ returned 0 after 1 usecs
[ 38.435799] calling backlight+ @ 1610, parent: backlight
[ 38.436032] call backlight+ returned 0 after 221 usecs
[ 38.436048] calling backlight+ @ 1610, parent: platform
[ 38.445536] call backlight+ returned 0 after 9257 usecs
[ 38.445670] calling mmc2:0001:3+ @ 6, parent: mmc2:0001
[ 38.445700] call mmc2:0001:3+ returned 0 after 1 usecs
[ 38.445733] calling mmc2:0001:2+ @ 6, parent: mmc2:0001
[ 38.445740] call mmc2:0001:2+ returned 0 after 1 usecs
[ 38.445760] calling mmc2:0001:1+ @ 6, parent: mmc2:0001
[ 38.445767] call mmc2:0001:1+ returned 0 after 1 usecs
[ 38.445792] calling mmc2:0001+ @ 6, parent: mmc2
[ 38.445884] calling snd-soc-dummy+ @ 1610, parent: platform
[ 38.445892] call snd-soc-dummy+ returned 0 after 1 usecs
[ 38.445988] calling cpufreq-dt+ @ 1610, parent: platform
[ 38.445997] call cpufreq-dt+ returned 0 after 1 usecs
[ 38.446071] calling tps65090-charger+ @ 1610, parent: 104-0048
[ 38.446079] call tps65090-charger+ returned 0 after 1 usecs
[ 38.446208] calling mmc1:e624+ @ 78, parent: mmc1
[ 38.446212] calling tps65090-pmic+ @ 1610, parent: 104-0048
[ 38.446220] call tps65090-pmic+ returned 0 after 1 usecs
[ 38.446279] calling input1+ @ 1610, parent:
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller
[ 38.446289] call input1+ returned 0 after 3 usecs
[ 38.446305] calling
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+ @ 1610,
parent: 104-001e
[ 38.446313] call
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+
returned 0 after 1 usecs
[ 38.446327] calling cros-ec-dev.3.auto+ @ 1610, parent: 104-001e
[ 38.446334] call cros-ec-dev.3.auto+ returned 0 after 1 usecs
[ 38.446370] calling 104-001e+ @ 1610, parent: i2c-104
[ 38.448555] call mmc1:e624+ returned 0 after 2283 usecs
[ 38.450514] calling mmc0:0001+ @ 79, parent: mmc0
[ 38.457501] call mmc2:0001+ returned 0 after 11425 usecs
[ 38.463830] wake enabled for irq 150
[ 38.469426] calling 1-1+ @ 6, parent: usb1
[ 38.474501] call 104-001e+ returned 0 after 27461 usecs
[ 38.490008] call 1-1+ returned 0 after 10331 usecs
[ 38.494988] calling 104-000b+ @ 1610, parent: i2c-104
[ 38.512028] call mmc0:0001+ returned 0 after 36926 usecs
[ 38.547373] call 104-000b+ returned 0 after 51146 usecs
[ 38.670382] calling rtc1+ @ 1610, parent: 101e0000.rtc
[ 38.675688] call rtc1+ returned 0 after 2 usecs
[ 38.680296] calling rtc0+ @ 1610, parent: max77686-rtc
[ 38.717626] call rtc0+ returned 0 after 31302 usecs
[ 38.722578] calling input0+ @ 1610, parent: 1-0067
[ 38.727536] call input0+ returned 0 after 3 usecs
[ 38.732368] calling usb4+ @ 78, parent: xhci-hcd.2.auto
[ 38.732790] calling usb2+ @ 1614, parent: 12120000.usb
[ 38.738659] calling usb1+ @ 79, parent: 12110000.usb
[ 38.743044] calling usb3+ @ 6, parent: xhci-hcd.2.auto
[ 38.748311] call usb4+ returned 0 after 10186 usecs
[ 38.753567] call usb3+ returned 0 after 251 usecs
[ 38.758811] call usb1+ returned 0 after 526 usecs
[ 38.763006] calling xhci-hcd.2.auto+ @ 6, parent: 12000000.dwc3
[ 38.773625] call xhci-hcd.2.auto+ returned 0 after 43 usecs
[ 38.779206] calling 12000000.dwc3+ @ 1610, parent: soc:usb_dwc3
[ 38.785417] call 12000000.dwc3+ returned 0 after 245 usecs
[ 38.790917] calling usb_phy_generic.1.auto+ @ 1610, parent: platform
[ 38.797356] call usb_phy_generic.1.auto+ returned 0 after 1 usecs
[ 38.803431] calling usb_phy_generic.0.auto+ @ 1610, parent: platform
[ 38.809966] call usb_phy_generic.0.auto+ returned 0 after 1 usecs
[ 38.816108] calling Fixed MDIO bus.0+ @ 1610, parent: platform
[ 38.822083] call Fixed MDIO bus.0+ returned 0 after 1 usecs
[ 38.827738] calling max77686-clk+ @ 1610, parent: 0-0009
[ 38.833159] call max77686-clk+ returned 0 after 1 usecs
[ 38.838478] calling max77686-rtc+ @ 1610, parent: 0-0009
[ 38.844475] wake enabled for irq 146
[ 38.848184] call max77686-rtc+ returned 0 after 4181 usecs
[ 38.853999] calling max77686-pmic+ @ 1610, parent: 0-0009
[ 38.859554] call max77686-pmic+ returned 0 after 1 usecs
[ 38.865284] calling exynos-drm+ @ 1610, parent: platform
[ 38.871024] call usb2+ returned 0 after 114877 usecs
[ 38.890105] call exynos-drm+ returned 0 after 13780 usecs
[ 38.894146] calling serial8250+ @ 1610, parent: platform
[ 38.899515] call serial8250+ returned 0 after 2 usecs
[ 38.908551] calling alarmtimer+ @ 1610, parent: platform
[ 38.913057] call alarmtimer+ returned 0 after 536 usecs
[ 38.917812] calling regulatory.0+ @ 1610, parent: platform
[ #8.923263] call regulatory.0+ returned 0 after 1 usecs
[ 38.929144] calling 1-0067+ @ 1610, parent: i2c-1
[ 38.967236] wake enabled for irq 148
[ 38.969454] call 1-0067+ returned 0 after 35363 usecs
[ 38.974510] calling 0-0009+ @ 1610, parent: i2c-0
[ 38.979274] call 0-0009+ returned 0 after 5 usecs
[ 38.983989] calling mmc3_pwrseq+ @ 1610, parent: platform
[ 38.989422] call mmc3_pwrseq+ returned 0 after 1 usecs
[ 38.994522] calling regulator-usb3+ @ 1610, parent: platform
[ 39.000271] call regulator-usb3+ returned 0 after 1 usecs
[ 39.005633] calling i2c-arbitrator+ @ 1610, parent: platform
[ 39.011381] call i2c-arbitrator+ returned 0 after 1 usecs
[ 39.016744] calling vbat-fixed-regulator+ @ 1610, parent: platform
[ 39.023015] call vbat-fixed-regulator+ returned 0 after 1 usecs
[ 39.028925] calling gpio-keys+ @ 1610, parent: platform
[ 39.034182] wake enabled for irq 152
[ 39.037759] wake enabled for irq 153
[ 39.041292] call gpio-keys+ returned 0 after 6944 usecs
[ 39.046515] calling opp_table0+ @ 1610, parent: platform
[ 39.051915] call opp_table0+ returned 0 after 1 usecs
[ 39.056940] calling 14650000.sysmmu+ @ 1610, parent: soc
[ 39.062332] call 14650000.sysmmu+ returned 0 after 2 usecs
[ 39.067818] calling 14640000.sysmmu+ @ 1610, parent: soc
[ 39.073332] call 14640000.sysmmu+ returned 0 after 174 usecs
[ 39.078845] calling 13eb0000.sysmmu+ @ 1610, parent: soc
[ 39.084180] call 13eb0000.sysmmu+ returned 0 after 2 usecs
[ 39.089690] calling 13ea0000.sysmmu+ @ 1610, parent: soc
[ 39.095029] call 13ea0000.sysmmu+ returned 0 after 2 usecs
[ 39.100547] calling 13e90000.sysmmu+ @ 1610, parent: soc
[ 39.105880] call 13e90000.sysmmu+ returned 0 after 2 usecs
[ 39.111402] calling 13e80000.sysmmu+ @ 1610, parent: soc
[ 39.116731] call 13e80000.sysmmu+ returned 0 after 2 usecs
[ 39.122241] calling 13c50000.sysmmu+ @ 1610, parent: soc
[ 39.127607] call 13c50000.sysmmu+ returned 0 after 2 usecs
[ 39.133065] calling 13c40000.sysmmu+ @ 1610, parent: soc
[ 39.138498] call 13c40000.sysmmu+ returned 0 after 2 usecs
[ 39.143915] calling 132f0000.sysmmu+ @ 1610, parent: soc
[ 39.149308] call 132f0000.sysmmu+ returned 0 after 2 usecs
[ 39.154765] calling 132e0000.sysmmu+ @ 1610, parent: soc
[ 39.160155] call 132e0000.sysmmu+ returned 0 after 2 usecs
[ 39.165615] calling 132d0000.sysmmu+ @ 1610, parent: soc
[ 39.171005] call 132d0000.sysmmu+ returned 0 after 2 usecs
[ 39.176465] calling 132c0000.sysmmu+ @ 1610, parent: soc
[ 39.181856] call 132c0000.sysmmu+ returned 0 after 2 usecs
[ 39.187340] calling 132b0000.sysmmu+ @ 1610, parent: soc
[ 39.192680] call 132b0000.sysmmu+ returned 0 after 2 usecs
[ 39.198190] calling 13290000.sysmmu+ @ 1610, parent: soc
[ 39.203530] call 13290000.sysmmu+ returned 0 after 2 usecs
[ 39.209091] calling 13280000.sysmmu+ @ 1610, parent: soc
[ 39.214380] call 13280000.sysmmu+ returned 0 after 2 usecs
[ 39.219892] calling 132a0000.sysmmu+ @ 1610, parent: soc
[ 39.225230] call 132a0000.sysmmu+ returned 0 after 2 usecs
[ 39.230749] calling 13270000.sysmmu+ @ 1610, parent: soc
[ 39.236080] call 13270000.sysmmu+ returned 0 after 2 usecs
[ 39.241590] calling 13260000.sysmmu+ @ 1610, parent: soc
[ 39.246931] call 13260000.sysmmu+ returned 0 after 2 usecs
[ 39.252440] calling 11f20000.sysmmu+ @ 1610, parent: soc
[ 39.257806] call 11f20000.sysmmu+ returned 0 after 2 usecs
[ 39.263265] calling 11d40000.sysmmu+ @ 1610, parent: soc
[ 39.268655] call 11d40000.sysmmu+ returned 0 after 2 usecs
[ 39.274115] calling 11210000.sysmmu+ @ 1610, parent: soc
[ 39.279505] call 11210000.sysmmu+ returned 0 after 2 usecs
[ 39.284965] calling 11200000.sysmmu+ @ 1610, parent: soc
[ 39.290355] call 11200000.sysmmu+ returned 0 after 2 usecs
[ 39.295815] calling 10a60000.sysmmu+ @ 1610, parent: soc
[ 39.301206] call 10a60000.sysmmu+ returned 0 after 2 usecs
[ 39.306657] calling soc:video-phy+ @ 1610, parent: soc
[ 39.311881] call soc:video-phy+ returned 0 after 2 usecs
[ 39.317158] calling 101b0000.cec+ @ 1610, parent: soc
[ 39.322296] call 101b0000.cec+ returned 0 after 1 usecs
[ 39.327511] calling 13e30000.gsc+ @ 1610, parent: soc
[ 39.332600] call 13e30000.gsc+ returned 0 after 1 usecs
[ 39.337841] calling 13e20000.gsc+ @ 1610, parent: soc
[ 39.342929] call 13e20000.gsc+ returned 0 after 1 usecs
[ 39.348208] calling 13e10000.gsc+ @ 1610, parent: soc
[ 39.353258] call 13e10000.gsc+ returned 0 after 1 usecs
[ 39.358506] calling 13e00000.gsc+ @ 1610, parent: soc
[ 39.363588] call 13e00000.gsc+ returned 0 after 1 usecs
[ 39.368835] calling 11c10000.mdma+ @ 1610, parent: soc:amba
[ 39.374443] call 11c10000.mdma+ returned 0 after 5 usecs
[ 39.379772] calling 10800000.mdma+ @ 1610, parent: soc:amba
[ 39.385379] call 10800000.mdma+ returned 0 after 5 usecs
[ 39.390726] calling 121b0000.pdma+ @ 1610, parent: soc:amba
[ 39.396316] call 121b0000.pdma+ returned 0 after 5 usecs
[ 39.401663] calling 121a0000.pdma+ @ 1610, parent: soc:amba
[ 39.407280] call 121a0000.pdma+ returned 0 after 4 usecs
[ 39.412554] calling soc:amba+ @ 1610, parent: soc
[ 39.417340] call soc:amba+ returned 0 after 1 usecs
[ 39.422186] calling 12130000.phy+ @ 1610, parent: soc
[ 39.427323] call 12130000.phy+ returned 0 after 1 usecs
[ 39.432517] calling 12120000.usb+ @ 1610, parent: soc
[ 39.437820] call 12120000.usb+ returned 0 after 165 usecs
[ 39.443020] calling 12110000.usb+ @ 1610, parent: soc
[ 39.448434] call 12110000.usb+ returned 0 after 270 usecs
[ 39.453523] calling 12100000.phy+ @ 1610, parent: soc
[ 39.458662] call 12100000.phy+ returned 0 after 1 usecs
[ 39.463850] calling soc:usb_dwc3+ @ 1610, parent: soc
[ 39.468994] call soc:usb_dwc3+ returned 0 after 7 usecs
[ 39.474179] calling 3830000.i2s+ @ 1610, parent: soc
[ 39.479232] call 3830000.i2s+ returned 0 after 2 usecs
[ 39.484337] calling 12230000.mmc+ @ 1610, parent: soc
[ 39.489497] call 12230000.mmc+ returned 0 after 17 usecs
[ 39.494753] calling 12220000.mmc+ @ 1610, parent: soc
[ 39.499900] call 12220000.mmc+ returned 0 after 11 usecs
[ 39.505169] calling 12200000.mmc+ @ 1610, parent: soc
[ 39.510321] call 12200000.mmc+ returned 0 after 16 usecs
[ 39.515583] calling 12d30000.spi+ @ 1610, parent: soc
[ 39.520864] call 12d30000.spi+ returned 0 after 140 usecs
[ 39.526086] calling 12ce0000.i2c+ @ 1610, parent: soc
[ 39.531225] call 12ce0000.i2c+ returned 0 after 1 usecs
[ 39.536415] calling 12cd0000.i2c+ @ 1610, parent: soc
[ 39.541552] call 12cd0000.i2c+ returned 0 after 1 usecs
[ 39.546744] calling 12cb0000.i2c+ @ 1610, parent: soc
[ 39.551881] call 12cb0000.i2c+ returned 0 after 1 usecs
[ 39.557073] calling 12ca0000.i2c+ @ 1610, parent: soc
[ 39.562253] call 12ca0000.i2c+ returned 0 after 1 usecs
[ 39.567427] calling 10060000.tmu+ @ 1610, parent: soc
[ 39.572696] call 10060000.tmu+ returned 0 after 178 usecs
[ 39.577932] calling 11c00000.rotator+ @ 1610, parent: soc
[ 39.583366] call 11c00000.rotator+ returned 0 after 1 usecs
[ 39.588955] calling 11000000.codec+ @ 1610, parent: soc
[ 39.594216] call 11000000.codec+ returned 0 after 1 usecs
[ 39.599632] calling 101d0000.watchdog+ @ 1610, parent: soc
[ 39.605415] call 101d0000.watchdog+ returned 0 after 256 usecs
[ 39.611005] calling 10040000.system-controller+ @ 1610, parent: soc
[ 39.617342] call 10040000.system-controller+ returned 0 after 1 usecs
[ 39.623806] calling 10d10000.pinctrl+ @ 1610, parent: soc
[ 39.629223] call 10d10000.pinctrl+ returned 0 after 1 usecs
[ 39.634845] calling 13400000.pinctrl+ @ 1610, parent: soc
[ 39.640247] call 13400000.pinctrl+ returned 0 after 1 usecs
[ 39.646009] calling 11400000.pinctrl+ @ 1610, parent: soc
[ 39.651271] call 11400000.pinctrl+ returned 0 after 1 usecs
[ 39.656807] calling soc:pmu+ @ 1610, parent: soc
[ 39.661509] call soc:pmu+ returned 0 after 2 usecs
[ 39.666265] calling 101c0000.mct+ @ 1610, parent: soc
[ 39.671405] call 101c0000.mct+ returned 0 after 1 usecs
[ 39.676596] calling soc:timer+ @ 1610, parent: soc
[ 39.681473] call soc:timer+ returned 0 after 1 usecs
[ 39.686423] calling 10010000.clock-controller+ @ 1610, parent: soc
[ 39.692676] call 10010000.clock-controller+ returned 0 after 1 usecs
[ 39.699021] calling 100440c0.power-domain+ @ 1610, parent: Soc
[ 39.704888] call 100440c0.power-domain+ returned 0 after 1 usecs
[ 39.710911] calling 100440a0.power-domain+ @ 1610, parent: soc
[ 39.716780] call 100440a0.power-domain+ returned 0 after 1 usecs
[ 39.722802] calling 10044060.power-domain+ @ 1610, parent: soc
[ 39.728697] call 10044060.power-domain+ returned 0 after 1 usecs
[ 39.734669] calling 10044040.power-domain+ @ 1610, parent: soc
[ 39.740589] call 10044040.power-domain+ returned 0 after 1 usecs
[ 39.746560] calling 10044000.power-domain+ @ 1610, parent: soc
[ 39.752486] call 10044000.power-domain+ returned 0 after 1 usecs
[ 39.758477] calling 2020000.sysram+ @ 1610, parent: soc
[ 39.763736] call 2020000.sysram+ returned 0 after 2 usecs
[ 39.769191] calling 10850000.g2d+ @ 1610, parent: soc
[ 39.774238] call 10850000.g2d+ returned 0 after 1 usecs
[ 39.779480] calling 10830600.rng+ @ 1610, parent: soc
[ 39.784568] call 10830600.rng+ returned 0 after 3 usecs
[ 39.789808] calling 10830400.rng+ @ 1610, parent: soc
[ 39.794897] call 10830400.rng+ returned 0 after 3 usecs
[ 39.800137] calling 10830000.sss+ @ 1610, parent: soc
[ 39.805226] call 10830000.sss+ returned 0 after 2 usecs
[ 39.810468] calling 101e0000.rtc+ @ 1610, parent: soc
[ 39.815639] call 101e0000.rtc+ returned 0 after 84 usecs
[ 39.820886] calling 12dd0000.pwm+ @ 1610, parent: soc
[ 39.825972] call 12dd0000.pwm+ returned 0 after 3 usecs
[ 39.831211] calling 12c90000.i2c+ @ 1610, parent: soc
[ 39.836300] call 12c90000.i2c+ returned 0 after 1 usecs
[ 39.841542] calling 12c80000.i2c+ @ 1610, parent: soc
[ 39.846629] call 12c80000.i2c+ returned 0 after 1 usecs
[ 39.851871] calling 12c70000.i2c+ @ 1610, parent: soc
[ 39.856958] call 12c70000.i2c+ returned 0 after 1 usecs
[ 39.862200] calling 12c60000.i2c+ @ 1610, parent: soc
[ 39.867313] call 12c60000.i2c+ returned 0 after 1 usecs
[ 39.872505] calling 12c30000.serial+ @ 1610, parent: soc
[ 39.878121] call 12c30000.serial+ returned 0 after 209 usecs
[ 39.883531] calling 12c20000.serial+ @ 1610, parent: soc
[ 39.888936] call 12c20000.serial+ returned 0 after 6 usecs
[ 39.894379] calling 12c10000.serial+ @ 1610, parent: soc
[ 39.899782] call 12c10000.serial+ returned 0 after 5 usecs
[ 39.905229] calling 12c00000.serial+ @ 1610, parent: soc
[ 39.910631] call 12c00000.serial+ returned 0 after 6 usecs
[ 39.916078] calling 10050000.syscon+ @ 1610, parent: soc
[ 39.921478] call 10050000.syscon+ returned 0 after 1 usecs
[ 39.926929] calling 12250000.memory-controller+ @ 1610, parent: soc
[ 39.933289] call 12250000.memory-controller+ returned 0 after 4 usecs
[ 39.939717] calling 10000000.chipid+ @ 1610, parent: soc
[ 39.945062] call 10000000.chipid+ returned 0 after 1 usecs
[ 39.950564] calling soc:syscon-reboot+ @ 1610, parent: soc
[ 39.956086] call soc:syscon-reboot+ returned 0 after 1 usecs
[ 39.961761] calling soc:syscon-poweroff+ @ 1610, parent: soc
[ 39.967484] call soc:syscon-poweroff+ returned 0 after 2 usecs
[ 39.973344] calling soc+ @ 1610, parent: platform
[ 39.978108] call soc+ returned 0 after 1 usecs
[ 39.982477] calling exynos_cpuidle+ @ 1610, parent: platform
[ 39.988230] call exynos_cpuidle+ returned 0 after 1 usecs
[ 39.993609] calling reg-dummy+ @ 1610, parent: platform
[ 39.998903] call reg-dummy+ returned 0 after 1 usecs
[ 40.005000] calling regulator.49+ @ 1610, parent: 104-0048
[ 40.014319] call regulator.49+ returned 0 after 4783 usecs
[ 40.018399] calling regulator.48+ @ 1610, parent: 104-0048
[ 40.026464] call regulator.48+ returned 0 after 2491 usecs
[ 40.030537] calling regulator.47+ @ 1610, parent: 104-0048
[ 40.038619] call regulator.47+ returned 0 after 2503 usecs
[ 40.042668] calling regulator.46+ @ 1610, parent: 104-0048
[ 40.050792] call regulator.46+ returned 0 after 2484 usecs
[ 40.054836] calling regulator.45+ @ 1610, parent: 104-0048
[ 40.062966] call regulator.45+ returned 0 after 2488 usecs
[ 40.067007] calling regulator.44+ @ 1610, parent: 104-0048
[ 40.075128] call regulator.44+ returned 0 after 2482 usecs
[ 40.079207] calling regulator.43+ @ 1610, parent: 104-0048
[ 40.087293] call regulator.43+ returned 0 after 2508 usecs
[ 40.091337] calling regulator.42+ @ 1610, parent: 104-0048
[ 40.099447] call regulator.42+ returned 0 after 2502 usecs
[ 40.103488M calling regulator.41+ @ 1610, parent: 104-0048
[ 40.111609] call regulator.41+ returned 0 after 2481 usecs
[ 40.115658] calling regulator.40+ @ 1610, parent: 104-0048
[ 40.123782] call regulator.40+ returned 0 after 2484 usecs
[ 40.127859] calling regulator.39+ @ 1610, parent: 104-0048
[ 40.135918] call regulator.39+ returned 0 after 2482 usecs
[ 40.139993] calling regulator.38+ @ 1610, parent: 104-0048
[ 40.148053] call regulator.38+ returned 0 after 2482 usecs
[ 40.153493] calling regulator.37+ @ 1610, parent: 0-0009
[ 40.160058] call regulator.37+ returned 0 after 2493 usecs
[ 40.164100] calling regulator.36+ @ 1610, parent: 0-0009
[ 40.172105] call regulator.36+ returned 0 after 2485 usecs
[ 40.176148] calling regulator.35+ @ 1610, parent: 0-0009
[ 40.184097] call regulator.35+ returned 0 after 2481 usecs
[ 40.188215] calling regulator.34+ @ 1610, parent: 0-0009
[ 40.196063] call regulator.34+ returned 0 after 2484 usecs
[ 40.200137] calling regulator.33+ @ 1610, parent: 0-0009
[ 40.208023] call regulator.33+ returned 0 after 2482 usecs
[ 40.212067] calling regulator.32+ @ 1610, parent: 0-0009
[ 40.220014] call regulator.32+ returned 0 after 2482 usecs
[ 40.224062] calling regulator.31+ @ 1610, parent: 0-0009
[ 40.232011] call regulator.31+ returned 0 after 2484 usecs
[ 40.236057] calling regulator.30+ @ 1610, parent: 0-0009
[ 40.244006] call regulator.30+ returned 0 after 2481 usecs
[ 40.248085] calling regulator.29+ @ 1610, parent: 0-0009
[ 40.255969] call regulator.29+ returned 0 after 2480 usecs
[ 40.260047] calling regulator.28+ @ 1610, parent: 0-0009
[ 40.267963] call regulator.28+ returned 0 after 2513 usecs
[ 40.272010] calling regulator.27+ @ 1610, parent: 0-0009
[ 40.279962] call regulator.27+ returned 0 after 2484 usecs
[ 40.284006] calling regulator.26+ @ 1610, parent: 0-0009
[ 40.291953] call regulator.26+ returned 0 after 2480 usecs
[ 40.295993] calling regulator.25+ @ 1610, parent: 0-0009
[ 40.303941] call regulator.25+ returned 0 after 2482 usecs
[ 40.308021] calling regulator.24+ @ 1610, parent: 0-0009
[ 40.315905] call regulator.24+ returned 0 after 2481 usecs
[ 40.319982] calling regulator.23+ @ 1610, parent: 0-0009
[ 40.327863] call regulator.23+ returned 0 after 2478 usecs
[ 40.331912] calling regulator.22+ @ 1610, parent: 0-0009
[ 40.339858] call regulator.22+ returned 0 after 2482 usecs
[ 40.343898] calling regulator.21+ @ 1610, parent: 0-0009
[ 40.351846] call regulator.21+ returned 0 after 2481 usecs
[ 40.355894] calling regulator.20+ @ 1610, parent: 0-0009
[ 40.363838] call regulator.20+ returned 0 after 2479 usecs
[ 40.367912] calling regulator.19+ @ 1610, parent: 0-0009
[ 40.375796] call regulator.19+ returned 0 after 2480 usecs
[ 40.379874] calling regulator.18+ @ 1610, parent: 0-0009
[ 40.387789] call regulator.18+ returned 0 after 2513 usecs
[ 40.391837] calling regulator.17+ @ 1610, parent: 0-0009
[ 40.399825] call regulator.17+ returned 0 after 2482 usecs
[ 40.403868] calling regulator.16+ @ 1610, parent: 0-0009
[ 40.411816] call regulator.16+ returned 0 after 2481 usecs
[ 40.415864] calling regulator.15+ @ 1610, parent: 0-0009
[ 40.423813] call regulator.15+ returned 0 after 2483 usecs
[ 40.427891] calling regulator.14+ @ 1610, parent: 0-0009
[ 40.435775] call regulator.14+ returned 0 after 2480 usecs
[ 40.439852] calling regulator.13+ @ 1610, parent: 0-0009
[ 40.447747] call regulator.13+ returned 0 after 2491 usecs
[ 40.451791] calling regulator.12+ @ 1610, parent: 0-0009
[ 40.459718] call regulator.12+ returned 0 after 2493 usecs
[ 40.463760] calling regulator.11+ @ 1610, parent: 0-0009
[ 40.471704] call regulator.11+ returned 0 after 2478 usecs
[ 40.475747] calling regulator.10+ @ 1610, parent: 0-0009
[ 40.483693] call regulator.10+ returned 0 after 2479 usecs
[ 40.487766] calling regulator.9+ @ 1610, parent: 0-0009
[ 40.495563] call regulator.9+ returned 0 after 2482 usecs
[ 40.499553] calling regulator.8+ @ 1610, parent: 0-0009
[ 40.507358] call regulator.8+ returned 0 after 2489 usecs
[ 40.511317] calling regulator.7+ @ 1610, parent: 0-0009
[ 40.519148] call regulator.7+ returned 0 after 2482 usecs
[ 40.523105] calling regulator.6+ @ 1610, parent: 0-0009
[ 40.530965] call regulator.6+ returned 0 after 2481 usecs
[ 40.534918] calling regulator.5+ @ 1610, parent: 0-0009
[ 40.542777] call regulator.5+ returned 0 after 2480 usecs
[ 40.546732] calling regulator.4+ @ 1610, parent: 0-0009
[ 40.554589] call regulator.4+ returned 0 after 2480 usecs
[ 40.558576] calling regulator.3+ @ 1610, parent: 0-0009
[ 40.566375] call regulator.3+ returned 0 after 2481 usecs
[ 40.574330] calling regulator.2+ @ 1610, parent: regulator-usb3
[ 40.581488] call regulator.2+ returned 0 after 2503 usecs
[ 40.585445] calling regulator.1+ @ 1610, parent: vbat-fixed-regulator
[ 40.594529] call regulator.1+ returned 0 after 2483 usecs
[ 40.599129] calling 3860000.pinctrl+ @ 1610, parent: soc
[ 40.603864] call 3860000.pinctrl+ returned 0 after 6 usecs
[ 40.609438] calling 10d10000.pinctrl+ @ 1610, parent: soc
[ 40.614804] call 10d10000.pinctrl+ returned 0 after 9 usecs
[ 40.620443] calling 13400000.pinctrl+ @ 1610, parent: soc
[ 40.625838] call 13400000.pinctrl+ returned 0 after 20 usecs
[ 40.631656] calling 11400000.pinctrl+ @ 1610, parent: soc
[ 40.636963] call 11400000.pinctrl+ returned 0 after 33 usecs
[ 40.642621] calling 3810000.audss-clock-controller+ @ 1610, parent: soc
[ 40.649295] call 3810000.audss-clock-controller+ returned 0 after 2 usecs
[ 40.656038] calling DISP1+ @ 1610, parent: 10010000.clock-controller
[ 40.662615] call DISP1+ returned 0 after 134 usecs
[ 40.667491] calling regulator.0+ @ 1610, parent: reg-dummy
[ 40.675340] call regulator.0+ returned 0 after 2501 usecs
[ 40.680439] calling 145b0000.dp-controller+ @ 1610, parent: soc
[ 40.685291] call 145b0000.dp-controller+ returned 0 after 3 usecs
[ 40.691452] calling 14530000.hdmi+ @ 1610, parent: soc
[ 40.696569] call 14530000.hdmi+ returned 0 after 2 usecs
[ 40.704295] calling 14450000.mixer+ @ 1610, parent: soc
[ 40.708189] call 14450000.mixer+ returned 0 after 3 usecs
[ 40.713542] calling 14400000.fimd+ @ 1610, parent: soc
[ 40.718772] call 14400000.fimd+ returned 0 after 3 usecs
[ 40.727460] calling 14650000.sysmmu+ @ 1610, parent: soc
[ 40.731412] call 14650000.sysmmu+ returned 0 after 3 usecs
[ 40.736888] calling 14640000.sysmmu+ @ 1610, parent: soc
[ 40.742287] call 14640000.sysmmu+ returned 0 after 2 usecs
[ 40.747764] calling 13eb0000.sysmmu+ @ 1610, parent: soc
[ 40.753110] call 13eb0000.sysmmu+ returned 0 after 3 usecs
[ 40.758614] calling 13ea0000.sysmmu+ @ 1610, parent: soc
[ 40.763960] call 13ea0000.sysmmu+ returned 0 after 2 usecs
[ 40.769463] calling 13e90000.sysmmu+ @ 1610, parent: soc
[ 40.774809] call 13e90000.sysmmu+ returned 0 after 2 usecs
[ 40.780320] calling 13e80000.sysmmu+ @ 1610, parent: soc
[ 40.785659] call 13e80000.sysmmu+ returned 0 after 2 usecs
[ 40.791163] calling 13c50000.sysmmu+ @ 1610, parent: soc
[ 40.796510] call 13c50000.sysmmu+ returned 0 after 2 usecs
[ 40.802013] calling 13c40000.sysmmu+ @ 1610, parent: soc
[ 40.807386] call 13c40000.sysmmu+ returned 0 after 2 usecs
[ 40.812940] calling 11f20000.sysmmu+ @ 1610, parent: soc
[ 40.818284] call 11f20000.sysmmu+ returned 0 after 3 usecs
[ 40.823699] calling 11210000.sysmmu+ @ 1610, parent: soc
[ 40.829088] call 11210000.sysmmu+ returned 0 after 3 usecs
[ 40.834539] calling 11200000.sysmmu+ @ 1610, parent: soc
[ 40.839935] call 11200000.sysmmu+ returned 0 after 2 usecs
[ 40.845539] calling 3830000.i2s+ @ 1610, parent: soc
[ 40.850439] call 3830000.i2s+ returned 0 after 3 usecs
[ 40.855564] calling 12ce0000.i2c+ @ 1610, parent: soc
[ 40.860679] call 12ce0000.i2c+ returned 0 after 1 usecs
[ 40.865867] calling 12cd0000.i2c+ @ 1610, parent: soc
[ 40.871007] call 12cd0000.i2c+ returned 0 after 2 usecs
[ 40.876196] calling 12cb0000.i2c+ @ 1610, parent: soc
[ 40.881336] call 12cb0000.i2c+ returned 0 after 1 usecs
[ 40.886525] calling 12ca0000.i2c+ @ 1610, parent: soc
[ 40.891666] call 12ca0000.i2c+ returned 0 after 1 usecs
[ 40.896885] calling 3860000.pinctrl+ @ 1610, parent: soc
[ 40.902257] call 3860000.pinctrl+ returned 0 after 2 usecs
[ 40.907970] calling 3810000.audss-clock-controller+ @ 1610, parent: soc
[ 40.914748] call 3810000.audss-clock-controller+ returned 0 after 350
usecs
[ 40.921371] calling DISP1+ @ 1610, parent: 10010000.clock-controller
[ 40.928050] call DISP1+ returned 0 after 263 usecs
[ 40.932597] calling 12c90000.i2c+ @ 1610, parent: soc
[ 40.937847] call 12c90000.i2c+ returned 0 after 165 usecs
[ 40.943034] calling 12c80000.i2c+ @ 1610, parent: soc
[ 40.948176] call 12c80000.i2c+ returned 0 after 3 usecs
[ 40.953362] calling 12c70000.i2c+ @ 1610, parent: soc
[ 40.958505] call 12c70000.i2c+ returned 0 after 4 usecs
[ 40.963690] calling 12c60000.i2c+ @ 1610, parent: soc
[ 40.968833] call 12c60000.i2c+ returned 0 after 3 usecs
[ 40.974280] Disabling non-boot CPUs ...
[ 41.019014] IRQ55 no longer affine to CPU1
[ 41.022280] PM: Calling exynos_pm_suspend+0x0/0x50
[ 41.029707] PM: Calling sched_clock_suspend+0x0/0x30
[ 41.034649] PM: Calling timekeeping_suspend+0x0/0x2f8
[ 41.034649] PM: Calling irq_gc_suspend+0x0/0x6c
[ 41.034649] PM: Calling fw_suspend+0x0/0x18
[ 41.034649] PM: Calling cpu_pm_suspend+0x0/0x18
[ 41.034649] PM: Calling exynos_clkout_suspend+0x0/0x24
[ 41.034649] PM: Calling exynos5250_clk_suspend+0x0/0x20
[ 41.034649] PM: Calling combiner_suspe[ 41.066995] call
12c30000.serial+ returned 0 after 60 usecs
[ 41.071122] calling 12c60000.i2c+ @ 1610, parent: soc
[ 41.076307] call 12c60000.i2c+ returned 0 after 1 usecs
[ 41.081450] calling 12c70000.i2c+ @ 1610, parent: soc
[ 41.086607] call 12c70000.i2c+ returned 0 after 1 usecs
[ 41.091807] calling 12c80000.i2c+ @ 1610, parent: soc
[ 41.096898] call 12c80000.i2c+ returned 0 after 1 usecs
[ 41.102133] calling 12c90000.i2c+ @ 1610, parent: soc
[ 41.107228] call 12c90000.i2c+ returned 0 after 1 usecs
[ 41.112470] calling 12dd0000.pwm+ @ 1610, parent: soc
[ 41.117569] call 12dd0000.pwm+ returned 0 after 13 usecs
[ 41.122880] calling 101e0000.rtc+ @ 1610, parent: soc
[ 41.127975] s3c-btc 101e0000.rtc: rtc disabled, re-enabling
[ 41.133558] call 101e0000.rtc+ returned 0 after 5456 usecs
[ 41.139000] calling 10830000.sss+ @ 1610, parent: soc
[ 41.144142] call 10830000.sss+ returned 0 after 2 usecs
[ 41.149328] calling 10830400.rng+ @ 1610, parent: soc
[ 41.154472] call 10830400.rng+ returned 0 after 1 usecs
[ 41.159657] calling 10830600.rng+ @ 1610, parent: soc
[ 41.164802] call 10830600.rng+ returned 0 after 3 usecs
[ 41.169987] calling 10850000.g2d+ @ 1610, parent: soc
[ 41.175129] call 10850000.g2d+ returned 0 after 1 usecs
[ 41.180315] calling 2020000.sysram+ @ 1610, parent: soc
[ 41.185633] call 2020000.sysram+ returned 0 after 1 usecs
[ 41.190992] calling 10044000.power-domain+ @ 1610, parent: soc
[ 41.196920] call 10044000.power-domain+ returned 0 after 1 usecs
[ 41.202976] calling 10044040.power-domain+ @ 1610, parent: soc
[ 41.208787] call 10044040.power-domain+ returned 0 after 1 usecs
[ 41.214811] calling 10044060.power-domain+ @ 1610, parent: soc
[ 41.220678] call 10044060.power-domain+ returned 0 after 1 usecs
[ 41.226696] calling 100440a0.power-domain+ @ 1610, parent: soc
[ 41.232594] call 100440a0.power-domain+ returned 0 after 1 usecs
[ 41.238563] calling 100440c0.power-domain+ @ 1610, parent: soc
[ 41.244536] call 100440c0.power-domain+ returned 0 after 1 usecs
[ 41.250455] calling 10010000.clock-controller+ @ 1610, parent: soc
[ 41.256742] call 10010000.clock-controller+ returned 0 after 1 usecs
[ 41.263088] calling soc:timer+ @ 1610, parent: soc
[ 41.267891] call soc:timer+ returned 0 after 1 usecs
[ 41.272868] calling 101c0000.mct+ @ 1610, parent: soc
[ 41.277962] call 101c0000.mct+ returned 0 after 1 usecs
[ 41.283199] calling soc:pmu+ @ 1610, parent: soc
[ 41.287857] call soc:pmu+ returned 0 after 2 usecs
[ 41.292658] calling 11400000.pinctrl+ @ 1610, parent: soc
[ 41.298103] call 11400000.pinctrl+ returned 0 after 1 usecs
[ 41.303773] calling 13400000.pinctrl+ @ 1610, parent: soc
[ 41.309125] call 13400000.pinctrl+ returned 0 after 1 usecs
[ 41.314738] calling 10d10000.pinctrl+ @ 1610, parent: soc
[ 41.320149] call 10d10000.pinctrl+ returned 0 after 2 usecs
[ 41.325757] calling 10040000.system-controller+ @ 1610, parent: soc
[ 41.332069] call 10040000.system-controller+ returned 0 after 1 usecs
[ 41.338471] calling 101d0000.watchdog+ @ 1610, parent: soc
[ 41.344054] s3c2410-wdt 101d0000.watchdog: watchdog disabled
[ 41.349659] call 101d0000.watchdog+ returned 0 after 5485 usecs
[ 41.355593] calling 11000000.codec+ @ 1610, parent: soc
[ 41.360858] call 11000000.codec+ returned 0 after 1 usecs
[ 41.366266] calling 11c00000.rotator+ @ 1610, parent: soc
[ 41.371736] call 11c00000.rotator+ returned 0 after 1 usecs
[ 41.377266] calling 10060000.tmu+ @ 1610, parent: soc
[ 41.382437] call 10060000.tmu+ returned 0 after 31 usecs
[ 41.387681] calling 12ca0000.i2c+ @ 610, parent: soc
[ 41.392823] call 12ca0000.i2c+ returned 0 after 1 usecs
[ 41.398010] calling 12cb0000.i2c+ @ 1610, parent: soc
[ 41.403152] call 12cb0000.i2c+ returned 0 after 1 usecs
[ 41.408339] calling 12cd0000.i2c+ @ 1610, parent: soc
[ 41.413481] call 12cd0000.i2c+ returned 0 after 1 usecs
[ 41.418669] calling 12ce0000.i2c+ @ 1610, parent: soc
[ 41.423811] call 12ce0000.i2c+ returned 0 after 1 usecs
[ 41.428998] calling 12d30000.spi+ @ 1610, parent: soc
[ 41.434413] call 12d30000.spi+ returned 0 after 268 usecs
[ 41.439502] calling 12200000.mmc+ @ 1610, parent: soc
[ 41.444837] call 12200000.mmc+ returned 0 after 188 usecs
[ 41.450010] calling 12220000.mmc+ @ 1610, parent: soc
[ 41.450061] calling mmc0:0001+ @ 1643, parent: mmc0
[ 41.455218] call 12220000.mmc+ returned 0 after 26 usecs
[ 41.460128] call mmc0:0001+ returned 0 after 19 usecs
[ 41.465409] calling 12230000.mmc+ @ 1610, parent: soc
[ 41.470448] calling mmc1:e624+ @ 1644, parent: mmc1
[ 41.475574] call 12230000.mmc+ returned 0 after 31 usecs
[ 41.480499] call mmc1:e624+ returned 0 after 8 usecs
[ 41.485796] calling 3830000.i2s+ @ 1610, parent: soc
[ 41.490756] calling mmc2:0001+ @ 1646, parent: mmc2
[ 41.495767] call 3830000.i2s+ returned 0 after 2 usecs
[ 41.495778] calling soc:usb_dwc3+ @ 1610, parent: soc
[ 41.511006] call soc:usb_dwc3+ returned 0 after 63 usecs
[ 41.516269] calling 12100000.phy+ @ 1610, parent: soc
[ 41.521357] call 12100000.phy+ returned 0 after 2 usecs
[ 41.526591] calling 12110000.usb+ @ 1610, parent: soc
[ 41.532034] usb usb1: root hub lost power or was reset
[ 41.536810] call 12110000.usb+ returned 0 after 4980 usecs
[ 41.542304] calling 12120000.usb+ @ 1610, parent: soc
[ 41.542319] calling usb1+ @ 1617, parent: 12110000.usb
[ 41.551709] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req
400000Hz, actual 396825HZ div = 63)
[ 41.615745] usb usb2: root hub lost power or was reset
[ 41.619947] call 12120000.usb+ returned 0 after 70860 usecs
[ 41.625087] calling 12130000.phy+ @ 1610, parent: soc
[ 41.625111] calling usb2+ @ 1613, parent: 12120000.usb
[ 41.630177] call 12130000.phy+ returned 0 after 2 usecs
[ 41.640597] calling soc:amba+ @ 1610, parent: soc
[ 41.645371] call soc:amba+ returned 0 after 1 usecs
[ 41.650193] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req
50000000Hz, actual 50000000HZ div = 0)
[ 41.659959] calling 121a0000.pdma+ @ 1610, parent: soc:amba
[ 41.660009] call mmc2:0001+ returned 0 after 155559 usecs
[ 41.665553] call 121a0000.pdma+ returned 0 after 5 usecs
[ 41.665565] calling 121b0000.pdma+ @ 1610, parent: soc:amba
[ 41.681649] calling mmc2:0001:1+ @ 1647, parent: mmc2:0001
[ 41.682210] call 121b0000.pdma+ returned 0 after 5 usecs
[ 41.687397] call mmc2:0001:1+ returned 0 after 1 usecs
[ 41.692768] calling 10800000.mdma+ @ 1610, parent: soc:amba
[ 41.697822] calling mmc2:0001:2+ @ 1648, parent: mmc2:0001
[ 41.703483] call 10800000.mdma+ returned 0 after 4 usecs
[ 41.709022] calling mmc2:0001:3+ @ 1649, parent: mmc2:0001
[ 41.714329] calling 11c10000.mdma+ @ 1610, parent: soc:amba
[ 41.719870] call mmc2:0001:3+ returned 0 after 1 usecs
[ 41.725590] call mmc2:0001:2+ returned 0 after 1 usecs
[ 41.731642] call 11c10000.mdma+ returned 0 after 6 usecs
[ 41.741045] calling 13e00000.gsc+ @ 1610, parent: soc
[ 41.746186] call 13e00000.gsc+ returned 0 after 1 usecs
[ 41.751373] calling 13e10000.gsc+ @ 1610, parent: soc
[ 41.756516] call 13e10000.gsc+ returned 0 after 1 usecs
[ 41.761724] calling 13e20000.gsc+ @ 1610, parent: soc
[ 41.766820] call 13e20000.gsc+ returned 0 after 1 usecs
[ 41.772058] calling 13e30000.gsc+ @ 1610, parent: soc
[ 41.777149] call 13e30000.gsc+ returned 0 after 1 usecs
[ 41.782386] calling 101b0000.cec+ @ 1610, parent: soc
[ 41.787479] call 101b0000.cec+ returned 0 after 1 usecs
[ 41.792715] calling soc:video-phy+ @ 1610, parent: soc
[ 41.797895] call soc:video-phy+ returned 0 after 2 usecs
[ 41.801680] call usb1+ returned 0 after 243207 usecs
[ 41.803225] calling 10a60000.sysmmu+ @ 1610, parent: soc
[ 41.808275] calling 1-1+ @ 1635, parent: usb1
[ 41.813545] call 10a60000.sysmmu+ returned 0 after 2 usecs
[ 41.813563] calling 11200000.sysmmu+ @ 1610, parent: soc
[ 41.828798] call 11200000.sysmmu+ returned 0 after 2 usecs
[ 41.834298] calling 11210000.sysmmu+ @ 1610, parent: soc
[ 41.839649] call 11210000.sysmmu+ returned 0 after 3 usecs
[ 41.845147] calling 11d40000.sysmmu+ @ 1610, parent: soc
[ 41.850498] call 11d40000.sysmmu+ returned 0 after 3 usecs
[ 41.855997] calling 11f20000.sysmmu+ @ 1610, parent: soc
[ 41.861348] call 11f20000.sysmmu+ returned 0 after 2 usecs
[ 41.866846] calling 13260000.sysmmu+ @ 1610, parent: soc
[ 41.872264] call 13260000.sysmmu+ returned 0 after 2 usecs
[ 41.877673] calling 13270000.sysmmu+ @ 1610, parent: soc
[ 41.881864] call usb2+ returned 0 after 240745 usecs
[ 41.883075] call 13270000.sysmmu+ returned 0 after 3 usecs
[ 41.893496] calling 132a0000.sysmmu+ @ 1610, parent: soc
[ 41.898845] call 132a0000.sysmmu+ returned 0 after 2 usecs
[ 41.904345] calling 13280000.sysmmu+ @ 1610, parent: soc
[ 41.909695] call 13280000.sysmmu+ returned 0 after 2 usecs
[ 41.915194] calling 13290000.sysmmu+ @ 1610, parent: soc
[ 41.920546] call 13290000.sysmmu+ returned 0 after 3 usecs
[ 41.926044] calling 132b0000.sysmmu+ @ 1610, parent: soc
[ 41.931396] call 132b0000.sysmmu+ returned 0 after 3 usecs
[ 41.936900] calling 132c0000.sysmmu+ @ 1610, parent: soc
[ 41.942270] call 132c0000.sysmmu+ returned 0 after 2 usecs
[ 41.947720] calling 132d0000.sysmmu+ @ 1610, parent: soc
[ 41.953122] call 132d0000.sysmmu+ returned 0 after 3 usecs
[ 41.958570] calling 132e0000.sysmmu+ @ 1610, parent: soc
[ 41.962417] usb 1-1: reset high-speed USB device number 2 using
exynos-ehci
[ 41.963970] call 132e0000.sysmmu+ returned 0 after 3 usecs
[ 41.976423] calling 132f0000.sysmmu+ @ 1610, parent: soc
[ 41.981764] call 132f0000.sysmmu+ returned 0 after 2 usecs
[ 41.987225] calling 13c40000.sysmmu+ @ 1610, parent: soc
[ 41.992627] call 13c40000.sysmmu+ returned 0 after 2 usecs
[ 41.998072] calling 13c50000.sysmmu+ @ 1610, parent: soc
[ 42.003469] call 13c50000.sysmmu+ returned 0 after 2 usecs
[ 42.008913] calling 13e80000.sysmmu+ @ 1610, parent: soc
[ 42.014319] call 13e80000.sysmmu+ returned 0 after 2 usecs
[ 42.019763] calling 13e90000.sysmmu+ @ 1610, parent: soc
[ 42.025166] call 13e90000.sysmmu+ returned 0 after 2 usecs
[ 42.030613] calling 13ea0000.sysmmu+ @ 1610, parent: soc
[ 42.036015] call 13ea0000.sysmmu+ returned 0 after 2 usecs
[ 42.041463] calling 13eb0000.sysmmu+ @ 1610, parent: soc
[ 42.046863] call 13eb0000.sysmmu+ returned 0 after 2 usecs
[ 42.052336] calling 14640000.sysmmu+ @ 1610, parent: soc
[ 42.057753] call 14640000.sysmmu+ returned 0 after 65 usecs
[ 42.063283] calling 14650000.sysmmu+ @ 1610, parent: soc
[ 42.068626] call 14650000.sysmmu+ returned 0 after 3 usecs
[ 42.074129] calling opp_table0+ @ 1610, parent: platform
[ 42.079475] call opp_table0+ returned 0 after 1 usecs
[ 42.084575] calling gpio-keys+ @ 1610, parent: platform
[ 42.089805] wake disabled for irq 152
[ 42.093464] wake disabled for irq 153
[ 42.097095] call gpio-keys+ returned 0 after 7122 usecs
[ 42.102331] calling vbat-fixed-regulator+ @ 1610, parent: platform
[ 42.108559] call vbat-fixed-regulator+ returned 0 after 2 usecs
[ 42.114486] calling i2c-arbitrator+ @ 1610, parent: platform
[ 42.120186] call i2c-arbitrator+ returned 0 after 2 usecs
[ 42.125615] calling regulator-usb3+ @ 1610, parent: platform
[ 42.131306] call regulator-usb3+ returned 0 after 1 usecs
[ 42.136717] calling mmc3_pwrseq+ @ 1610, parent: platform
[ 42.142172] call mmc3_pwrseq+ returned 0 after 1 usecs
[ 42.147294] calling 0-0009+ @ 1610, parent: i2c-0
[ 42.152352] call 0-0009+ returned 0 after 279 usecs
[ 42.156913] calling 1-0067+ @ 1610, parent: i2c-1
[ 42.161775] wake disabled for irq 148
[ 42.321621] call 1-0067+ returned 0 after 156102 usecs
[ 42.325614] calling regulatory.0+ @ 1610, parent: platform
[ 42.330866] call regulatory.0+ returned 0 after 1 usecs
[ 42.336121] calling alarmtimer+ @ 1610, parent: platform
[ 42.341459] call alarmtimer+ returned 0 after 6 usecs
[ 42.348605] calling serial8250+ @ 1610, parent: platform
[ 42.352589] call serial8250+ returned 0 after 2 usecs
[ 42.357625] calling exynos-drm+ @ 1610, parent: platform
[ 42.478238] exynos-dp 145b0000.dp-controller: Link Training Clock
Recovery success
[ 42.487049] exynos-dp 145b0000.dp-controller: Link Training success!
[ 42.598098] exynos-dp 145b0000.dp-controller: Timeout of video
streamclk ok
[ 42.603648] exynos-dp 145b0000.dp-controller: unable to config video
[ 42.632081] call 1-1+ returned 0 after 794948 usecs
[ 42.654712] call exynos-drm+ returned 0 after 284877 usecs
[ 42.660368] calling max77686-pmic+ @ 1610, parent: 0-0009
[ 42.665845] call max77686-pmic+ returned 0 after 1 usecs
[ 42.671229] calling max77686-rtc+ @ 1610, parent: 0-0009
[ 42.676798] wake disabled for irq 146
[ 42.680400] call max77686-rtc+ returned 0 after 3705 usecs
[ 42.685914] calling max77686-clk+ @ 1610, parent: 0-0009
[ 42.691260] call max77686-clk+ returned 0 after 1 usecs
[ 42.696508] calling Fixed MDIO bus.0+ @ 1610, parent: platform
[ 42.702422] call Fixed MDIO bus.0+ returned 0 after 1 usecs
[ 42.708756] calling usb_phy_generic.0.auto+ @ 1610, parent: platform
[ 42.715664] call usb_phy_generic.0.auto+ returned 0 after 1 usecs
[ 42.721785] calling usb_phy_generic.1.auto+ @ 1610, parent: platform
[ 42.728251] call usb_phy_generic.1.auto+ returned 0 after 1 usecs
[ 42.734379] calling 12000000.dwc3+ @ 1610, parent: soc:usb_dwc3
[ 42.740472] call 12000000.dwc3+ returned 0 after 79 usecs
[ 42.745933] calling input0+ @ 1610, parent: 1-0067
[ 42.745948] calling xhci-hcd.2.auto+ @ 1618, parent: 12000000.dwc3
[ 42.750813] call input0+ returned 0 after 3 usecs
[ 42.757161] usb usb3: root hub lost power or was reset
[ 42.761865] calling rtc0+ @ 1610, parent: max77686-rtc
[ 42.767037] usb usb4: root hub lost power or was reset
[ 42.780258] call xhci-hcd.2.auto+ returned 0 after 22597 usecs
[ 42.786253] calling usb3+ @ 1625, parent: xhci-hcd.2.auto
[ 42.791825] calling usb4+ @ 1630, parent: xhci-hcd.2.auto
[ 42.802300] call rtc0+ returned 0 after 29281 usecs
[ 42.807236] calling rtc1+ @ 1610, parent: 101e0000.rtc
[ 42.812588] call rtc1+ returned 0 after 1 usecs
[ 42.817220] calling 104-001e+ @ 1610, parent: i2c-104
[ 42.825054] wake disabled for irq 150
[ 42.911689] call usb4+ returned 0 after 111658 usecs
[ 42.912072] call usb3+ returned 0 after 111335 usecs
[ 44.505817] asix 1-1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
*** break sent ***
[ 63.472452] sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c)
show-all-locks(d) terminate-all-tasks(e) memory-full-oom-kill(f)
kill-all-tasks(i) thaw-filesystems(j) sak(k)
show-backtrace-all-active-cpus(l) show-memory-usage(m)
nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q)
unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V)
show-blocked-tasks(w) dump-ftrace-buffer(z)
*** break sent ***
[ 66.873020] sysrq: SysRq : Show backtrace of all active CPUs
[ 66.878907] NMI backtrace for cpu 0
[ 66.882602] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
[ 66.891572] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 66.897948] [<c0111ed0>] (unwind_backtrace) from [<c010e4ec>]
(show_stack+0x10/0x14)
[ 66.905999] [<c010e4ec>] (show_stack) from [<c09cea04>]
(dump_stack+0x90/0xc8)
[ 66.913539] [<c09cea04>] (dump_stack) from [<c09d4ab4>]
(nmi_cpu_backtrace+0xf8/0x10c)
[ 66.921777] [<c09d4ab4>] (nmi_cpu_backtrace) from [<c09d4bd8>]
(nmi_trigger_cpumask_backtrace+0x110/0x148)
[ 66.931793] [<c09d4bd8>] (nmi_trigger_cpumask_backtrace) from
[<c04c0d3c>] (__handle_sysrq+0xdc/0x250)
[ 66.941482] [<c04c0d3c>] (__handle_sysrq) from [<c04da95c>]
(s3c24xx_serial_rx_drain_fifo+0x134/0x224)
[ 66.951191] [<c04da95c>] (s3c24xx_serial_rx_drain_fifo) from
[<c04db568>] (s3c24xx_serial_rx_chars+0x6c/0x198)
[ 66.961600] [<c04db568>] (s3c24xx_serial_rx_chars) from [<c04db6dc>]
(s3c64xx_serial_handle_irq+0x48/0x60)
[ 66.971644] [<c04db6dc>] (s3c64xx_serial_handle_irq) from
[<c018eb0c>] (__handle_irq_event_percpu+0x98/0x510)
[ 66.981975] [<c018eb0c>] (__handle_irq_event_percpu) from
[<c018efa0>] (handle_irq_event_percpu+0x1c/0x58)
[ 66.992059] [<c018efa0>] (handle_irq_event_percpu) from [<c018f014>]
(handle_irq_event+0x38/0x5c)
[ 67.001370] [<c018f014>] (handle_irq_event) from [<c01927dc>]
(handle_fasteoi_irq+0xa4/0x138)
[ 67.010341] [<c01927dc>] (handle_fasteoi_irq) from [<c018e2e4>]
(generic_handle_irq+0x18/0x28)
[ 67.019428] [<c018e2e4>] (generic_handle_irq) from [<c018e400>]
(__handle_domain_irq+0x6c/0xe4)
[ 67.028610] [<c018e400>] (__handle_domain_irq) from [<c0465ca4>]
(gic_handle_irq+0x54/0xa0)
[ 67.037441] [<c0465ca4>] (gic_handle_irq) from [<c01019f0>]
(__irq_svc+0x70/0xb0)
[ 67.045410] Exception stack(0xc0f01ee8 to 0xc0f01f30)
[ 67.050934] 1ee0: 00000001 00000001 00000000
c0f0bc00 91f13160 0000000f
[ 67.059626] 1f00: 00000000 c0f7aad4 00000000 00000000 eefb47c0
00000000 00000000 c0f01f38
[ 67.068324] 1f20: c0180a08 c06c4e0c 20000153 ffffffff
[ 67.073876] [<c01019f0>] (__irq_svc) from [<c06c4e0c>]
(cpuidle_enter_state+0x1c0/0x498)
[ 67.082500] [<c06c4e0c>] (cpuidle_enter_state) from [<c015c1e8>]
(do_idle+0x1c0/0x278)
[ 67.090967] [<c015c1e8>] (do_idle) from [<c015c5e0>]
(cpu_startup_entry+0x18/0x1c)
[ 67.099089] [<c015c5e0>] (cpu_startup_entry) from [<c0e00dc0>]
(start_kernel+0x3ec/0x46c)
[ 67.107837] Sending NMI from CPU 0 to CPUs 1:
[ 67.112750] NMI backtrace for cpu 1
[ 67.112756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
[ 67.112758] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 67.112764] PC is at cpuidle_enter_state+0x1c0/0x498
[ 67.112769] LR is at trace_hardirqs_on_caller+0x100/0x1e0
[ 67.112772] pc : [<c06c4e0c>] lr : [<c0180a08>] psr: 20000013
[ 67.112775] sp : ee8f7f70 ip : 00000000 fp : 00000000
[ 67.112777] r10: eefc67c0 r9 : 00000000 r8 : 00000001
[ 67.112780] r7 : c0f7aad4 r6 : 00000001 r5 : 0000000f r4 : a03b2a20
[ 67.112782] r3 : ee8ea640 r2 : 00000000 r1 : 00000001 r0 : 00000001
[ 67.112786] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM
Segment none
[ 67.112788] Control: 10c5387d Table: 6c06806a DAC: 00000051
[ 67.112793] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
[ 67.112795] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 67.112801] [<c0111ed0>] (unwind_backtrace) from [<c010e4ec>]
(show_stack+0x10/0x14)
[ 67.112807] [<c010e4ec>] (show_stack) from [<c09cea04>]
(dump_stack+0x90/0xc8)
[ 67.112813] [<c09cea04>] (dump_stack) from [<c09d4a64>]
(nmi_cpu_backt2ace+0xa8/0x10c)
[ 67.112818] [<c09d4a64>] (nmi_cpu_backtrace) from [<c0110c4c>]
(handle_IPI+0x108/0x3e4)
[ 67.112824] [<c0110c4c>] (handle_IPI) from [<c0465ce4>]
(gic_handle_irq+0x94/0xa0)
[ 67.112829] [<c0465ce4>] (gic_handle_irq) from [<c01019f0>]
(__irq_svc+0x70/0xb0)
[ 67.112831] Exception stack(0xee8f7f20 to 0xee8f7f68)
[ 67.112836] 7f20: 00000001 00000001 00000000 ee8ea640 a03b2a20
0000000f 00000001 c0f7aad4
[ 67.112841] 7f40: 00000001 00000000 eefc67c0 00000000 00000000
ee8f7f70 c0180a08 c06c4e0c
[ 67.112844] 7f60: 20000013 ffffffff
[ 67.112850] [<c01019f0>] (__irq_svc) from [<c06c4e0c>]
(cpuidle_enter_state+0x1c0/0x498)
[ 67.112857] [<c06c4e0c>] (cpuidle_enter_state) from [<c015c1e8>]
(do_idle+0x1c0/0x278)
[ 67.112862] [<c015c1e8>] (do_idle) from [<c015c5e0>]
(cpu_startup_entry+0x18/0x1c)
[ 67.112867] [<c015c5e0>] (cpu_startup_entry) from [<401028ac>]
(0x401028ac)
[ 67.114359] cros-ec-i2c 104-001e: bad packet checksum
[ 67.322533] call 104-001e+ returned 0 after 23925980 usecs
[ 67.328468] calling cros-ec-dev.3.auto+ @ 1610, parent: 104-001e
[ 67.335024] call cros-ec-dev.3.auto+ returned 0 after 1 usecs
[ 67.341192] calling
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+ @ 1610,
parent: 104-001e
[ 67.351704] call
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+
returned 0 after 1 usecs
[ 67.361881] calling input1+ @ 1610, parent:
i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller
[ 67.372254] call input1+ returned 0 after 3 usecs
[ 67.377450] calling tps65090-pmic+ @ 1610, parent: 104-0048
[ 67.383604] call tps65090-pmic+ returned 0 after 1 usecs
[ 67.389409] calling tps65090-charger+ @ 1610, parent: 104-0048
[ 67.395783] call tps65090-charger+ returned 0 after 1 usecs
[ 67.401811] calling cpufreq-dt+ @ 1610, parent: platform
[ 67.407613] call cpufreq-dt+ returned 0 after 1 usecs
[ 67.413094] calling snd-soc-dummy+ @ 1610, parent: platform
[ 67.419141] call snd-soc-dummy+ returned 0 after 1 usecs
[ 67.424949] calling backlight+ @ 1610, parent: platform
[ 67.430781] call backlight+ returned 0 after 206 usecs
[ 67.436251] calling backlight+ @ 1610, parent: backlight
[ 67.441954] call backlight+ returned 0 after 3 usecs
[ 67.447256] calling hdmi-audio-codec.4.auto+ @ 1610, parent:
14530000.hdmi
[ 67.454596] call hdmi-audio-codec.4.auto+ returned 0 after 1 usecs
[ 67.461098] calling panel+ @ 1610, parent: platform
[ 67.466391] call panel+ returned 0 after 1 usecs
[ 67.471315] calling sound+ @ 1610, parent: platform
[ 67.477289] call sound+ returned 0 after 673 usecs
[ 67.482595] calling input2+ @ 1610, parent: gpio-keys
[ 67.488097] call input2+ returned 0 after 2 usecs
[ 67.498847] OOM killer enabled.
[ 67.502391] Restarting tasks ... done.
> ---
> drivers/input/keyboard/cros_ec_keyb.c | 30 ++++++++++-----------------
> 1 file changed, 11 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/input/keyboard/cros_ec_keyb.c b/drivers/input/keyboard/cros_ec_keyb.c
> index 489ddd37bd4ee..c5e32544130dc 100644
> --- a/drivers/input/keyboard/cros_ec_keyb.c
> +++ b/drivers/input/keyboard/cros_ec_keyb.c
> @@ -242,19 +242,17 @@ static int cros_ec_keyb_work(struct notifier_block *nb,
> u32 val;
> unsigned int ev_type;
>
> + /*
> + * If not wake enabled, discard key state changes during
> + * suspend. Switches will be re-checked in
> + * cros_ec_keyb_resume() to be sure nothing is lost.
> + */
> + if (queued_during_suspend && !device_may_wakeup(ckdev->dev))
> + return NOTIFY_OK;
> +
> switch (ckdev->ec->event_data.event_type) {
> case EC_MKBP_EVENT_KEY_MATRIX:
> - if (device_may_wakeup(ckdev->dev)) {
> - pm_wakeup_event(ckdev->dev, 0);
> - } else {
> - /*
> - * If keyboard is not wake enabled, discard key state
> - * changes during suspend. Switches will be re-checked
> - * in cros_ec_keyb_resume() to be sure nothing is lost.
> - */
> - if (queued_during_suspend)
> - return NOTIFY_OK;
> - }
> + pm_wakeup_event(ckdev->dev, 0);
>
> if (ckdev->ec->event_size != ckdev->cols) {
> dev_err(ckdev->dev,
> @@ -268,10 +266,7 @@ static int cros_ec_keyb_work(struct notifier_block *nb,
> break;
>
> case EC_MKBP_EVENT_SYSRQ:
> - if (device_may_wakeup(ckdev->dev))
> - pm_wakeup_event(ckdev->dev, 0);
> - else if (queued_during_suspend)
> - return NOTIFY_OK;
> + pm_wakeup_event(ckdev->dev, 0);
>
> val = get_unaligned_le32(&ckdev->ec->event_data.data.sysrq);
> dev_dbg(ckdev->dev, "sysrq code from EC: %#x\n", val);
> @@ -280,10 +275,7 @@ static int cros_ec_keyb_work(struct notifier_block *nb,
>
> case EC_MKBP_EVENT_BUTTON:
> case EC_MKBP_EVENT_SWITCH:
> - if (device_may_wakeup(ckdev->dev))
> - pm_wakeup_event(ckdev->dev, 0);
> - else if (queued_during_suspend)
> - return NOTIFY_OK;
> + pm_wakeup_event(ckdev->dev, 0);
>
> if (ckdev->ec->event_data.event_type == EC_MKBP_EVENT_BUTTON) {
> val = get_unaligned_le32(
>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
^ permalink raw reply
* Built in PS2 keyboard in new ASUS/acer laptops can not wake up system after s2idle
From: Chris Chiu @ 2018-08-03 8:04 UTC (permalink / raw)
To: Dmitry Torokhov, Rafael J. Wysocki, linux-input, linux-pm,
Linux Kernel, Linux Upstreaming Team
Hi guys,
We have some new laptops with Intel new Intel WiskyLake CPU come
in and they all have the same problem. They all have the so-called
"Modern Standby" feature which is s2idle in Linux.
The problem is the built-in keyboard no longer wake up the system
after it goes to s2idle. Only the power button can wake up. It's
different from the other laptops with old Intel CPUs (CoffeeLake,
KaybeLake...etc). We found the difference is that the EC (embedded
controller) no longer signals SCI event when in s2idle.
Confirmed with ASUS EC engineer, he also admits that the EC code
for signaling SCI event in modern standby has been removed on
WiskyLake models. Because the built-in PS2 keyboard can still wake up
the system on WisksyLake+Windows10 RS4 combination without EC
intervention.
Based on this information, we suspect that maybe the built-in
keyboard wakeup on Windows 10 RS4 in enabled by default (although we
don't know how to prove that). It's easy to simply do
'device_set_wakeup_enable' and 'enable_irq_wake' for the i8042
keyboard port to wake up the system without EC, but it's nasty.
Any suggestion about how to achieve the keyboard wake up function
on these new laptops in a generic way? Thanks
Chris
^ permalink raw reply
* Re: [PATCH v11 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC
From: kbuild test robot @ 2018-08-03 10:10 UTC (permalink / raw)
To: Matti Vaittinen
Cc: kbuild-all, lee.jones, robh+dt, mark.rutland, eballetbo,
linus.walleij, mazziesaccount, dmitry.torokhov, linux-clk,
devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <77184f651e5cefb112f1061bc682b759f88144c6.1532946848.git.matti.vaittinen@fi.rohmeurope.com>
Hi Matti,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.18-rc7 next-20180802]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Matti-Vaittinen/mfd-bd71837-mfd-driver-for-ROHM-BD71837-PMIC/20180730-204810
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
smatch warnings:
drivers/mfd/rohm-bd718x7.c:163 bd71837_i2c_probe() warn: unsigned 'button.irq' is never less than zero.
vim +163 drivers/mfd/rohm-bd718x7.c
88
89 static int bd71837_i2c_probe(struct i2c_client *i2c,
90 const struct i2c_device_id *id)
91 {
92 struct bd71837 *bd71837;
93 int ret, i;
94 unsigned int val;
95
96 bd71837 = devm_kzalloc(&i2c->dev, sizeof(struct bd71837), GFP_KERNEL);
97
98 if (!bd71837)
99 return -ENOMEM;
100
101 bd71837->chip_irq = i2c->irq;
102
103 if (!bd71837->chip_irq) {
104 dev_err(&i2c->dev, "No IRQ configured\n");
105 return -EINVAL;
106 }
107
108 bd71837->dev = &i2c->dev;
109 dev_set_drvdata(&i2c->dev, bd71837);
110
111 bd71837->regmap = devm_regmap_init_i2c(i2c, &bd71837_regmap_config);
112 if (IS_ERR(bd71837->regmap)) {
113 dev_err(&i2c->dev, "regmap initialization failed\n");
114 return PTR_ERR(bd71837->regmap);
115 }
116
117 ret = regmap_read(bd71837->regmap, BD71837_REG_REV, &val);
118 if (ret) {
119 dev_err(&i2c->dev, "Read BD71837_REG_DEVICE failed\n");
120 return ret;
121 }
122 for (i = 0; i < ARRAY_SIZE(supported_revisions); i++)
123 if (supported_revisions[i] == val)
124 break;
125
126 if (i == ARRAY_SIZE(supported_revisions)) {
127 dev_err(&i2c->dev, "Unsupported chip revision\n");
128 return -ENODEV;
129 }
130
131 ret = devm_regmap_add_irq_chip(&i2c->dev, bd71837->regmap,
132 bd71837->chip_irq, IRQF_ONESHOT, 0,
133 &bd71837_irq_chip, &bd71837->irq_data);
134 if (ret) {
135 dev_err(&i2c->dev, "Failed to add irq_chip\n");
136 return ret;
137 }
138
139 /* Configure short press to 10 milliseconds */
140 ret = regmap_update_bits(bd71837->regmap,
141 BD71837_REG_PWRONCONFIG0,
142 BD718XX_PWRBTN_PRESS_DURATION_MASK,
143 BD718XX_PWRBTN_SHORT_PRESS_10MS);
144 if (ret) {
145 dev_err(&i2c->dev, "Failed to configure button short press timeout\n");
146 return ret;
147 }
148
149 /* Configure long press to 10 seconds */
150 ret = regmap_update_bits(bd71837->regmap,
151 BD71837_REG_PWRONCONFIG1,
152 BD718XX_PWRBTN_PRESS_DURATION_MASK,
153 BD718XX_PWRBTN_LONG_PRESS_10S);
154
155 if (ret) {
156 dev_err(&i2c->dev, "Failed to configure button long press timeout\n");
157 return ret;
158 }
159
160 button.irq = regmap_irq_get_virq(bd71837->irq_data,
161 BD71837_INT_PWRBTN_S);
162
> 163 if (button.irq < 0) {
164 dev_err(&i2c->dev, "Failed to get the IRQ\n");
165 return button.irq;
166 }
167
168 ret = devm_mfd_add_devices(bd71837->dev, PLATFORM_DEVID_AUTO,
169 bd71837_mfd_cells,
170 ARRAY_SIZE(bd71837_mfd_cells), NULL, 0,
171 regmap_irq_get_domain(bd71837->irq_data));
172 if (ret)
173 dev_err(&i2c->dev, "Failed to create subdevices\n");
174
175 return ret;
176 }
177
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
^ permalink raw reply
* Re: [PATCH v11 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC
From: Matti Vaittinen @ 2018-08-03 11:05 UTC (permalink / raw)
Cc: kbuild-all, lee.jones, robh+dt, mark.rutland, eballetbo,
linus.walleij, mazziesaccount, dmitry.torokhov, linux-clk,
devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <201808031831.TJYSQ80i%fengguang.wu@intel.com>
On Fri, Aug 03, 2018 at 06:10:21PM +0800, kbuild test robot wrote:
> smatch warnings:
> drivers/mfd/rohm-bd718x7.c:163 bd71837_i2c_probe() warn: unsigned 'button.irq' is never less than zero.
>
> 160 button.irq = regmap_irq_get_virq(bd71837->irq_data,
> 161 BD71837_INT_PWRBTN_S);
> 162
> > 163 if (button.irq < 0) {
> 164 dev_err(&i2c->dev, "Failed to get the IRQ\n");
> 165 return button.irq;
> 166 }
Comparing unsiged to smaller-than-zero. These tools are handy! I'll fix
the errno check and send v12 in a minute... (or a bit more - but soonish
in any case =])
Br,
Matti Vaittinen
^ permalink raw reply
* [PATCH v12 0/2] mfd/regulator/clk/input: bd71837: ROHM BD71837 PMIC driver
From: Matti Vaittinen @ 2018-08-03 11:07 UTC (permalink / raw)
To: lee.jones, robh+dt, mark.rutland, eballetbo, linus.walleij,
mazziesaccount, dmitry.torokhov
Cc: linux-clk, devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
Patch series adding support for ROHM BD71837 PMIC.
BD71837 is a programmable Power Management IC for powering single-core,
dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is optimized for
low BOM cost and compact solution footprint. It integrates 8 buck
regulators and 7 LDOs to provide all the power rails required by the
SoC and the commonly used peripherals.
This is reduced set of patches containing only the MFD and devicetree
bindings. This enables alrady applied regulator part and power button
support using gpio-keys. Clock and reset support will be sent as separate
set of patches.
Changelog v12
- fix return value check for regmap_irq_get_virq spotted by build bot.
Changelog v11
More fixes based on comments from Lee Jones
- styling issues/spelling errors.
- drop i2c_client struct from driver data.
- add chip revision validation.
Changelog v10
Fixes based on comments from Lee Jones
- Drop the platform data.
- Drop the regmap wrapper functions and use regmap directly.
- Rename files with rohm-prefix.
- Replace goto from probe by in-place returns.
- Drop unnecessary i2c_id table.
- Change gpio_keys_button array to simple struct.
- Fix return value checks for regmap functions.
- Various styling/spelling fixes.
- Replace foo-bar with something more meaningfull in DT example
Changelog v9
Fixes initiated by feedback from Enric Balletbo Serra, Lee and Dmitry.
- Simplified control flow for probe
- Removed accidentally left squash commit message
- Some comma presence toggling after last member in an array =)
- Styling of multi line comments.
Changelog v8
- Dropped clk-bd71837 from series (will send later)
- Dropped bd718xx-pwrkey driver and used gpio_keys instead.
- Added power-button short/long press duration configuratio to MFD
- Cleaned MFD driver according to comments from Enric Balletbo Serra.
(used devm, removed unnecessary header inclusions, removed redundant
assignment, styling issues, allow building MFD part as module, fixed
license mismatch).
Changelog v7
- patch 1: Cleaned MFD probe since MFD no longer directly reads DT
properties.
- patch 1/4: Moved power-key related definitions from powerkey patch (4)
to MFD patch (1) so that powerkey can be applied independently
- Patch 2 is unchanged.
- patch 3: Added missing allocation check back to clk probe
Changelog v6
- Added power-key input driver
Based on feedback from Rob Herring and Stephen Boyd
- Added link to datasheet
- Removed interrupt-controller from DT and fixed binding document
- clk styling fixes
- remove clkdev usage
- add clk bindings to MFD documentation
- removed clk binding document
Changelog v5
- dropped regulator patches which are already applied to Mark's tree
Based on feedback from Rob Herring and Stephen Boyd
- mfd bindings: explain why this can be interrupt-controller
- mfd bindings: describe interrupts better
- mfd bindings: require one cell interrupt specifier
- mfd bindings: use generic node names in example
- mfd driver: ack masked interrupt once at init
- clk bindings: use generic node names in example
- clk driver: use devm
- clk driver: use of_clk_add_hw_provider
- clk driver: change severity of print and how prints are emitted at
probe error path.
- clk driver: dropped forward declared functions
- clk configs: drop unnecessary dependencies
- clk driver: other styling issues
- mfd/clk DT: drop clk node.
Changelog v4
- remove mutex from regulator state check as core prevents simultaneous
accesses
- allow voltage change for bucks 1 to 4 when regulator is enabled
- fix indentiation problems
- properly correct SPDX comments
Changelog v3
- kill unused variable
- kill unused definitions
- use REGMAP_IRQ_REG
Changelog v2
Based on feedback from Mark Brown
- Squashed code and buildfile changes to same patch
- Fixed some styling issues
- Changed SPDX comments to CPP style
- Error out if voltage is changed when regulator is enabled instead of
Disabling the regulator for duration of change
- Use devm_regulator_register
- Remove compatible usage from regulators - use parent dev for config
- Add a note about using regulator-boot-on for BUCK6 and 7
- fixed warnings from kbuild test robot
patch 1:
MFD driver and definitions bringing interrupt support and
enabling clk, regulator and input subsystems.
patch 2:
MFD driver DT bindings
This patch series is based on for-mfd-next
---
Matti Vaittinen (2):
mfd: bd71837: mfd driver for ROHM BD71837 PMIC
mfd: bd71837: Devicetree bindings for ROHM BD71837 PMIC
.../devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 62 ++++
drivers/mfd/Kconfig | 13 +
drivers/mfd/Makefile | 1 +
drivers/mfd/rohm-bd718x7.c | 211 +++++++++++++
include/linux/mfd/rohm-bd718x7.h | 332 +++++++++++++++++++++
5 files changed, 619 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
create mode 100644 drivers/mfd/rohm-bd718x7.c
create mode 100644 include/linux/mfd/rohm-bd718x7.h
--
2.14.3
^ permalink raw reply
* [PATCH v12 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC
From: Matti Vaittinen @ 2018-08-03 11:08 UTC (permalink / raw)
To: lee.jones, robh+dt, mark.rutland, eballetbo, linus.walleij,
mazziesaccount, dmitry.torokhov
Cc: linux-clk, devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <cover.1533292711.git.matti.vaittinen@fi.rohmeurope.com>
ROHM BD71837 PMIC MFD driver providing interrupts and support
for three subsystems:
- clk
- Regulators
- input/power-key
Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
---
drivers/mfd/Kconfig | 13 ++
drivers/mfd/Makefile | 1 +
drivers/mfd/rohm-bd718x7.c | 211 +++++++++++++++++++++++++
include/linux/mfd/rohm-bd718x7.h | 332 +++++++++++++++++++++++++++++++++++++++
4 files changed, 557 insertions(+)
create mode 100644 drivers/mfd/rohm-bd718x7.c
create mode 100644 include/linux/mfd/rohm-bd718x7.h
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index f3fa516011ec..11841f4b7b2b 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -1817,6 +1817,19 @@ config MFD_STW481X
in various ST Microelectronics and ST-Ericsson embedded
Nomadik series.
+config MFD_ROHM_BD718XX
+ tristate "ROHM BD71837 Power Management IC"
+ depends on I2C=y
+ depends on OF
+ select REGMAP_I2C
+ select REGMAP_IRQ
+ select MFD_CORE
+ help
+ Select this option to get support for the ROHM BD71837
+ Power Management ICs. BD71837 is designed to power processors like
+ NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
+ and emergency shut down as well as 32,768KHz clock output.
+
config MFD_STM32_LPTIMER
tristate "Support for STM32 Low-Power Timer"
depends on (ARCH_STM32 && OF) || COMPILE_TEST
diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
index 2852a6042ecf..5856a9489cbd 100644
--- a/drivers/mfd/Makefile
+++ b/drivers/mfd/Makefile
@@ -239,4 +239,5 @@ obj-$(CONFIG_MFD_STM32_TIMERS) += stm32-timers.o
obj-$(CONFIG_MFD_MXS_LRADC) += mxs-lradc.o
obj-$(CONFIG_MFD_SC27XX_PMIC) += sprd-sc27xx-spi.o
obj-$(CONFIG_RAVE_SP_CORE) += rave-sp.o
+obj-$(CONFIG_MFD_ROHM_BD718XX) += rohm-bd718x7.o
diff --git a/drivers/mfd/rohm-bd718x7.c b/drivers/mfd/rohm-bd718x7.c
new file mode 100644
index 000000000000..75c8ec659547
--- /dev/null
+++ b/drivers/mfd/rohm-bd718x7.c
@@ -0,0 +1,211 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+//
+// Copyright (C) 2018 ROHM Semiconductors
+//
+// ROHM BD71837MWV PMIC driver
+//
+// Datasheet available from
+// https://www.rohm.com/datasheet/BD71837MWV/bd71837mwv-e
+
+#include <linux/i2c.h>
+#include <linux/input.h>
+#include <linux/interrupt.h>
+#include <linux/mfd/rohm-bd718x7.h>
+#include <linux/mfd/core.h>
+#include <linux/module.h>
+#include <linux/regmap.h>
+
+/*
+ * gpio_keys.h requires definiton of bool. It is brought in
+ * by above includes. Keep this as last until gpio_keys.h gets fixed.
+ */
+#include <linux/gpio_keys.h>
+
+static const u8 supported_revisions[] = { 0xA2 /* BD71837 */ };
+
+static struct gpio_keys_button button = {
+ .code = KEY_POWER,
+ .gpio = -1,
+ .type = EV_KEY,
+};
+
+static struct gpio_keys_platform_data bd718xx_powerkey_data = {
+ .buttons = &button,
+ .nbuttons = 1,
+ .name = "bd718xx-pwrkey",
+};
+
+static struct mfd_cell bd71837_mfd_cells[] = {
+ {
+ .name = "gpio-keys",
+ .platform_data = &bd718xx_powerkey_data,
+ .pdata_size = sizeof(bd718xx_powerkey_data),
+ },
+ { .name = "bd71837-clk", },
+ { .name = "bd71837-pmic", },
+};
+
+static const struct regmap_irq bd71837_irqs[] = {
+ REGMAP_IRQ_REG(BD71837_INT_SWRST, 0, BD71837_INT_SWRST_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_PWRBTN_S, 0, BD71837_INT_PWRBTN_S_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_PWRBTN_L, 0, BD71837_INT_PWRBTN_L_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_PWRBTN, 0, BD71837_INT_PWRBTN_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_WDOG, 0, BD71837_INT_WDOG_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_ON_REQ, 0, BD71837_INT_ON_REQ_MASK),
+ REGMAP_IRQ_REG(BD71837_INT_STBY_REQ, 0, BD71837_INT_STBY_REQ_MASK),
+};
+
+static struct regmap_irq_chip bd71837_irq_chip = {
+ .name = "bd71837-irq",
+ .irqs = bd71837_irqs,
+ .num_irqs = ARRAY_SIZE(bd71837_irqs),
+ .num_regs = 1,
+ .irq_reg_stride = 1,
+ .status_base = BD71837_REG_IRQ,
+ .mask_base = BD71837_REG_MIRQ,
+ .ack_base = BD71837_REG_IRQ,
+ .init_ack_masked = true,
+ .mask_invert = false,
+};
+
+static const struct regmap_range pmic_status_range = {
+ .range_min = BD71837_REG_IRQ,
+ .range_max = BD71837_REG_POW_STATE,
+};
+
+static const struct regmap_access_table volatile_regs = {
+ .yes_ranges = &pmic_status_range,
+ .n_yes_ranges = 1,
+};
+
+static const struct regmap_config bd71837_regmap_config = {
+ .reg_bits = 8,
+ .val_bits = 8,
+ .volatile_table = &volatile_regs,
+ .max_register = BD71837_MAX_REGISTER - 1,
+ .cache_type = REGCACHE_RBTREE,
+};
+
+static int bd71837_i2c_probe(struct i2c_client *i2c,
+ const struct i2c_device_id *id)
+{
+ struct bd71837 *bd71837;
+ int ret, i;
+ unsigned int val;
+
+ bd71837 = devm_kzalloc(&i2c->dev, sizeof(struct bd71837), GFP_KERNEL);
+
+ if (!bd71837)
+ return -ENOMEM;
+
+ bd71837->chip_irq = i2c->irq;
+
+ if (!bd71837->chip_irq) {
+ dev_err(&i2c->dev, "No IRQ configured\n");
+ return -EINVAL;
+ }
+
+ bd71837->dev = &i2c->dev;
+ dev_set_drvdata(&i2c->dev, bd71837);
+
+ bd71837->regmap = devm_regmap_init_i2c(i2c, &bd71837_regmap_config);
+ if (IS_ERR(bd71837->regmap)) {
+ dev_err(&i2c->dev, "regmap initialization failed\n");
+ return PTR_ERR(bd71837->regmap);
+ }
+
+ ret = regmap_read(bd71837->regmap, BD71837_REG_REV, &val);
+ if (ret) {
+ dev_err(&i2c->dev, "Read BD71837_REG_DEVICE failed\n");
+ return ret;
+ }
+ for (i = 0; i < ARRAY_SIZE(supported_revisions); i++)
+ if (supported_revisions[i] == val)
+ break;
+
+ if (i == ARRAY_SIZE(supported_revisions)) {
+ dev_err(&i2c->dev, "Unsupported chip revision\n");
+ return -ENODEV;
+ }
+
+ ret = devm_regmap_add_irq_chip(&i2c->dev, bd71837->regmap,
+ bd71837->chip_irq, IRQF_ONESHOT, 0,
+ &bd71837_irq_chip, &bd71837->irq_data);
+ if (ret) {
+ dev_err(&i2c->dev, "Failed to add irq_chip\n");
+ return ret;
+ }
+
+ /* Configure short press to 10 milliseconds */
+ ret = regmap_update_bits(bd71837->regmap,
+ BD71837_REG_PWRONCONFIG0,
+ BD718XX_PWRBTN_PRESS_DURATION_MASK,
+ BD718XX_PWRBTN_SHORT_PRESS_10MS);
+ if (ret) {
+ dev_err(&i2c->dev,
+ "Failed to configure button short press timeout\n");
+ return ret;
+ }
+
+ /* Configure long press to 10 seconds */
+ ret = regmap_update_bits(bd71837->regmap,
+ BD71837_REG_PWRONCONFIG1,
+ BD718XX_PWRBTN_PRESS_DURATION_MASK,
+ BD718XX_PWRBTN_LONG_PRESS_10S);
+
+ if (ret) {
+ dev_err(&i2c->dev,
+ "Failed to configure button long press timeout\n");
+ return ret;
+ }
+
+ ret = regmap_irq_get_virq(bd71837->irq_data, BD71837_INT_PWRBTN_S);
+
+ if (ret < 0) {
+ dev_err(&i2c->dev, "Failed to get the IRQ\n");
+ return ret;
+ }
+
+ button.irq = ret;
+
+ ret = devm_mfd_add_devices(bd71837->dev, PLATFORM_DEVID_AUTO,
+ bd71837_mfd_cells,
+ ARRAY_SIZE(bd71837_mfd_cells), NULL, 0,
+ regmap_irq_get_domain(bd71837->irq_data));
+ if (ret)
+ dev_err(&i2c->dev, "Failed to create subdevices\n");
+
+ return ret;
+}
+
+static const struct of_device_id bd71837_of_match[] = {
+ { .compatible = "rohm,bd71837", },
+ { }
+};
+MODULE_DEVICE_TABLE(of, bd71837_of_match);
+
+static struct i2c_driver bd71837_i2c_driver = {
+ .driver = {
+ .name = "rohm-bd718x7",
+ .of_match_table = bd71837_of_match,
+ },
+ .probe = bd71837_i2c_probe,
+};
+
+static int __init bd71837_i2c_init(void)
+{
+ return i2c_add_driver(&bd71837_i2c_driver);
+}
+
+/* Initialise early so consumer devices can complete system boot */
+subsys_initcall(bd71837_i2c_init);
+
+static void __exit bd71837_i2c_exit(void)
+{
+ i2c_del_driver(&bd71837_i2c_driver);
+}
+module_exit(bd71837_i2c_exit);
+
+MODULE_AUTHOR("Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>");
+MODULE_DESCRIPTION("ROHM BD71837 Power Management IC driver");
+MODULE_LICENSE("GPL");
diff --git a/include/linux/mfd/rohm-bd718x7.h b/include/linux/mfd/rohm-bd718x7.h
new file mode 100644
index 000000000000..a528747f8aed
--- /dev/null
+++ b/include/linux/mfd/rohm-bd718x7.h
@@ -0,0 +1,332 @@
+/* SPDX-License-Identifier: GPL-2.0-or-later */
+/* Copyright (C) 2018 ROHM Semiconductors */
+
+#ifndef __LINUX_MFD_BD71837_H__
+#define __LINUX_MFD_BD71837_H__
+
+#include <linux/regmap.h>
+
+enum {
+ BD71837_BUCK1 = 0,
+ BD71837_BUCK2,
+ BD71837_BUCK3,
+ BD71837_BUCK4,
+ BD71837_BUCK5,
+ BD71837_BUCK6,
+ BD71837_BUCK7,
+ BD71837_BUCK8,
+ BD71837_LDO1,
+ BD71837_LDO2,
+ BD71837_LDO3,
+ BD71837_LDO4,
+ BD71837_LDO5,
+ BD71837_LDO6,
+ BD71837_LDO7,
+ BD71837_REGULATOR_CNT,
+};
+
+#define BD71837_BUCK1_VOLTAGE_NUM 0x40
+#define BD71837_BUCK2_VOLTAGE_NUM 0x40
+#define BD71837_BUCK3_VOLTAGE_NUM 0x40
+#define BD71837_BUCK4_VOLTAGE_NUM 0x40
+
+#define BD71837_BUCK5_VOLTAGE_NUM 0x08
+#define BD71837_BUCK6_VOLTAGE_NUM 0x04
+#define BD71837_BUCK7_VOLTAGE_NUM 0x08
+#define BD71837_BUCK8_VOLTAGE_NUM 0x40
+
+#define BD71837_LDO1_VOLTAGE_NUM 0x04
+#define BD71837_LDO2_VOLTAGE_NUM 0x02
+#define BD71837_LDO3_VOLTAGE_NUM 0x10
+#define BD71837_LDO4_VOLTAGE_NUM 0x10
+#define BD71837_LDO5_VOLTAGE_NUM 0x10
+#define BD71837_LDO6_VOLTAGE_NUM 0x10
+#define BD71837_LDO7_VOLTAGE_NUM 0x10
+
+enum {
+ BD71837_REG_REV = 0x00,
+ BD71837_REG_SWRESET = 0x01,
+ BD71837_REG_I2C_DEV = 0x02,
+ BD71837_REG_PWRCTRL0 = 0x03,
+ BD71837_REG_PWRCTRL1 = 0x04,
+ BD71837_REG_BUCK1_CTRL = 0x05,
+ BD71837_REG_BUCK2_CTRL = 0x06,
+ BD71837_REG_BUCK3_CTRL = 0x07,
+ BD71837_REG_BUCK4_CTRL = 0x08,
+ BD71837_REG_BUCK5_CTRL = 0x09,
+ BD71837_REG_BUCK6_CTRL = 0x0A,
+ BD71837_REG_BUCK7_CTRL = 0x0B,
+ BD71837_REG_BUCK8_CTRL = 0x0C,
+ BD71837_REG_BUCK1_VOLT_RUN = 0x0D,
+ BD71837_REG_BUCK1_VOLT_IDLE = 0x0E,
+ BD71837_REG_BUCK1_VOLT_SUSP = 0x0F,
+ BD71837_REG_BUCK2_VOLT_RUN = 0x10,
+ BD71837_REG_BUCK2_VOLT_IDLE = 0x11,
+ BD71837_REG_BUCK3_VOLT_RUN = 0x12,
+ BD71837_REG_BUCK4_VOLT_RUN = 0x13,
+ BD71837_REG_BUCK5_VOLT = 0x14,
+ BD71837_REG_BUCK6_VOLT = 0x15,
+ BD71837_REG_BUCK7_VOLT = 0x16,
+ BD71837_REG_BUCK8_VOLT = 0x17,
+ BD71837_REG_LDO1_VOLT = 0x18,
+ BD71837_REG_LDO2_VOLT = 0x19,
+ BD71837_REG_LDO3_VOLT = 0x1A,
+ BD71837_REG_LDO4_VOLT = 0x1B,
+ BD71837_REG_LDO5_VOLT = 0x1C,
+ BD71837_REG_LDO6_VOLT = 0x1D,
+ BD71837_REG_LDO7_VOLT = 0x1E,
+ BD71837_REG_TRANS_COND0 = 0x1F,
+ BD71837_REG_TRANS_COND1 = 0x20,
+ BD71837_REG_VRFAULTEN = 0x21,
+ BD71837_REG_MVRFLTMASK0 = 0x22,
+ BD71837_REG_MVRFLTMASK1 = 0x23,
+ BD71837_REG_MVRFLTMASK2 = 0x24,
+ BD71837_REG_RCVCFG = 0x25,
+ BD71837_REG_RCVNUM = 0x26,
+ BD71837_REG_PWRONCONFIG0 = 0x27,
+ BD71837_REG_PWRONCONFIG1 = 0x28,
+ BD71837_REG_RESETSRC = 0x29,
+ BD71837_REG_MIRQ = 0x2A,
+ BD71837_REG_IRQ = 0x2B,
+ BD71837_REG_IN_MON = 0x2C,
+ BD71837_REG_POW_STATE = 0x2D,
+ BD71837_REG_OUT32K = 0x2E,
+ BD71837_REG_REGLOCK = 0x2F,
+ BD71837_REG_OTPVER = 0xFF,
+ BD71837_MAX_REGISTER = 0x100,
+};
+
+#define REGLOCK_PWRSEQ 0x1
+#define REGLOCK_VREG 0x10
+
+/* Generic BUCK control masks */
+#define BD71837_BUCK_SEL 0x02
+#define BD71837_BUCK_EN 0x01
+#define BD71837_BUCK_RUN_ON 0x04
+
+/* Generic LDO masks */
+#define BD71837_LDO_SEL 0x80
+#define BD71837_LDO_EN 0x40
+
+/* BD71837 BUCK ramp rate CTRL reg bits */
+#define BUCK_RAMPRATE_MASK 0xC0
+#define BUCK_RAMPRATE_10P00MV 0x0
+#define BUCK_RAMPRATE_5P00MV 0x1
+#define BUCK_RAMPRATE_2P50MV 0x2
+#define BUCK_RAMPRATE_1P25MV 0x3
+
+/* BD71837_REG_BUCK1_VOLT_RUN bits */
+#define BUCK1_RUN_MASK 0x3F
+#define BUCK1_RUN_DEFAULT 0x14
+
+/* BD71837_REG_BUCK1_VOLT_SUSP bits */
+#define BUCK1_SUSP_MASK 0x3F
+#define BUCK1_SUSP_DEFAULT 0x14
+
+/* BD71837_REG_BUCK1_VOLT_IDLE bits */
+#define BUCK1_IDLE_MASK 0x3F
+#define BUCK1_IDLE_DEFAULT 0x14
+
+/* BD71837_REG_BUCK2_VOLT_RUN bits */
+#define BUCK2_RUN_MASK 0x3F
+#define BUCK2_RUN_DEFAULT 0x1E
+
+/* BD71837_REG_BUCK2_VOLT_IDLE bits */
+#define BUCK2_IDLE_MASK 0x3F
+#define BUCK2_IDLE_DEFAULT 0x14
+
+/* BD71837_REG_BUCK3_VOLT_RUN bits */
+#define BUCK3_RUN_MASK 0x3F
+#define BUCK3_RUN_DEFAULT 0x1E
+
+/* BD71837_REG_BUCK4_VOLT_RUN bits */
+#define BUCK4_RUN_MASK 0x3F
+#define BUCK4_RUN_DEFAULT 0x1E
+
+/* BD71837_REG_BUCK5_VOLT bits */
+#define BUCK5_MASK 0x07
+#define BUCK5_DEFAULT 0x02
+
+/* BD71837_REG_BUCK6_VOLT bits */
+#define BUCK6_MASK 0x03
+#define BUCK6_DEFAULT 0x03
+
+/* BD71837_REG_BUCK7_VOLT bits */
+#define BUCK7_MASK 0x07
+#define BUCK7_DEFAULT 0x03
+
+/* BD71837_REG_BUCK8_VOLT bits */
+#define BUCK8_MASK 0x3F
+#define BUCK8_DEFAULT 0x1E
+
+/* BD71837_REG_IRQ bits */
+#define IRQ_SWRST 0x40
+#define IRQ_PWRON_S 0x20
+#define IRQ_PWRON_L 0x10
+#define IRQ_PWRON 0x08
+#define IRQ_WDOG 0x04
+#define IRQ_ON_REQ 0x02
+#define IRQ_STBY_REQ 0x01
+
+/* BD71837_REG_OUT32K bits */
+#define BD71837_OUT32K_EN 0x01
+
+/* BD71837 gated clock rate */
+#define BD71837_CLK_RATE 32768
+
+/* ROHM BD71837 irqs */
+enum {
+ BD71837_INT_STBY_REQ,
+ BD71837_INT_ON_REQ,
+ BD71837_INT_WDOG,
+ BD71837_INT_PWRBTN,
+ BD71837_INT_PWRBTN_L,
+ BD71837_INT_PWRBTN_S,
+ BD71837_INT_SWRST
+};
+
+/* ROHM BD71837 interrupt masks */
+#define BD71837_INT_SWRST_MASK 0x40
+#define BD71837_INT_PWRBTN_S_MASK 0x20
+#define BD71837_INT_PWRBTN_L_MASK 0x10
+#define BD71837_INT_PWRBTN_MASK 0x8
+#define BD71837_INT_WDOG_MASK 0x4
+#define BD71837_INT_ON_REQ_MASK 0x2
+#define BD71837_INT_STBY_REQ_MASK 0x1
+
+/* BD71837_REG_LDO1_VOLT bits */
+#define LDO1_MASK 0x03
+
+/* BD71837_REG_LDO1_VOLT bits */
+#define LDO2_MASK 0x20
+
+/* BD71837_REG_LDO3_VOLT bits */
+#define LDO3_MASK 0x0F
+
+/* BD71837_REG_LDO4_VOLT bits */
+#define LDO4_MASK 0x0F
+
+/* BD71837_REG_LDO5_VOLT bits */
+#define LDO5_MASK 0x0F
+
+/* BD71837_REG_LDO6_VOLT bits */
+#define LDO6_MASK 0x0F
+
+/* BD71837_REG_LDO7_VOLT bits */
+#define LDO7_MASK 0x0F
+
+/* Register write induced reset settings */
+
+/*
+ * Even though the bit zero is not SWRESET type we still want to write zero
+ * to it when changing type. Bit zero is 'SWRESET' trigger bit and if we
+ * write 1 to it we will trigger the action. So always write 0 to it when
+ * changning SWRESET action - no matter what we read from it.
+ */
+#define BD71837_SWRESET_TYPE_MASK 7
+#define BD71837_SWRESET_TYPE_DISABLED 0
+#define BD71837_SWRESET_TYPE_COLD 4
+#define BD71837_SWRESET_TYPE_WARM 6
+
+#define BD71837_SWRESET_RESET_MASK 1
+#define BD71837_SWRESET_RESET 1
+
+/* Poweroff state transition conditions */
+
+#define BD718XX_ON_REQ_POWEROFF_MASK 1
+#define BD718XX_SWRESET_POWEROFF_MASK 2
+#define BD718XX_WDOG_POWEROFF_MASK 4
+#define BD718XX_KEY_L_POWEROFF_MASK 8
+
+#define BD718XX_POWOFF_TO_SNVS 0
+#define BD718XX_POWOFF_TO_RDY 0xF
+
+#define BD718XX_POWOFF_TIME_MASK 0xF0
+enum {
+ BD718XX_POWOFF_TIME_5MS = 0,
+ BD718XX_POWOFF_TIME_10MS,
+ BD718XX_POWOFF_TIME_15MS,
+ BD718XX_POWOFF_TIME_20MS,
+ BD718XX_POWOFF_TIME_25MS,
+ BD718XX_POWOFF_TIME_30MS,
+ BD718XX_POWOFF_TIME_35MS,
+ BD718XX_POWOFF_TIME_40MS,
+ BD718XX_POWOFF_TIME_45MS,
+ BD718XX_POWOFF_TIME_50MS,
+ BD718XX_POWOFF_TIME_75MS,
+ BD718XX_POWOFF_TIME_100MS,
+ BD718XX_POWOFF_TIME_250MS,
+ BD718XX_POWOFF_TIME_500MS,
+ BD718XX_POWOFF_TIME_750MS,
+ BD718XX_POWOFF_TIME_1500MS
+};
+
+/* Poweron sequence state transition conditions */
+#define BD718XX_RDY_TO_SNVS_MASK 0xF
+#define BD718XX_SNVS_TO_RUN_MASK 0xF0
+
+#define BD718XX_PWR_TRIG_KEY_L 1
+#define BD718XX_PWR_TRIG_KEY_S 2
+#define BD718XX_PWR_TRIG_PMIC_ON 4
+#define BD718XX_PWR_TRIG_VSYS_UVLO 8
+#define BD718XX_RDY_TO_SNVS_SIFT 0
+#define BD718XX_SNVS_TO_RUN_SIFT 4
+
+#define BD718XX_PWRBTN_PRESS_DURATION_MASK 0xF
+
+/* Timeout value for detecting short press */
+enum {
+ BD718XX_PWRBTN_SHORT_PRESS_10MS = 0,
+ BD718XX_PWRBTN_SHORT_PRESS_500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_1000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_1500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_2000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_2500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_3000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_3500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_4000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_4500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_5000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_5500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_6000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_6500MS,
+ BD718XX_PWRBTN_SHORT_PRESS_7000MS,
+ BD718XX_PWRBTN_SHORT_PRESS_7500MS
+};
+
+/* Timeout value for detecting LONG press */
+enum {
+ BD718XX_PWRBTN_LONG_PRESS_10MS = 0,
+ BD718XX_PWRBTN_LONG_PRESS_1S,
+ BD718XX_PWRBTN_LONG_PRESS_2S,
+ BD718XX_PWRBTN_LONG_PRESS_3S,
+ BD718XX_PWRBTN_LONG_PRESS_4S,
+ BD718XX_PWRBTN_LONG_PRESS_5S,
+ BD718XX_PWRBTN_LONG_PRESS_6S,
+ BD718XX_PWRBTN_LONG_PRESS_7S,
+ BD718XX_PWRBTN_LONG_PRESS_8S,
+ BD718XX_PWRBTN_LONG_PRESS_9S,
+ BD718XX_PWRBTN_LONG_PRESS_10S,
+ BD718XX_PWRBTN_LONG_PRESS_11S,
+ BD718XX_PWRBTN_LONG_PRESS_12S,
+ BD718XX_PWRBTN_LONG_PRESS_13S,
+ BD718XX_PWRBTN_LONG_PRESS_14S,
+ BD718XX_PWRBTN_LONG_PRESS_15S
+};
+
+struct bd71837_pmic;
+struct bd71837_clk;
+
+struct bd71837 {
+ struct device *dev;
+ struct regmap *regmap;
+ unsigned long int id;
+
+ int chip_irq;
+ struct regmap_irq_chip_data *irq_data;
+
+ struct bd71837_pmic *pmic;
+ struct bd71837_clk *clk;
+};
+
+#endif /* __LINUX_MFD_BD71837_H__ */
--
2.14.3
^ permalink raw reply related
* [PATCH v12 2/2] mfd: bd71837: Devicetree bindings for ROHM BD71837 PMIC
From: Matti Vaittinen @ 2018-08-03 11:09 UTC (permalink / raw)
To: lee.jones, robh+dt, mark.rutland, eballetbo, linus.walleij,
mazziesaccount, dmitry.torokhov
Cc: linux-clk, devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <cover.1533292711.git.matti.vaittinen@fi.rohmeurope.com>
Document devicetree bindings for ROHM BD71837 PMIC MFD.
Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
---
.../devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 62 ++++++++++++++++++++++
1 file changed, 62 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
new file mode 100644
index 000000000000..3ca56fdb5ffe
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
@@ -0,0 +1,62 @@
+* ROHM BD71837 Power Management Integrated Circuit bindings
+
+BD71837MWV is a programmable Power Management IC for powering single-core,
+dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is optimized for
+low BOM cost and compact solution footprint. It integrates 8 Buck
+egulators and 7 LDOs to provide all the power rails required by the SoC and
+the commonly used peripherals.
+
+Datasheet for PMIC is available at:
+https://www.rohm.com/datasheet/BD71837MWV/bd71837mwv-e
+
+Required properties:
+ - compatible : Should be "rohm,bd71837".
+ - reg : I2C slave address.
+ - interrupt-parent : Phandle to the parent interrupt controller.
+ - interrupts : The interrupt line the device is connected to.
+ - clocks : The parent clock connected to PMIC. If this is missing
+ 32768 KHz clock is assumed.
+ - #clock-cells : Should be 0.
+ - regulators: : List of child nodes that specify the regulators.
+ Please see ../regulator/rohm,bd71837-regulator.txt
+
+Optional properties:
+- clock-output-names : Should contain name for output clock.
+
+Example:
+
+ /* external oscillator node */
+ osc: oscillator {
+ compatible = "fixed-clock";
+ #clock-cells = <1>;
+ clock-frequency = <32768>;
+ clock-output-names = "osc";
+ };
+
+ pmic: pmic@4b {
+ compatible = "rohm,bd71837";
+ reg = <0x4b>;
+ interrupt-parent = <&gpio1>;
+ interrupts = <29 GPIO_ACTIVE_LOW>;
+ interrupt-names = "irq";
+ #clock-cells = <0>;
+ clocks = <&osc 0>;
+ clock-output-names = "bd71837-32k-out";
+
+ regulators {
+ buck1: BUCK1 {
+ regulator-name = "buck1";
+ regulator-min-microvolt = <700000>;
+ regulator-max-microvolt = <1300000>;
+ regulator-boot-on;
+ regulator-ramp-delay = <1250>;
+ };
+ };
+ };
+
+ /* Clock consumer node */
+ rtc@0 {
+ compatible = "company,my-rtc";
+ clock-names = "my-clock";
+ clocks = <&pmic>;
+ };
--
2.14.3
^ permalink raw reply related
* Re: [PATCH v12 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC
From: Matti Vaittinen @ 2018-08-03 11:12 UTC (permalink / raw)
To: lee.jones, robh+dt, mark.rutland, eballetbo, linus.walleij,
mazziesaccount, dmitry.torokhov
Cc: linux-clk, devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <4f49022ed8e4fa357bf5d213c57ad57752e72aa4.1533292711.git.matti.vaittinen@fi.rohmeurope.com>
On Fri, Aug 03, 2018 at 02:08:14PM +0300, Matti Vaittinen wrote:
> ROHM BD71837 PMIC MFD driver providing interrupts and support
> for three subsystems:
> - clk
> - Regulators
> - input/power-key
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
I maintained Enric's Reviewed-by as only change I did to v12 was:
> + ret = regmap_irq_get_virq(bd71837->irq_data, BD71837_INT_PWRBTN_S);
> +
> + if (ret < 0) {
> + dev_err(&i2c->dev, "Failed to get the IRQ\n");
> + return ret;
> + }
> +
> + button.irq = ret;
instead of v11 which was:
+ button.irq = regmap_irq_get_virq(bd71837->irq_data,
+ BD71837_INT_PWRBTN_S);
+
+ if (button.irq < 0) {
+ dev_err(&i2c->dev, "Failed to get the IRQ\n");
+ return button.irq;
+ }
Br,
Matti Vaittinen
^ permalink raw reply
* Re: [PATCH v12 2/2] mfd: bd71837: Devicetree bindings for ROHM BD71837 PMIC
From: Matti Vaittinen @ 2018-08-03 11:14 UTC (permalink / raw)
To: lee.jones, robh+dt, mark.rutland, eballetbo, linus.walleij,
mazziesaccount, dmitry.torokhov
Cc: linux-clk, devicetree, linux-kernel, sboyd, broonie, linux-input,
mikko.mutanen, heikki.haikola
In-Reply-To: <d053f54e5ce726ffaa95fbd9c20962a49dd1ee07.1533292711.git.matti.vaittinen@fi.rohmeurope.com>
On Fri, Aug 03, 2018 at 02:09:12PM +0300, Matti Vaittinen wrote:
> Document devicetree bindings for ROHM BD71837 PMIC MFD.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> ---
I kept the Reviewed-by and Acked-by as this patch is unchanged once
again... Sorry for the spam.
^ permalink raw reply
* Re: [PATCH 2/2] HID: redragon Add additional verification to rdesc modification quirk
From: Robert Munteanu @ 2018-08-03 13:21 UTC (permalink / raw)
To: John S Gruber, Jiri Kosina, linux-input, benjamin.tissoires,
dmitry.torokhov, linux-kernel
In-Reply-To: <CAPotdmQh_sWqPmiQ=_+fJ27AT7GA5hcne=wsXcmKhNnUpUs3wQ@mail.gmail.com>
On Sat, 2018-07-28 at 15:53 -0400, John S Gruber wrote:
> There are many devices using the vendor_id 0c45 and device_id of 760b
> combination. Also the two bytes 0x81 0x00 aren't rare for a report
> description. For these reasons the report description being altered
> by the quirk should be verified more completely
>
> If I'm understanding this correctly, I believe for an array field the
> report_size should be greater or equal to
> ceil(log2(usage_maximum - usage_minimum + 1)). That's 3 bits for
> these 8
> shift keys, 0xe0-0xe7. Therefore the incorrect report description
> can't
> be valid for any device.
>
> Check the actual count of the rdesc and compare the entire field
> description to reduce the chance of patching the wrong thing by
> inadvertence.
>
> Signed-off-by: John S Gruber <JohnSGruber@gmail.com>
I tested this on 4.17.11 with 85455dd906d5 and cbe7e3ad0eab from Jiri's
for-4.19/upstream tree and it works just fine.
Feel free to add
Acked-By: Robert Munteanu <rombert@apache.org>
Thanks for looking into this.
Robert
^ permalink raw reply
* Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.
From: Ravi Chandra Sadineni @ 2018-08-03 15:50 UTC (permalink / raw)
To: m.szyprowski
Cc: Ravi Chandra Sadineni, Dmitry Torokhov, Dmitry Torokhov,
Todd Broch, linux-kernel, linux-input, linux-samsung-soc
In-Reply-To: <20180803072628eucas1p26abe0cb121b974401759502f8807bb96~HTx4BGQjl1119311193eucas1p2U@eucas1p2.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 55538 bytes --]
Hi Marek,
Can you please give me little more context ? Snow is still on 3.8.11. This
patch is not backported to 3.8.11. Are you trying to flash a different
kernel on snow?
Thanks,
Ravi
On Fri, Aug 3, 2018 at 12:26 AM Marek Szyprowski <m.szyprowski@samsung.com>
wrote:
> Hi All,
>
> On 2018-06-06 00:44, Ravi Chandra Sadineni wrote:
> > Remove the unnecessary check before calling pm_wakeup_event. If the
> > device is not wake enabled, this call is no-op anyway.
> >
> > Signed-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org>
>
> This patch breaks suspend/resume on Samsung Exynos5250 Snow Chromebook.
> It looks that it is waiting forever(?) on some cros ec i2c call. With
> no_console_suspend and initcall_debug kernel parameters together with
> playing with magic-sysrq after suspend/resume cycle I've managed to get
> following log:
>
> # rtcwake -s10 -mmem
> rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Aug 3 06:13:42 2018
> [ 38.359219] PM: suspend entry (deep)
> [ 38.362782] PM: Syncing filesystems ... done.
> [ 38.379897] Freezing user space processes ... (elapsed 0.002 seconds)
> done.
> [ 38.382258] OOM killer disabled.
> [ 38.382263] Freezing remaining freezable tasks ... (elapsed 0.001
> seconds) done.
> [ 38.388705] calling input2+ @ 1610, parent: gpio-keys
> [ 38.388847] call input2+ returned 0 after 122 usecs
> [ 38.388985] calling sound+ @ 1610, parent: platform
> [ 38.423739] max98095 7-0011: ASoC: PRE_PMD: LINE Left Out event
> failed: -22
> [ 38.435718] call sound+ returned 0 after 45628 usecs
> [ 38.435746] calling panel+ @ 1610, parent: platform
> [ 38.435754] call panel+ returned 0 after 1 usecs
> [ 38.435768] calling hdmi-audio-codec.4.auto+ @ 1610, parent:
> 14530000.hdmi
> [ 38.435775] call hdmi-audio-codec.4.auto+ returned 0 after 1 usecs
> [ 38.435799] calling backlight+ @ 1610, parent: backlight
> [ 38.436032] call backlight+ returned 0 after 221 usecs
> [ 38.436048] calling backlight+ @ 1610, parent: platform
> [ 38.445536] call backlight+ returned 0 after 9257 usecs
> [ 38.445670] calling mmc2:0001:3+ @ 6, parent: mmc2:0001
> [ 38.445700] call mmc2:0001:3+ returned 0 after 1 usecs
> [ 38.445733] calling mmc2:0001:2+ @ 6, parent: mmc2:0001
> [ 38.445740] call mmc2:0001:2+ returned 0 after 1 usecs
> [ 38.445760] calling mmc2:0001:1+ @ 6, parent: mmc2:0001
> [ 38.445767] call mmc2:0001:1+ returned 0 after 1 usecs
> [ 38.445792] calling mmc2:0001+ @ 6, parent: mmc2
> [ 38.445884] calling snd-soc-dummy+ @ 1610, parent: platform
> [ 38.445892] call snd-soc-dummy+ returned 0 after 1 usecs
> [ 38.445988] calling cpufreq-dt+ @ 1610, parent: platform
> [ 38.445997] call cpufreq-dt+ returned 0 after 1 usecs
> [ 38.446071] calling tps65090-charger+ @ 1610, parent: 104-0048
> [ 38.446079] call tps65090-charger+ returned 0 after 1 usecs
> [ 38.446208] calling mmc1:e624+ @ 78, parent: mmc1
> [ 38.446212] calling tps65090-pmic+ @ 1610, parent: 104-0048
> [ 38.446220] call tps65090-pmic+ returned 0 after 1 usecs
> [ 38.446279] calling input1+ @ 1610, parent:
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller
> [ 38.446289] call input1+ returned 0 after 3 usecs
> [ 38.446305] calling
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+ @ 1610,
> parent: 104-001e
> [ 38.446313] call
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+
> returned 0 after 1 usecs
> [ 38.446327] calling cros-ec-dev.3.auto+ @ 1610, parent: 104-001e
> [ 38.446334] call cros-ec-dev.3.auto+ returned 0 after 1 usecs
> [ 38.446370] calling 104-001e+ @ 1610, parent: i2c-104
> [ 38.448555] call mmc1:e624+ returned 0 after 2283 usecs
> [ 38.450514] calling mmc0:0001+ @ 79, parent: mmc0
> [ 38.457501] call mmc2:0001+ returned 0 after 11425 usecs
> [ 38.463830] wake enabled for irq 150
> [ 38.469426] calling 1-1+ @ 6, parent: usb1
> [ 38.474501] call 104-001e+ returned 0 after 27461 usecs
> [ 38.490008] call 1-1+ returned 0 after 10331 usecs
> [ 38.494988] calling 104-000b+ @ 1610, parent: i2c-104
> [ 38.512028] call mmc0:0001+ returned 0 after 36926 usecs
> [ 38.547373] call 104-000b+ returned 0 after 51146 usecs
> [ 38.670382] calling rtc1+ @ 1610, parent: 101e0000.rtc
> [ 38.675688] call rtc1+ returned 0 after 2 usecs
> [ 38.680296] calling rtc0+ @ 1610, parent: max77686-rtc
> [ 38.717626] call rtc0+ returned 0 after 31302 usecs
> [ 38.722578] calling input0+ @ 1610, parent: 1-0067
> [ 38.727536] call input0+ returned 0 after 3 usecs
> [ 38.732368] calling usb4+ @ 78, parent: xhci-hcd.2.auto
> [ 38.732790] calling usb2+ @ 1614, parent: 12120000.usb
> [ 38.738659] calling usb1+ @ 79, parent: 12110000.usb
> [ 38.743044] calling usb3+ @ 6, parent: xhci-hcd.2.auto
> [ 38.748311] call usb4+ returned 0 after 10186 usecs
> [ 38.753567] call usb3+ returned 0 after 251 usecs
> [ 38.758811] call usb1+ returned 0 after 526 usecs
> [ 38.763006] calling xhci-hcd.2.auto+ @ 6, parent: 12000000.dwc3
> [ 38.773625] call xhci-hcd.2.auto+ returned 0 after 43 usecs
> [ 38.779206] calling 12000000.dwc3+ @ 1610, parent: soc:usb_dwc3
> [ 38.785417] call 12000000.dwc3+ returned 0 after 245 usecs
> [ 38.790917] calling usb_phy_generic.1.auto+ @ 1610, parent: platform
> [ 38.797356] call usb_phy_generic.1.auto+ returned 0 after 1 usecs
> [ 38.803431] calling usb_phy_generic.0.auto+ @ 1610, parent: platform
> [ 38.809966] call usb_phy_generic.0.auto+ returned 0 after 1 usecs
> [ 38.816108] calling Fixed MDIO bus.0+ @ 1610, parent: platform
> [ 38.822083] call Fixed MDIO bus.0+ returned 0 after 1 usecs
> [ 38.827738] calling max77686-clk+ @ 1610, parent: 0-0009
> [ 38.833159] call max77686-clk+ returned 0 after 1 usecs
> [ 38.838478] calling max77686-rtc+ @ 1610, parent: 0-0009
> [ 38.844475] wake enabled for irq 146
> [ 38.848184] call max77686-rtc+ returned 0 after 4181 usecs
> [ 38.853999] calling max77686-pmic+ @ 1610, parent: 0-0009
> [ 38.859554] call max77686-pmic+ returned 0 after 1 usecs
> [ 38.865284] calling exynos-drm+ @ 1610, parent: platform
> [ 38.871024] call usb2+ returned 0 after 114877 usecs
> [ 38.890105] call exynos-drm+ returned 0 after 13780 usecs
> [ 38.894146] calling serial8250+ @ 1610, parent: platform
> [ 38.899515] call serial8250+ returned 0 after 2 usecs
> [ 38.908551] calling alarmtimer+ @ 1610, parent: platform
> [ 38.913057] call alarmtimer+ returned 0 after 536 usecs
> [ 38.917812] calling regulatory.0+ @ 1610, parent: platform
> [ #8.923263] call regulatory.0+ returned 0 after 1 usecs
> [ 38.929144] calling 1-0067+ @ 1610, parent: i2c-1
> [ 38.967236] wake enabled for irq 148
> [ 38.969454] call 1-0067+ returned 0 after 35363 usecs
> [ 38.974510] calling 0-0009+ @ 1610, parent: i2c-0
> [ 38.979274] call 0-0009+ returned 0 after 5 usecs
> [ 38.983989] calling mmc3_pwrseq+ @ 1610, parent: platform
> [ 38.989422] call mmc3_pwrseq+ returned 0 after 1 usecs
> [ 38.994522] calling regulator-usb3+ @ 1610, parent: platform
> [ 39.000271] call regulator-usb3+ returned 0 after 1 usecs
> [ 39.005633] calling i2c-arbitrator+ @ 1610, parent: platform
> [ 39.011381] call i2c-arbitrator+ returned 0 after 1 usecs
> [ 39.016744] calling vbat-fixed-regulator+ @ 1610, parent: platform
> [ 39.023015] call vbat-fixed-regulator+ returned 0 after 1 usecs
> [ 39.028925] calling gpio-keys+ @ 1610, parent: platform
> [ 39.034182] wake enabled for irq 152
> [ 39.037759] wake enabled for irq 153
> [ 39.041292] call gpio-keys+ returned 0 after 6944 usecs
> [ 39.046515] calling opp_table0+ @ 1610, parent: platform
> [ 39.051915] call opp_table0+ returned 0 after 1 usecs
> [ 39.056940] calling 14650000.sysmmu+ @ 1610, parent: soc
> [ 39.062332] call 14650000.sysmmu+ returned 0 after 2 usecs
> [ 39.067818] calling 14640000.sysmmu+ @ 1610, parent: soc
> [ 39.073332] call 14640000.sysmmu+ returned 0 after 174 usecs
> [ 39.078845] calling 13eb0000.sysmmu+ @ 1610, parent: soc
> [ 39.084180] call 13eb0000.sysmmu+ returned 0 after 2 usecs
> [ 39.089690] calling 13ea0000.sysmmu+ @ 1610, parent: soc
> [ 39.095029] call 13ea0000.sysmmu+ returned 0 after 2 usecs
> [ 39.100547] calling 13e90000.sysmmu+ @ 1610, parent: soc
> [ 39.105880] call 13e90000.sysmmu+ returned 0 after 2 usecs
> [ 39.111402] calling 13e80000.sysmmu+ @ 1610, parent: soc
> [ 39.116731] call 13e80000.sysmmu+ returned 0 after 2 usecs
> [ 39.122241] calling 13c50000.sysmmu+ @ 1610, parent: soc
> [ 39.127607] call 13c50000.sysmmu+ returned 0 after 2 usecs
> [ 39.133065] calling 13c40000.sysmmu+ @ 1610, parent: soc
> [ 39.138498] call 13c40000.sysmmu+ returned 0 after 2 usecs
> [ 39.143915] calling 132f0000.sysmmu+ @ 1610, parent: soc
> [ 39.149308] call 132f0000.sysmmu+ returned 0 after 2 usecs
> [ 39.154765] calling 132e0000.sysmmu+ @ 1610, parent: soc
> [ 39.160155] call 132e0000.sysmmu+ returned 0 after 2 usecs
> [ 39.165615] calling 132d0000.sysmmu+ @ 1610, parent: soc
> [ 39.171005] call 132d0000.sysmmu+ returned 0 after 2 usecs
> [ 39.176465] calling 132c0000.sysmmu+ @ 1610, parent: soc
> [ 39.181856] call 132c0000.sysmmu+ returned 0 after 2 usecs
> [ 39.187340] calling 132b0000.sysmmu+ @ 1610, parent: soc
> [ 39.192680] call 132b0000.sysmmu+ returned 0 after 2 usecs
> [ 39.198190] calling 13290000.sysmmu+ @ 1610, parent: soc
> [ 39.203530] call 13290000.sysmmu+ returned 0 after 2 usecs
> [ 39.209091] calling 13280000.sysmmu+ @ 1610, parent: soc
> [ 39.214380] call 13280000.sysmmu+ returned 0 after 2 usecs
> [ 39.219892] calling 132a0000.sysmmu+ @ 1610, parent: soc
> [ 39.225230] call 132a0000.sysmmu+ returned 0 after 2 usecs
> [ 39.230749] calling 13270000.sysmmu+ @ 1610, parent: soc
> [ 39.236080] call 13270000.sysmmu+ returned 0 after 2 usecs
> [ 39.241590] calling 13260000.sysmmu+ @ 1610, parent: soc
> [ 39.246931] call 13260000.sysmmu+ returned 0 after 2 usecs
> [ 39.252440] calling 11f20000.sysmmu+ @ 1610, parent: soc
> [ 39.257806] call 11f20000.sysmmu+ returned 0 after 2 usecs
> [ 39.263265] calling 11d40000.sysmmu+ @ 1610, parent: soc
> [ 39.268655] call 11d40000.sysmmu+ returned 0 after 2 usecs
> [ 39.274115] calling 11210000.sysmmu+ @ 1610, parent: soc
> [ 39.279505] call 11210000.sysmmu+ returned 0 after 2 usecs
> [ 39.284965] calling 11200000.sysmmu+ @ 1610, parent: soc
> [ 39.290355] call 11200000.sysmmu+ returned 0 after 2 usecs
> [ 39.295815] calling 10a60000.sysmmu+ @ 1610, parent: soc
> [ 39.301206] call 10a60000.sysmmu+ returned 0 after 2 usecs
> [ 39.306657] calling soc:video-phy+ @ 1610, parent: soc
> [ 39.311881] call soc:video-phy+ returned 0 after 2 usecs
> [ 39.317158] calling 101b0000.cec+ @ 1610, parent: soc
> [ 39.322296] call 101b0000.cec+ returned 0 after 1 usecs
> [ 39.327511] calling 13e30000.gsc+ @ 1610, parent: soc
> [ 39.332600] call 13e30000.gsc+ returned 0 after 1 usecs
> [ 39.337841] calling 13e20000.gsc+ @ 1610, parent: soc
> [ 39.342929] call 13e20000.gsc+ returned 0 after 1 usecs
> [ 39.348208] calling 13e10000.gsc+ @ 1610, parent: soc
> [ 39.353258] call 13e10000.gsc+ returned 0 after 1 usecs
> [ 39.358506] calling 13e00000.gsc+ @ 1610, parent: soc
> [ 39.363588] call 13e00000.gsc+ returned 0 after 1 usecs
> [ 39.368835] calling 11c10000.mdma+ @ 1610, parent: soc:amba
> [ 39.374443] call 11c10000.mdma+ returned 0 after 5 usecs
> [ 39.379772] calling 10800000.mdma+ @ 1610, parent: soc:amba
> [ 39.385379] call 10800000.mdma+ returned 0 after 5 usecs
> [ 39.390726] calling 121b0000.pdma+ @ 1610, parent: soc:amba
> [ 39.396316] call 121b0000.pdma+ returned 0 after 5 usecs
> [ 39.401663] calling 121a0000.pdma+ @ 1610, parent: soc:amba
> [ 39.407280] call 121a0000.pdma+ returned 0 after 4 usecs
> [ 39.412554] calling soc:amba+ @ 1610, parent: soc
> [ 39.417340] call soc:amba+ returned 0 after 1 usecs
> [ 39.422186] calling 12130000.phy+ @ 1610, parent: soc
> [ 39.427323] call 12130000.phy+ returned 0 after 1 usecs
> [ 39.432517] calling 12120000.usb+ @ 1610, parent: soc
> [ 39.437820] call 12120000.usb+ returned 0 after 165 usecs
> [ 39.443020] calling 12110000.usb+ @ 1610, parent: soc
> [ 39.448434] call 12110000.usb+ returned 0 after 270 usecs
> [ 39.453523] calling 12100000.phy+ @ 1610, parent: soc
> [ 39.458662] call 12100000.phy+ returned 0 after 1 usecs
> [ 39.463850] calling soc:usb_dwc3+ @ 1610, parent: soc
> [ 39.468994] call soc:usb_dwc3+ returned 0 after 7 usecs
> [ 39.474179] calling 3830000.i2s+ @ 1610, parent: soc
> [ 39.479232] call 3830000.i2s+ returned 0 after 2 usecs
> [ 39.484337] calling 12230000.mmc+ @ 1610, parent: soc
> [ 39.489497] call 12230000.mmc+ returned 0 after 17 usecs
> [ 39.494753] calling 12220000.mmc+ @ 1610, parent: soc
> [ 39.499900] call 12220000.mmc+ returned 0 after 11 usecs
> [ 39.505169] calling 12200000.mmc+ @ 1610, parent: soc
> [ 39.510321] call 12200000.mmc+ returned 0 after 16 usecs
> [ 39.515583] calling 12d30000.spi+ @ 1610, parent: soc
> [ 39.520864] call 12d30000.spi+ returned 0 after 140 usecs
> [ 39.526086] calling 12ce0000.i2c+ @ 1610, parent: soc
> [ 39.531225] call 12ce0000.i2c+ returned 0 after 1 usecs
> [ 39.536415] calling 12cd0000.i2c+ @ 1610, parent: soc
> [ 39.541552] call 12cd0000.i2c+ returned 0 after 1 usecs
> [ 39.546744] calling 12cb0000.i2c+ @ 1610, parent: soc
> [ 39.551881] call 12cb0000.i2c+ returned 0 after 1 usecs
> [ 39.557073] calling 12ca0000.i2c+ @ 1610, parent: soc
> [ 39.562253] call 12ca0000.i2c+ returned 0 after 1 usecs
> [ 39.567427] calling 10060000.tmu+ @ 1610, parent: soc
> [ 39.572696] call 10060000.tmu+ returned 0 after 178 usecs
> [ 39.577932] calling 11c00000.rotator+ @ 1610, parent: soc
> [ 39.583366] call 11c00000.rotator+ returned 0 after 1 usecs
> [ 39.588955] calling 11000000.codec+ @ 1610, parent: soc
> [ 39.594216] call 11000000.codec+ returned 0 after 1 usecs
> [ 39.599632] calling 101d0000.watchdog+ @ 1610, parent: soc
> [ 39.605415] call 101d0000.watchdog+ returned 0 after 256 usecs
> [ 39.611005] calling 10040000.system-controller+ @ 1610, parent: soc
> [ 39.617342] call 10040000.system-controller+ returned 0 after 1 usecs
> [ 39.623806] calling 10d10000.pinctrl+ @ 1610, parent: soc
> [ 39.629223] call 10d10000.pinctrl+ returned 0 after 1 usecs
> [ 39.634845] calling 13400000.pinctrl+ @ 1610, parent: soc
> [ 39.640247] call 13400000.pinctrl+ returned 0 after 1 usecs
> [ 39.646009] calling 11400000.pinctrl+ @ 1610, parent: soc
> [ 39.651271] call 11400000.pinctrl+ returned 0 after 1 usecs
> [ 39.656807] calling soc:pmu+ @ 1610, parent: soc
> [ 39.661509] call soc:pmu+ returned 0 after 2 usecs
> [ 39.666265] calling 101c0000.mct+ @ 1610, parent: soc
> [ 39.671405] call 101c0000.mct+ returned 0 after 1 usecs
> [ 39.676596] calling soc:timer+ @ 1610, parent: soc
> [ 39.681473] call soc:timer+ returned 0 after 1 usecs
> [ 39.686423] calling 10010000.clock-controller+ @ 1610, parent: soc
> [ 39.692676] call 10010000.clock-controller+ returned 0 after 1 usecs
> [ 39.699021] calling 100440c0.power-domain+ @ 1610, parent: Soc
> [ 39.704888] call 100440c0.power-domain+ returned 0 after 1 usecs
> [ 39.710911] calling 100440a0.power-domain+ @ 1610, parent: soc
> [ 39.716780] call 100440a0.power-domain+ returned 0 after 1 usecs
> [ 39.722802] calling 10044060.power-domain+ @ 1610, parent: soc
> [ 39.728697] call 10044060.power-domain+ returned 0 after 1 usecs
> [ 39.734669] calling 10044040.power-domain+ @ 1610, parent: soc
> [ 39.740589] call 10044040.power-domain+ returned 0 after 1 usecs
> [ 39.746560] calling 10044000.power-domain+ @ 1610, parent: soc
> [ 39.752486] call 10044000.power-domain+ returned 0 after 1 usecs
> [ 39.758477] calling 2020000.sysram+ @ 1610, parent: soc
> [ 39.763736] call 2020000.sysram+ returned 0 after 2 usecs
> [ 39.769191] calling 10850000.g2d+ @ 1610, parent: soc
> [ 39.774238] call 10850000.g2d+ returned 0 after 1 usecs
> [ 39.779480] calling 10830600.rng+ @ 1610, parent: soc
> [ 39.784568] call 10830600.rng+ returned 0 after 3 usecs
> [ 39.789808] calling 10830400.rng+ @ 1610, parent: soc
> [ 39.794897] call 10830400.rng+ returned 0 after 3 usecs
> [ 39.800137] calling 10830000.sss+ @ 1610, parent: soc
> [ 39.805226] call 10830000.sss+ returned 0 after 2 usecs
> [ 39.810468] calling 101e0000.rtc+ @ 1610, parent: soc
> [ 39.815639] call 101e0000.rtc+ returned 0 after 84 usecs
> [ 39.820886] calling 12dd0000.pwm+ @ 1610, parent: soc
> [ 39.825972] call 12dd0000.pwm+ returned 0 after 3 usecs
> [ 39.831211] calling 12c90000.i2c+ @ 1610, parent: soc
> [ 39.836300] call 12c90000.i2c+ returned 0 after 1 usecs
> [ 39.841542] calling 12c80000.i2c+ @ 1610, parent: soc
> [ 39.846629] call 12c80000.i2c+ returned 0 after 1 usecs
> [ 39.851871] calling 12c70000.i2c+ @ 1610, parent: soc
> [ 39.856958] call 12c70000.i2c+ returned 0 after 1 usecs
> [ 39.862200] calling 12c60000.i2c+ @ 1610, parent: soc
> [ 39.867313] call 12c60000.i2c+ returned 0 after 1 usecs
> [ 39.872505] calling 12c30000.serial+ @ 1610, parent: soc
> [ 39.878121] call 12c30000.serial+ returned 0 after 209 usecs
> [ 39.883531] calling 12c20000.serial+ @ 1610, parent: soc
> [ 39.888936] call 12c20000.serial+ returned 0 after 6 usecs
> [ 39.894379] calling 12c10000.serial+ @ 1610, parent: soc
> [ 39.899782] call 12c10000.serial+ returned 0 after 5 usecs
> [ 39.905229] calling 12c00000.serial+ @ 1610, parent: soc
> [ 39.910631] call 12c00000.serial+ returned 0 after 6 usecs
> [ 39.916078] calling 10050000.syscon+ @ 1610, parent: soc
> [ 39.921478] call 10050000.syscon+ returned 0 after 1 usecs
> [ 39.926929] calling 12250000.memory-controller+ @ 1610, parent: soc
> [ 39.933289] call 12250000.memory-controller+ returned 0 after 4 usecs
> [ 39.939717] calling 10000000.chipid+ @ 1610, parent: soc
> [ 39.945062] call 10000000.chipid+ returned 0 after 1 usecs
> [ 39.950564] calling soc:syscon-reboot+ @ 1610, parent: soc
> [ 39.956086] call soc:syscon-reboot+ returned 0 after 1 usecs
> [ 39.961761] calling soc:syscon-poweroff+ @ 1610, parent: soc
> [ 39.967484] call soc:syscon-poweroff+ returned 0 after 2 usecs
> [ 39.973344] calling soc+ @ 1610, parent: platform
> [ 39.978108] call soc+ returned 0 after 1 usecs
> [ 39.982477] calling exynos_cpuidle+ @ 1610, parent: platform
> [ 39.988230] call exynos_cpuidle+ returned 0 after 1 usecs
> [ 39.993609] calling reg-dummy+ @ 1610, parent: platform
> [ 39.998903] call reg-dummy+ returned 0 after 1 usecs
> [ 40.005000] calling regulator.49+ @ 1610, parent: 104-0048
> [ 40.014319] call regulator.49+ returned 0 after 4783 usecs
> [ 40.018399] calling regulator.48+ @ 1610, parent: 104-0048
> [ 40.026464] call regulator.48+ returned 0 after 2491 usecs
> [ 40.030537] calling regulator.47+ @ 1610, parent: 104-0048
> [ 40.038619] call regulator.47+ returned 0 after 2503 usecs
> [ 40.042668] calling regulator.46+ @ 1610, parent: 104-0048
> [ 40.050792] call regulator.46+ returned 0 after 2484 usecs
> [ 40.054836] calling regulator.45+ @ 1610, parent: 104-0048
> [ 40.062966] call regulator.45+ returned 0 after 2488 usecs
> [ 40.067007] calling regulator.44+ @ 1610, parent: 104-0048
> [ 40.075128] call regulator.44+ returned 0 after 2482 usecs
> [ 40.079207] calling regulator.43+ @ 1610, parent: 104-0048
> [ 40.087293] call regulator.43+ returned 0 after 2508 usecs
> [ 40.091337] calling regulator.42+ @ 1610, parent: 104-0048
> [ 40.099447] call regulator.42+ returned 0 after 2502 usecs
> [ 40.103488M calling regulator.41+ @ 1610, parent: 104-0048
> [ 40.111609] call regulator.41+ returned 0 after 2481 usecs
> [ 40.115658] calling regulator.40+ @ 1610, parent: 104-0048
> [ 40.123782] call regulator.40+ returned 0 after 2484 usecs
> [ 40.127859] calling regulator.39+ @ 1610, parent: 104-0048
> [ 40.135918] call regulator.39+ returned 0 after 2482 usecs
> [ 40.139993] calling regulator.38+ @ 1610, parent: 104-0048
> [ 40.148053] call regulator.38+ returned 0 after 2482 usecs
> [ 40.153493] calling regulator.37+ @ 1610, parent: 0-0009
> [ 40.160058] call regulator.37+ returned 0 after 2493 usecs
> [ 40.164100] calling regulator.36+ @ 1610, parent: 0-0009
> [ 40.172105] call regulator.36+ returned 0 after 2485 usecs
> [ 40.176148] calling regulator.35+ @ 1610, parent: 0-0009
> [ 40.184097] call regulator.35+ returned 0 after 2481 usecs
> [ 40.188215] calling regulator.34+ @ 1610, parent: 0-0009
> [ 40.196063] call regulator.34+ returned 0 after 2484 usecs
> [ 40.200137] calling regulator.33+ @ 1610, parent: 0-0009
> [ 40.208023] call regulator.33+ returned 0 after 2482 usecs
> [ 40.212067] calling regulator.32+ @ 1610, parent: 0-0009
> [ 40.220014] call regulator.32+ returned 0 after 2482 usecs
> [ 40.224062] calling regulator.31+ @ 1610, parent: 0-0009
> [ 40.232011] call regulator.31+ returned 0 after 2484 usecs
> [ 40.236057] calling regulator.30+ @ 1610, parent: 0-0009
> [ 40.244006] call regulator.30+ returned 0 after 2481 usecs
> [ 40.248085] calling regulator.29+ @ 1610, parent: 0-0009
> [ 40.255969] call regulator.29+ returned 0 after 2480 usecs
> [ 40.260047] calling regulator.28+ @ 1610, parent: 0-0009
> [ 40.267963] call regulator.28+ returned 0 after 2513 usecs
> [ 40.272010] calling regulator.27+ @ 1610, parent: 0-0009
> [ 40.279962] call regulator.27+ returned 0 after 2484 usecs
> [ 40.284006] calling regulator.26+ @ 1610, parent: 0-0009
> [ 40.291953] call regulator.26+ returned 0 after 2480 usecs
> [ 40.295993] calling regulator.25+ @ 1610, parent: 0-0009
> [ 40.303941] call regulator.25+ returned 0 after 2482 usecs
> [ 40.308021] calling regulator.24+ @ 1610, parent: 0-0009
> [ 40.315905] call regulator.24+ returned 0 after 2481 usecs
> [ 40.319982] calling regulator.23+ @ 1610, parent: 0-0009
> [ 40.327863] call regulator.23+ returned 0 after 2478 usecs
> [ 40.331912] calling regulator.22+ @ 1610, parent: 0-0009
> [ 40.339858] call regulator.22+ returned 0 after 2482 usecs
> [ 40.343898] calling regulator.21+ @ 1610, parent: 0-0009
> [ 40.351846] call regulator.21+ returned 0 after 2481 usecs
> [ 40.355894] calling regulator.20+ @ 1610, parent: 0-0009
> [ 40.363838] call regulator.20+ returned 0 after 2479 usecs
> [ 40.367912] calling regulator.19+ @ 1610, parent: 0-0009
> [ 40.375796] call regulator.19+ returned 0 after 2480 usecs
> [ 40.379874] calling regulator.18+ @ 1610, parent: 0-0009
> [ 40.387789] call regulator.18+ returned 0 after 2513 usecs
> [ 40.391837] calling regulator.17+ @ 1610, parent: 0-0009
> [ 40.399825] call regulator.17+ returned 0 after 2482 usecs
> [ 40.403868] calling regulator.16+ @ 1610, parent: 0-0009
> [ 40.411816] call regulator.16+ returned 0 after 2481 usecs
> [ 40.415864] calling regulator.15+ @ 1610, parent: 0-0009
> [ 40.423813] call regulator.15+ returned 0 after 2483 usecs
> [ 40.427891] calling regulator.14+ @ 1610, parent: 0-0009
> [ 40.435775] call regulator.14+ returned 0 after 2480 usecs
> [ 40.439852] calling regulator.13+ @ 1610, parent: 0-0009
> [ 40.447747] call regulator.13+ returned 0 after 2491 usecs
> [ 40.451791] calling regulator.12+ @ 1610, parent: 0-0009
> [ 40.459718] call regulator.12+ returned 0 after 2493 usecs
> [ 40.463760] calling regulator.11+ @ 1610, parent: 0-0009
> [ 40.471704] call regulator.11+ returned 0 after 2478 usecs
> [ 40.475747] calling regulator.10+ @ 1610, parent: 0-0009
> [ 40.483693] call regulator.10+ returned 0 after 2479 usecs
> [ 40.487766] calling regulator.9+ @ 1610, parent: 0-0009
> [ 40.495563] call regulator.9+ returned 0 after 2482 usecs
> [ 40.499553] calling regulator.8+ @ 1610, parent: 0-0009
> [ 40.507358] call regulator.8+ returned 0 after 2489 usecs
> [ 40.511317] calling regulator.7+ @ 1610, parent: 0-0009
> [ 40.519148] call regulator.7+ returned 0 after 2482 usecs
> [ 40.523105] calling regulator.6+ @ 1610, parent: 0-0009
> [ 40.530965] call regulator.6+ returned 0 after 2481 usecs
> [ 40.534918] calling regulator.5+ @ 1610, parent: 0-0009
> [ 40.542777] call regulator.5+ returned 0 after 2480 usecs
> [ 40.546732] calling regulator.4+ @ 1610, parent: 0-0009
> [ 40.554589] call regulator.4+ returned 0 after 2480 usecs
> [ 40.558576] calling regulator.3+ @ 1610, parent: 0-0009
> [ 40.566375] call regulator.3+ returned 0 after 2481 usecs
> [ 40.574330] calling regulator.2+ @ 1610, parent: regulator-usb3
> [ 40.581488] call regulator.2+ returned 0 after 2503 usecs
> [ 40.585445] calling regulator.1+ @ 1610, parent: vbat-fixed-regulator
> [ 40.594529] call regulator.1+ returned 0 after 2483 usecs
> [ 40.599129] calling 3860000.pinctrl+ @ 1610, parent: soc
> [ 40.603864] call 3860000.pinctrl+ returned 0 after 6 usecs
> [ 40.609438] calling 10d10000.pinctrl+ @ 1610, parent: soc
> [ 40.614804] call 10d10000.pinctrl+ returned 0 after 9 usecs
> [ 40.620443] calling 13400000.pinctrl+ @ 1610, parent: soc
> [ 40.625838] call 13400000.pinctrl+ returned 0 after 20 usecs
> [ 40.631656] calling 11400000.pinctrl+ @ 1610, parent: soc
> [ 40.636963] call 11400000.pinctrl+ returned 0 after 33 usecs
> [ 40.642621] calling 3810000.audss-clock-controller+ @ 1610, parent: soc
> [ 40.649295] call 3810000.audss-clock-controller+ returned 0 after 2
> usecs
> [ 40.656038] calling DISP1+ @ 1610, parent: 10010000.clock-controller
> [ 40.662615] call DISP1+ returned 0 after 134 usecs
> [ 40.667491] calling regulator.0+ @ 1610, parent: reg-dummy
> [ 40.675340] call regulator.0+ returned 0 after 2501 usecs
> [ 40.680439] calling 145b0000.dp-controller+ @ 1610, parent: soc
> [ 40.685291] call 145b0000.dp-controller+ returned 0 after 3 usecs
> [ 40.691452] calling 14530000.hdmi+ @ 1610, parent: soc
> [ 40.696569] call 14530000.hdmi+ returned 0 after 2 usecs
> [ 40.704295] calling 14450000.mixer+ @ 1610, parent: soc
> [ 40.708189] call 14450000.mixer+ returned 0 after 3 usecs
> [ 40.713542] calling 14400000.fimd+ @ 1610, parent: soc
> [ 40.718772] call 14400000.fimd+ returned 0 after 3 usecs
> [ 40.727460] calling 14650000.sysmmu+ @ 1610, parent: soc
> [ 40.731412] call 14650000.sysmmu+ returned 0 after 3 usecs
> [ 40.736888] calling 14640000.sysmmu+ @ 1610, parent: soc
> [ 40.742287] call 14640000.sysmmu+ returned 0 after 2 usecs
> [ 40.747764] calling 13eb0000.sysmmu+ @ 1610, parent: soc
> [ 40.753110] call 13eb0000.sysmmu+ returned 0 after 3 usecs
> [ 40.758614] calling 13ea0000.sysmmu+ @ 1610, parent: soc
> [ 40.763960] call 13ea0000.sysmmu+ returned 0 after 2 usecs
> [ 40.769463] calling 13e90000.sysmmu+ @ 1610, parent: soc
> [ 40.774809] call 13e90000.sysmmu+ returned 0 after 2 usecs
> [ 40.780320] calling 13e80000.sysmmu+ @ 1610, parent: soc
> [ 40.785659] call 13e80000.sysmmu+ returned 0 after 2 usecs
> [ 40.791163] calling 13c50000.sysmmu+ @ 1610, parent: soc
> [ 40.796510] call 13c50000.sysmmu+ returned 0 after 2 usecs
> [ 40.802013] calling 13c40000.sysmmu+ @ 1610, parent: soc
> [ 40.807386] call 13c40000.sysmmu+ returned 0 after 2 usecs
> [ 40.812940] calling 11f20000.sysmmu+ @ 1610, parent: soc
> [ 40.818284] call 11f20000.sysmmu+ returned 0 after 3 usecs
> [ 40.823699] calling 11210000.sysmmu+ @ 1610, parent: soc
> [ 40.829088] call 11210000.sysmmu+ returned 0 after 3 usecs
> [ 40.834539] calling 11200000.sysmmu+ @ 1610, parent: soc
> [ 40.839935] call 11200000.sysmmu+ returned 0 after 2 usecs
> [ 40.845539] calling 3830000.i2s+ @ 1610, parent: soc
> [ 40.850439] call 3830000.i2s+ returned 0 after 3 usecs
> [ 40.855564] calling 12ce0000.i2c+ @ 1610, parent: soc
> [ 40.860679] call 12ce0000.i2c+ returned 0 after 1 usecs
> [ 40.865867] calling 12cd0000.i2c+ @ 1610, parent: soc
> [ 40.871007] call 12cd0000.i2c+ returned 0 after 2 usecs
> [ 40.876196] calling 12cb0000.i2c+ @ 1610, parent: soc
> [ 40.881336] call 12cb0000.i2c+ returned 0 after 1 usecs
> [ 40.886525] calling 12ca0000.i2c+ @ 1610, parent: soc
> [ 40.891666] call 12ca0000.i2c+ returned 0 after 1 usecs
> [ 40.896885] calling 3860000.pinctrl+ @ 1610, parent: soc
> [ 40.902257] call 3860000.pinctrl+ returned 0 after 2 usecs
> [ 40.907970] calling 3810000.audss-clock-controller+ @ 1610, parent: soc
> [ 40.914748] call 3810000.audss-clock-controller+ returned 0 after 350
> usecs
> [ 40.921371] calling DISP1+ @ 1610, parent: 10010000.clock-controller
> [ 40.928050] call DISP1+ returned 0 after 263 usecs
> [ 40.932597] calling 12c90000.i2c+ @ 1610, parent: soc
> [ 40.937847] call 12c90000.i2c+ returned 0 after 165 usecs
> [ 40.943034] calling 12c80000.i2c+ @ 1610, parent: soc
> [ 40.948176] call 12c80000.i2c+ returned 0 after 3 usecs
> [ 40.953362] calling 12c70000.i2c+ @ 1610, parent: soc
> [ 40.958505] call 12c70000.i2c+ returned 0 after 4 usecs
> [ 40.963690] calling 12c60000.i2c+ @ 1610, parent: soc
> [ 40.968833] call 12c60000.i2c+ returned 0 after 3 usecs
> [ 40.974280] Disabling non-boot CPUs ...
> [ 41.019014] IRQ55 no longer affine to CPU1
> [ 41.022280] PM: Calling exynos_pm_suspend+0x0/0x50
> [ 41.029707] PM: Calling sched_clock_suspend+0x0/0x30
> [ 41.034649] PM: Calling timekeeping_suspend+0x0/0x2f8
> [ 41.034649] PM: Calling irq_gc_suspend+0x0/0x6c
> [ 41.034649] PM: Calling fw_suspend+0x0/0x18
> [ 41.034649] PM: Calling cpu_pm_suspend+0x0/0x18
> [ 41.034649] PM: Calling exynos_clkout_suspend+0x0/0x24
> [ 41.034649] PM: Calling exynos5250_clk_suspend+0x0/0x20
> [ 41.034649] PM: Calling combiner_suspe[ 41.066995] call
> 12c30000.serial+ returned 0 after 60 usecs
> [ 41.071122] calling 12c60000.i2c+ @ 1610, parent: soc
> [ 41.076307] call 12c60000.i2c+ returned 0 after 1 usecs
> [ 41.081450] calling 12c70000.i2c+ @ 1610, parent: soc
> [ 41.086607] call 12c70000.i2c+ returned 0 after 1 usecs
> [ 41.091807] calling 12c80000.i2c+ @ 1610, parent: soc
> [ 41.096898] call 12c80000.i2c+ returned 0 after 1 usecs
> [ 41.102133] calling 12c90000.i2c+ @ 1610, parent: soc
> [ 41.107228] call 12c90000.i2c+ returned 0 after 1 usecs
> [ 41.112470] calling 12dd0000.pwm+ @ 1610, parent: soc
> [ 41.117569] call 12dd0000.pwm+ returned 0 after 13 usecs
> [ 41.122880] calling 101e0000.rtc+ @ 1610, parent: soc
> [ 41.127975] s3c-btc 101e0000.rtc: rtc disabled, re-enabling
> [ 41.133558] call 101e0000.rtc+ returned 0 after 5456 usecs
> [ 41.139000] calling 10830000.sss+ @ 1610, parent: soc
> [ 41.144142] call 10830000.sss+ returned 0 after 2 usecs
> [ 41.149328] calling 10830400.rng+ @ 1610, parent: soc
> [ 41.154472] call 10830400.rng+ returned 0 after 1 usecs
> [ 41.159657] calling 10830600.rng+ @ 1610, parent: soc
> [ 41.164802] call 10830600.rng+ returned 0 after 3 usecs
> [ 41.169987] calling 10850000.g2d+ @ 1610, parent: soc
> [ 41.175129] call 10850000.g2d+ returned 0 after 1 usecs
> [ 41.180315] calling 2020000.sysram+ @ 1610, parent: soc
> [ 41.185633] call 2020000.sysram+ returned 0 after 1 usecs
> [ 41.190992] calling 10044000.power-domain+ @ 1610, parent: soc
> [ 41.196920] call 10044000.power-domain+ returned 0 after 1 usecs
> [ 41.202976] calling 10044040.power-domain+ @ 1610, parent: soc
> [ 41.208787] call 10044040.power-domain+ returned 0 after 1 usecs
> [ 41.214811] calling 10044060.power-domain+ @ 1610, parent: soc
> [ 41.220678] call 10044060.power-domain+ returned 0 after 1 usecs
> [ 41.226696] calling 100440a0.power-domain+ @ 1610, parent: soc
> [ 41.232594] call 100440a0.power-domain+ returned 0 after 1 usecs
> [ 41.238563] calling 100440c0.power-domain+ @ 1610, parent: soc
> [ 41.244536] call 100440c0.power-domain+ returned 0 after 1 usecs
> [ 41.250455] calling 10010000.clock-controller+ @ 1610, parent: soc
> [ 41.256742] call 10010000.clock-controller+ returned 0 after 1 usecs
> [ 41.263088] calling soc:timer+ @ 1610, parent: soc
> [ 41.267891] call soc:timer+ returned 0 after 1 usecs
> [ 41.272868] calling 101c0000.mct+ @ 1610, parent: soc
> [ 41.277962] call 101c0000.mct+ returned 0 after 1 usecs
> [ 41.283199] calling soc:pmu+ @ 1610, parent: soc
> [ 41.287857] call soc:pmu+ returned 0 after 2 usecs
> [ 41.292658] calling 11400000.pinctrl+ @ 1610, parent: soc
> [ 41.298103] call 11400000.pinctrl+ returned 0 after 1 usecs
> [ 41.303773] calling 13400000.pinctrl+ @ 1610, parent: soc
> [ 41.309125] call 13400000.pinctrl+ returned 0 after 1 usecs
> [ 41.314738] calling 10d10000.pinctrl+ @ 1610, parent: soc
> [ 41.320149] call 10d10000.pinctrl+ returned 0 after 2 usecs
> [ 41.325757] calling 10040000.system-controller+ @ 1610, parent: soc
> [ 41.332069] call 10040000.system-controller+ returned 0 after 1 usecs
> [ 41.338471] calling 101d0000.watchdog+ @ 1610, parent: soc
> [ 41.344054] s3c2410-wdt 101d0000.watchdog: watchdog disabled
> [ 41.349659] call 101d0000.watchdog+ returned 0 after 5485 usecs
> [ 41.355593] calling 11000000.codec+ @ 1610, parent: soc
> [ 41.360858] call 11000000.codec+ returned 0 after 1 usecs
> [ 41.366266] calling 11c00000.rotator+ @ 1610, parent: soc
> [ 41.371736] call 11c00000.rotator+ returned 0 after 1 usecs
> [ 41.377266] calling 10060000.tmu+ @ 1610, parent: soc
> [ 41.382437] call 10060000.tmu+ returned 0 after 31 usecs
> [ 41.387681] calling 12ca0000.i2c+ @ 610, parent: soc
> [ 41.392823] call 12ca0000.i2c+ returned 0 after 1 usecs
> [ 41.398010] calling 12cb0000.i2c+ @ 1610, parent: soc
> [ 41.403152] call 12cb0000.i2c+ returned 0 after 1 usecs
> [ 41.408339] calling 12cd0000.i2c+ @ 1610, parent: soc
> [ 41.413481] call 12cd0000.i2c+ returned 0 after 1 usecs
> [ 41.418669] calling 12ce0000.i2c+ @ 1610, parent: soc
> [ 41.423811] call 12ce0000.i2c+ returned 0 after 1 usecs
> [ 41.428998] calling 12d30000.spi+ @ 1610, parent: soc
> [ 41.434413] call 12d30000.spi+ returned 0 after 268 usecs
> [ 41.439502] calling 12200000.mmc+ @ 1610, parent: soc
> [ 41.444837] call 12200000.mmc+ returned 0 after 188 usecs
> [ 41.450010] calling 12220000.mmc+ @ 1610, parent: soc
> [ 41.450061] calling mmc0:0001+ @ 1643, parent: mmc0
> [ 41.455218] call 12220000.mmc+ returned 0 after 26 usecs
> [ 41.460128] call mmc0:0001+ returned 0 after 19 usecs
> [ 41.465409] calling 12230000.mmc+ @ 1610, parent: soc
> [ 41.470448] calling mmc1:e624+ @ 1644, parent: mmc1
> [ 41.475574] call 12230000.mmc+ returned 0 after 31 usecs
> [ 41.480499] call mmc1:e624+ returned 0 after 8 usecs
> [ 41.485796] calling 3830000.i2s+ @ 1610, parent: soc
> [ 41.490756] calling mmc2:0001+ @ 1646, parent: mmc2
> [ 41.495767] call 3830000.i2s+ returned 0 after 2 usecs
> [ 41.495778] calling soc:usb_dwc3+ @ 1610, parent: soc
> [ 41.511006] call soc:usb_dwc3+ returned 0 after 63 usecs
> [ 41.516269] calling 12100000.phy+ @ 1610, parent: soc
> [ 41.521357] call 12100000.phy+ returned 0 after 2 usecs
> [ 41.526591] calling 12110000.usb+ @ 1610, parent: soc
> [ 41.532034] usb usb1: root hub lost power or was reset
> [ 41.536810] call 12110000.usb+ returned 0 after 4980 usecs
> [ 41.542304] calling 12120000.usb+ @ 1610, parent: soc
> [ 41.542319] calling usb1+ @ 1617, parent: 12110000.usb
> [ 41.551709] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req
> 400000Hz, actual 396825HZ div = 63)
> [ 41.615745] usb usb2: root hub lost power or was reset
> [ 41.619947] call 12120000.usb+ returned 0 after 70860 usecs
> [ 41.625087] calling 12130000.phy+ @ 1610, parent: soc
> [ 41.625111] calling usb2+ @ 1613, parent: 12120000.usb
> [ 41.630177] call 12130000.phy+ returned 0 after 2 usecs
> [ 41.640597] calling soc:amba+ @ 1610, parent: soc
> [ 41.645371] call soc:amba+ returned 0 after 1 usecs
> [ 41.650193] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req
> 50000000Hz, actual 50000000HZ div = 0)
> [ 41.659959] calling 121a0000.pdma+ @ 1610, parent: soc:amba
> [ 41.660009] call mmc2:0001+ returned 0 after 155559 usecs
> [ 41.665553] call 121a0000.pdma+ returned 0 after 5 usecs
> [ 41.665565] calling 121b0000.pdma+ @ 1610, parent: soc:amba
> [ 41.681649] calling mmc2:0001:1+ @ 1647, parent: mmc2:0001
> [ 41.682210] call 121b0000.pdma+ returned 0 after 5 usecs
> [ 41.687397] call mmc2:0001:1+ returned 0 after 1 usecs
> [ 41.692768] calling 10800000.mdma+ @ 1610, parent: soc:amba
> [ 41.697822] calling mmc2:0001:2+ @ 1648, parent: mmc2:0001
> [ 41.703483] call 10800000.mdma+ returned 0 after 4 usecs
> [ 41.709022] calling mmc2:0001:3+ @ 1649, parent: mmc2:0001
> [ 41.714329] calling 11c10000.mdma+ @ 1610, parent: soc:amba
> [ 41.719870] call mmc2:0001:3+ returned 0 after 1 usecs
> [ 41.725590] call mmc2:0001:2+ returned 0 after 1 usecs
> [ 41.731642] call 11c10000.mdma+ returned 0 after 6 usecs
> [ 41.741045] calling 13e00000.gsc+ @ 1610, parent: soc
> [ 41.746186] call 13e00000.gsc+ returned 0 after 1 usecs
> [ 41.751373] calling 13e10000.gsc+ @ 1610, parent: soc
> [ 41.756516] call 13e10000.gsc+ returned 0 after 1 usecs
> [ 41.761724] calling 13e20000.gsc+ @ 1610, parent: soc
> [ 41.766820] call 13e20000.gsc+ returned 0 after 1 usecs
> [ 41.772058] calling 13e30000.gsc+ @ 1610, parent: soc
> [ 41.777149] call 13e30000.gsc+ returned 0 after 1 usecs
> [ 41.782386] calling 101b0000.cec+ @ 1610, parent: soc
> [ 41.787479] call 101b0000.cec+ returned 0 after 1 usecs
> [ 41.792715] calling soc:video-phy+ @ 1610, parent: soc
> [ 41.797895] call soc:video-phy+ returned 0 after 2 usecs
> [ 41.801680] call usb1+ returned 0 after 243207 usecs
> [ 41.803225] calling 10a60000.sysmmu+ @ 1610, parent: soc
> [ 41.808275] calling 1-1+ @ 1635, parent: usb1
> [ 41.813545] call 10a60000.sysmmu+ returned 0 after 2 usecs
> [ 41.813563] calling 11200000.sysmmu+ @ 1610, parent: soc
> [ 41.828798] call 11200000.sysmmu+ returned 0 after 2 usecs
> [ 41.834298] calling 11210000.sysmmu+ @ 1610, parent: soc
> [ 41.839649] call 11210000.sysmmu+ returned 0 after 3 usecs
> [ 41.845147] calling 11d40000.sysmmu+ @ 1610, parent: soc
> [ 41.850498] call 11d40000.sysmmu+ returned 0 after 3 usecs
> [ 41.855997] calling 11f20000.sysmmu+ @ 1610, parent: soc
> [ 41.861348] call 11f20000.sysmmu+ returned 0 after 2 usecs
> [ 41.866846] calling 13260000.sysmmu+ @ 1610, parent: soc
> [ 41.872264] call 13260000.sysmmu+ returned 0 after 2 usecs
> [ 41.877673] calling 13270000.sysmmu+ @ 1610, parent: soc
> [ 41.881864] call usb2+ returned 0 after 240745 usecs
> [ 41.883075] call 13270000.sysmmu+ returned 0 after 3 usecs
> [ 41.893496] calling 132a0000.sysmmu+ @ 1610, parent: soc
> [ 41.898845] call 132a0000.sysmmu+ returned 0 after 2 usecs
> [ 41.904345] calling 13280000.sysmmu+ @ 1610, parent: soc
> [ 41.909695] call 13280000.sysmmu+ returned 0 after 2 usecs
> [ 41.915194] calling 13290000.sysmmu+ @ 1610, parent: soc
> [ 41.920546] call 13290000.sysmmu+ returned 0 after 3 usecs
> [ 41.926044] calling 132b0000.sysmmu+ @ 1610, parent: soc
> [ 41.931396] call 132b0000.sysmmu+ returned 0 after 3 usecs
> [ 41.936900] calling 132c0000.sysmmu+ @ 1610, parent: soc
> [ 41.942270] call 132c0000.sysmmu+ returned 0 after 2 usecs
> [ 41.947720] calling 132d0000.sysmmu+ @ 1610, parent: soc
> [ 41.953122] call 132d0000.sysmmu+ returned 0 after 3 usecs
> [ 41.958570] calling 132e0000.sysmmu+ @ 1610, parent: soc
> [ 41.962417] usb 1-1: reset high-speed USB device number 2 using
> exynos-ehci
> [ 41.963970] call 132e0000.sysmmu+ returned 0 after 3 usecs
> [ 41.976423] calling 132f0000.sysmmu+ @ 1610, parent: soc
> [ 41.981764] call 132f0000.sysmmu+ returned 0 after 2 usecs
> [ 41.987225] calling 13c40000.sysmmu+ @ 1610, parent: soc
> [ 41.992627] call 13c40000.sysmmu+ returned 0 after 2 usecs
> [ 41.998072] calling 13c50000.sysmmu+ @ 1610, parent: soc
> [ 42.003469] call 13c50000.sysmmu+ returned 0 after 2 usecs
> [ 42.008913] calling 13e80000.sysmmu+ @ 1610, parent: soc
> [ 42.014319] call 13e80000.sysmmu+ returned 0 after 2 usecs
> [ 42.019763] calling 13e90000.sysmmu+ @ 1610, parent: soc
> [ 42.025166] call 13e90000.sysmmu+ returned 0 after 2 usecs
> [ 42.030613] calling 13ea0000.sysmmu+ @ 1610, parent: soc
> [ 42.036015] call 13ea0000.sysmmu+ returned 0 after 2 usecs
> [ 42.041463] calling 13eb0000.sysmmu+ @ 1610, parent: soc
> [ 42.046863] call 13eb0000.sysmmu+ returned 0 after 2 usecs
> [ 42.052336] calling 14640000.sysmmu+ @ 1610, parent: soc
> [ 42.057753] call 14640000.sysmmu+ returned 0 after 65 usecs
> [ 42.063283] calling 14650000.sysmmu+ @ 1610, parent: soc
> [ 42.068626] call 14650000.sysmmu+ returned 0 after 3 usecs
> [ 42.074129] calling opp_table0+ @ 1610, parent: platform
> [ 42.079475] call opp_table0+ returned 0 after 1 usecs
> [ 42.084575] calling gpio-keys+ @ 1610, parent: platform
> [ 42.089805] wake disabled for irq 152
> [ 42.093464] wake disabled for irq 153
> [ 42.097095] call gpio-keys+ returned 0 after 7122 usecs
> [ 42.102331] calling vbat-fixed-regulator+ @ 1610, parent: platform
> [ 42.108559] call vbat-fixed-regulator+ returned 0 after 2 usecs
> [ 42.114486] calling i2c-arbitrator+ @ 1610, parent: platform
> [ 42.120186] call i2c-arbitrator+ returned 0 after 2 usecs
> [ 42.125615] calling regulator-usb3+ @ 1610, parent: platform
> [ 42.131306] call regulator-usb3+ returned 0 after 1 usecs
> [ 42.136717] calling mmc3_pwrseq+ @ 1610, parent: platform
> [ 42.142172] call mmc3_pwrseq+ returned 0 after 1 usecs
> [ 42.147294] calling 0-0009+ @ 1610, parent: i2c-0
> [ 42.152352] call 0-0009+ returned 0 after 279 usecs
> [ 42.156913] calling 1-0067+ @ 1610, parent: i2c-1
> [ 42.161775] wake disabled for irq 148
> [ 42.321621] call 1-0067+ returned 0 after 156102 usecs
> [ 42.325614] calling regulatory.0+ @ 1610, parent: platform
> [ 42.330866] call regulatory.0+ returned 0 after 1 usecs
> [ 42.336121] calling alarmtimer+ @ 1610, parent: platform
> [ 42.341459] call alarmtimer+ returned 0 after 6 usecs
> [ 42.348605] calling serial8250+ @ 1610, parent: platform
> [ 42.352589] call serial8250+ returned 0 after 2 usecs
> [ 42.357625] calling exynos-drm+ @ 1610, parent: platform
> [ 42.478238] exynos-dp 145b0000.dp-controller: Link Training Clock
> Recovery success
> [ 42.487049] exynos-dp 145b0000.dp-controller: Link Training success!
> [ 42.598098] exynos-dp 145b0000.dp-controller: Timeout of video
> streamclk ok
> [ 42.603648] exynos-dp 145b0000.dp-controller: unable to config video
> [ 42.632081] call 1-1+ returned 0 after 794948 usecs
> [ 42.654712] call exynos-drm+ returned 0 after 284877 usecs
> [ 42.660368] calling max77686-pmic+ @ 1610, parent: 0-0009
> [ 42.665845] call max77686-pmic+ returned 0 after 1 usecs
> [ 42.671229] calling max77686-rtc+ @ 1610, parent: 0-0009
> [ 42.676798] wake disabled for irq 146
> [ 42.680400] call max77686-rtc+ returned 0 after 3705 usecs
> [ 42.685914] calling max77686-clk+ @ 1610, parent: 0-0009
> [ 42.691260] call max77686-clk+ returned 0 after 1 usecs
> [ 42.696508] calling Fixed MDIO bus.0+ @ 1610, parent: platform
> [ 42.702422] call Fixed MDIO bus.0+ returned 0 after 1 usecs
> [ 42.708756] calling usb_phy_generic.0.auto+ @ 1610, parent: platform
> [ 42.715664] call usb_phy_generic.0.auto+ returned 0 after 1 usecs
> [ 42.721785] calling usb_phy_generic.1.auto+ @ 1610, parent: platform
> [ 42.728251] call usb_phy_generic.1.auto+ returned 0 after 1 usecs
> [ 42.734379] calling 12000000.dwc3+ @ 1610, parent: soc:usb_dwc3
> [ 42.740472] call 12000000.dwc3+ returned 0 after 79 usecs
> [ 42.745933] calling input0+ @ 1610, parent: 1-0067
> [ 42.745948] calling xhci-hcd.2.auto+ @ 1618, parent: 12000000.dwc3
> [ 42.750813] call input0+ returned 0 after 3 usecs
> [ 42.757161] usb usb3: root hub lost power or was reset
> [ 42.761865] calling rtc0+ @ 1610, parent: max77686-rtc
> [ 42.767037] usb usb4: root hub lost power or was reset
> [ 42.780258] call xhci-hcd.2.auto+ returned 0 after 22597 usecs
> [ 42.786253] calling usb3+ @ 1625, parent: xhci-hcd.2.auto
> [ 42.791825] calling usb4+ @ 1630, parent: xhci-hcd.2.auto
> [ 42.802300] call rtc0+ returned 0 after 29281 usecs
> [ 42.807236] calling rtc1+ @ 1610, parent: 101e0000.rtc
> [ 42.812588] call rtc1+ returned 0 after 1 usecs
> [ 42.817220] calling 104-001e+ @ 1610, parent: i2c-104
> [ 42.825054] wake disabled for irq 150
> [ 42.911689] call usb4+ returned 0 after 111658 usecs
> [ 42.912072] call usb3+ returned 0 after 111335 usecs
> [ 44.505817] asix 1-1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
>
>
>
>
>
>
>
>
> *** break sent ***
> [ 63.472452] sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c)
> show-all-locks(d) terminate-all-tasks(e) memory-full-oom-kill(f)
> kill-all-tasks(i) thaw-filesystems(j) sak(k)
> show-backtrace-all-active-cpus(l) show-memory-usage(m)
> nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q)
> unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V)
> show-blocked-tasks(w) dump-ftrace-buffer(z)
>
> *** break sent ***
> [ 66.873020] sysrq: SysRq : Show backtrace of all active CPUs
> [ 66.878907] NMI backtrace for cpu 0
> [ 66.882602] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
> 4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
> [ 66.891572] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
> [ 66.897948] [<c0111ed0>] (unwind_backtrace) from [<c010e4ec>]
> (show_stack+0x10/0x14)
> [ 66.905999] [<c010e4ec>] (show_stack) from [<c09cea04>]
> (dump_stack+0x90/0xc8)
> [ 66.913539] [<c09cea04>] (dump_stack) from [<c09d4ab4>]
> (nmi_cpu_backtrace+0xf8/0x10c)
> [ 66.921777] [<c09d4ab4>] (nmi_cpu_backtrace) from [<c09d4bd8>]
> (nmi_trigger_cpumask_backtrace+0x110/0x148)
> [ 66.931793] [<c09d4bd8>] (nmi_trigger_cpumask_backtrace) from
> [<c04c0d3c>] (__handle_sysrq+0xdc/0x250)
> [ 66.941482] [<c04c0d3c>] (__handle_sysrq) from [<c04da95c>]
> (s3c24xx_serial_rx_drain_fifo+0x134/0x224)
> [ 66.951191] [<c04da95c>] (s3c24xx_serial_rx_drain_fifo) from
> [<c04db568>] (s3c24xx_serial_rx_chars+0x6c/0x198)
> [ 66.961600] [<c04db568>] (s3c24xx_serial_rx_chars) from [<c04db6dc>]
> (s3c64xx_serial_handle_irq+0x48/0x60)
> [ 66.971644] [<c04db6dc>] (s3c64xx_serial_handle_irq) from
> [<c018eb0c>] (__handle_irq_event_percpu+0x98/0x510)
> [ 66.981975] [<c018eb0c>] (__handle_irq_event_percpu) from
> [<c018efa0>] (handle_irq_event_percpu+0x1c/0x58)
> [ 66.992059] [<c018efa0>] (handle_irq_event_percpu) from [<c018f014>]
> (handle_irq_event+0x38/0x5c)
> [ 67.001370] [<c018f014>] (handle_irq_event) from [<c01927dc>]
> (handle_fasteoi_irq+0xa4/0x138)
> [ 67.010341] [<c01927dc>] (handle_fasteoi_irq) from [<c018e2e4>]
> (generic_handle_irq+0x18/0x28)
> [ 67.019428] [<c018e2e4>] (generic_handle_irq) from [<c018e400>]
> (__handle_domain_irq+0x6c/0xe4)
> [ 67.028610] [<c018e400>] (__handle_domain_irq) from [<c0465ca4>]
> (gic_handle_irq+0x54/0xa0)
> [ 67.037441] [<c0465ca4>] (gic_handle_irq) from [<c01019f0>]
> (__irq_svc+0x70/0xb0)
> [ 67.045410] Exception stack(0xc0f01ee8 to 0xc0f01f30)
> [ 67.050934] 1ee0: 00000001 00000001 00000000
> c0f0bc00 91f13160 0000000f
> [ 67.059626] 1f00: 00000000 c0f7aad4 00000000 00000000 eefb47c0
> 00000000 00000000 c0f01f38
> [ 67.068324] 1f20: c0180a08 c06c4e0c 20000153 ffffffff
> [ 67.073876] [<c01019f0>] (__irq_svc) from [<c06c4e0c>]
> (cpuidle_enter_state+0x1c0/0x498)
> [ 67.082500] [<c06c4e0c>] (cpuidle_enter_state) from [<c015c1e8>]
> (do_idle+0x1c0/0x278)
> [ 67.090967] [<c015c1e8>] (do_idle) from [<c015c5e0>]
> (cpu_startup_entry+0x18/0x1c)
> [ 67.099089] [<c015c5e0>] (cpu_startup_entry) from [<c0e00dc0>]
> (start_kernel+0x3ec/0x46c)
> [ 67.107837] Sending NMI from CPU 0 to CPUs 1:
> [ 67.112750] NMI backtrace for cpu 1
> [ 67.112756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
> 4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
> [ 67.112758] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
> [ 67.112764] PC is at cpuidle_enter_state+0x1c0/0x498
> [ 67.112769] LR is at trace_hardirqs_on_caller+0x100/0x1e0
> [ 67.112772] pc : [<c06c4e0c>] lr : [<c0180a08>] psr: 20000013
> [ 67.112775] sp : ee8f7f70 ip : 00000000 fp : 00000000
> [ 67.112777] r10: eefc67c0 r9 : 00000000 r8 : 00000001
> [ 67.112780] r7 : c0f7aad4 r6 : 00000001 r5 : 0000000f r4 : a03b2a20
> [ 67.112782] r3 : ee8ea640 r2 : 00000000 r1 : 00000001 r0 : 00000001
> [ 67.112786] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM
> Segment none
> [ 67.112788] Control: 10c5387d Table: 6c06806a DAC: 00000051
> [ 67.112793] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
> 4.17.0-rc6-00023-g38ba34a43dbc-dirty #203
> [ 67.112795] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
> [ 67.112801] [<c0111ed0>] (unwind_backtrace) from [<c010e4ec>]
> (show_stack+0x10/0x14)
> [ 67.112807] [<c010e4ec>] (show_stack) from [<c09cea04>]
> (dump_stack+0x90/0xc8)
> [ 67.112813] [<c09cea04>] (dump_stack) from [<c09d4a64>]
> (nmi_cpu_backt2ace+0xa8/0x10c)
> [ 67.112818] [<c09d4a64>] (nmi_cpu_backtrace) from [<c0110c4c>]
> (handle_IPI+0x108/0x3e4)
> [ 67.112824] [<c0110c4c>] (handle_IPI) from [<c0465ce4>]
> (gic_handle_irq+0x94/0xa0)
> [ 67.112829] [<c0465ce4>] (gic_handle_irq) from [<c01019f0>]
> (__irq_svc+0x70/0xb0)
> [ 67.112831] Exception stack(0xee8f7f20 to 0xee8f7f68)
> [ 67.112836] 7f20: 00000001 00000001 00000000 ee8ea640 a03b2a20
> 0000000f 00000001 c0f7aad4
> [ 67.112841] 7f40: 00000001 00000000 eefc67c0 00000000 00000000
> ee8f7f70 c0180a08 c06c4e0c
> [ 67.112844] 7f60: 20000013 ffffffff
> [ 67.112850] [<c01019f0>] (__irq_svc) from [<c06c4e0c>]
> (cpuidle_enter_state+0x1c0/0x498)
> [ 67.112857] [<c06c4e0c>] (cpuidle_enter_state) from [<c015c1e8>]
> (do_idle+0x1c0/0x278)
> [ 67.112862] [<c015c1e8>] (do_idle) from [<c015c5e0>]
> (cpu_startup_entry+0x18/0x1c)
> [ 67.112867] [<c015c5e0>] (cpu_startup_entry) from [<401028ac>]
> (0x401028ac)
> [ 67.114359] cros-ec-i2c 104-001e: bad packet checksum
> [ 67.322533] call 104-001e+ returned 0 after 23925980 usecs
> [ 67.328468] calling cros-ec-dev.3.auto+ @ 1610, parent: 104-001e
> [ 67.335024] call cros-ec-dev.3.auto+ returned 0 after 1 usecs
> [ 67.341192] calling
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+ @ 1610,
> parent: 104-001e
> [ 67.351704] call
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller+
> returned 0 after 1 usecs
> [ 67.361881] calling input1+ @ 1610, parent:
> i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller
> [ 67.372254] call input1+ returned 0 after 3 usecs
> [ 67.377450] calling tps65090-pmic+ @ 1610, parent: 104-0048
> [ 67.383604] call tps65090-pmic+ returned 0 after 1 usecs
> [ 67.389409] calling tps65090-charger+ @ 1610, parent: 104-0048
> [ 67.395783] call tps65090-charger+ returned 0 after 1 usecs
> [ 67.401811] calling cpufreq-dt+ @ 1610, parent: platform
> [ 67.407613] call cpufreq-dt+ returned 0 after 1 usecs
> [ 67.413094] calling snd-soc-dummy+ @ 1610, parent: platform
> [ 67.419141] call snd-soc-dummy+ returned 0 after 1 usecs
> [ 67.424949] calling backlight+ @ 1610, parent: platform
> [ 67.430781] call backlight+ returned 0 after 206 usecs
> [ 67.436251] calling backlight+ @ 1610, parent: backlight
> [ 67.441954] call backlight+ returned 0 after 3 usecs
> [ 67.447256] calling hdmi-audio-codec.4.auto+ @ 1610, parent:
> 14530000.hdmi
> [ 67.454596] call hdmi-audio-codec.4.auto+ returned 0 after 1 usecs
> [ 67.461098] calling panel+ @ 1610, parent: platform
> [ 67.466391] call panel+ returned 0 after 1 usecs
> [ 67.471315] calling sound+ @ 1610, parent: platform
> [ 67.477289] call sound+ returned 0 after 673 usecs
> [ 67.482595] calling input2+ @ 1610, parent: gpio-keys
> [ 67.488097] call input2+ returned 0 after 2 usecs
> [ 67.498847] OOM killer enabled.
> [ 67.502391] Restarting tasks ... done.
>
>
>
> > ---
> > drivers/input/keyboard/cros_ec_keyb.c | 30 ++++++++++-----------------
> > 1 file changed, 11 insertions(+), 19 deletions(-)
> >
> > diff --git a/drivers/input/keyboard/cros_ec_keyb.c
> b/drivers/input/keyboard/cros_ec_keyb.c
> > index 489ddd37bd4ee..c5e32544130dc 100644
> > --- a/drivers/input/keyboard/cros_ec_keyb.c
> > +++ b/drivers/input/keyboard/cros_ec_keyb.c
> > @@ -242,19 +242,17 @@ static int cros_ec_keyb_work(struct notifier_block
> *nb,
> > u32 val;
> > unsigned int ev_type;
> >
> > + /*
> > + * If not wake enabled, discard key state changes during
> > + * suspend. Switches will be re-checked in
> > + * cros_ec_keyb_resume() to be sure nothing is lost.
> > + */
> > + if (queued_during_suspend && !device_may_wakeup(ckdev->dev))
> > + return NOTIFY_OK;
> > +
> > switch (ckdev->ec->event_data.event_type) {
> > case EC_MKBP_EVENT_KEY_MATRIX:
> > - if (device_may_wakeup(ckdev->dev)) {
> > - pm_wakeup_event(ckdev->dev, 0);
> > - } else {
> > - /*
> > - * If keyboard is not wake enabled, discard key
> state
> > - * changes during suspend. Switches will be
> re-checked
> > - * in cros_ec_keyb_resume() to be sure nothing is
> lost.
> > - */
> > - if (queued_during_suspend)
> > - return NOTIFY_OK;
> > - }
> > + pm_wakeup_event(ckdev->dev, 0);
> >
> > if (ckdev->ec->event_size != ckdev->cols) {
> > dev_err(ckdev->dev,
> > @@ -268,10 +266,7 @@ static int cros_ec_keyb_work(struct notifier_block
> *nb,
> > break;
> >
> > case EC_MKBP_EVENT_SYSRQ:
> > - if (device_may_wakeup(ckdev->dev))
> > - pm_wakeup_event(ckdev->dev, 0);
> > - else if (queued_during_suspend)
> > - return NOTIFY_OK;
> > + pm_wakeup_event(ckdev->dev, 0);
> >
> > val =
> get_unaligned_le32(&ckdev->ec->event_data.data.sysrq);
> > dev_dbg(ckdev->dev, "sysrq code from EC: %#x\n", val);
> > @@ -280,10 +275,7 @@ static int cros_ec_keyb_work(struct notifier_block
> *nb,
> >
> > case EC_MKBP_EVENT_BUTTON:
> > case EC_MKBP_EVENT_SWITCH:
> > - if (device_may_wakeup(ckdev->dev))
> > - pm_wakeup_event(ckdev->dev, 0);
> > - else if (queued_during_suspend)
> > - return NOTIFY_OK;
> > + pm_wakeup_event(ckdev->dev, 0);
> >
> > if (ckdev->ec->event_data.event_type ==
> EC_MKBP_EVENT_BUTTON) {
> > val = get_unaligned_le32(
> >
>
> Best regards
> --
> Marek Szyprowski, PhD
> Samsung R&D Institute Poland
>
>
[-- Attachment #2: Type: text/html, Size: 61802 bytes --]
^ permalink raw reply
* Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.
From: Dmitry Torokhov @ 2018-08-03 16:07 UTC (permalink / raw)
To: Ravi Chandra Sadineni
Cc: Marek Szyprowski, Ravi Chandra Sadineni, Dmitry Torokhov,
Todd Broch, lkml, linux-input@vger.kernel.org, linux-samsung-soc
In-Reply-To: <CAEZbON7qLheHFuU6zwArCz=CG03JvnFjcehBGjE4RqROYrMLhQ@mail.gmail.com>
On Fri, Aug 3, 2018 at 8:51 AM Ravi Chandra Sadineni
<ravisadineni@chromium.org> wrote:
>
> Hi Marek,
>
> Can you please give me little more context ? Snow is still on 3.8.11. This patch is not backported to 3.8.11. Are you trying to flash a different kernel on snow?
>
Ravi, from upstream perspective what kernel Google uses when shipping
Snow is completely immaterial. Mainline is supposed to work equally
well on all devices.
Thanks.
--
Dmitry
^ permalink raw reply
* Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.
From: Ravi Chandra Sadineni @ 2018-08-03 16:53 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: m.szyprowski, Ravi Chandra Sadineni, Dmitry Torokhov, Todd Broch,
linux-kernel, linux-input, linux-samsung-soc
In-Reply-To: <CAKdAkRQG08d_duPiKFi_=xUNO93c0Rcw9kpaYFFJahjJM-NdGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Understood. I am trying to reproduce this issue locally. Wanted to know the
version of the kernel so I can give a try. Marek, can you please confirm
the kernel version.
Thanks,
On Fri, Aug 3, 2018 at 9:08 AM Dmitry Torokhov <dmitry.torokhov@gmail.com>
wrote:
> On Fri, Aug 3, 2018 at 8:51 AM Ravi Chandra Sadineni
> <ravisadineni@chromium.org> wrote:
> >
> > Hi Marek,
> >
> > Can you please give me little more context ? Snow is still on 3.8.11.
> This patch is not backported to 3.8.11. Are you trying to flash a different
> kernel on snow?
> >
>
> Ravi, from upstream perspective what kernel Google uses when shipping
> Snow is completely immaterial. Mainline is supposed to work equally
> well on all devices.
>
> Thanks.
>
> --
> Dmitry
>
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
^ permalink raw reply
* [PATCH] Input: raydium_i2c_ts - use true and false for boolean values
From: Gustavo A. R. Silva @ 2018-08-05 0:34 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input, linux-kernel, Gustavo A. R. Silva
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
---
drivers/input/touchscreen/raydium_i2c_ts.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/raydium_i2c_ts.c b/drivers/input/touchscreen/raydium_i2c_ts.c
index d1c09e6..c89853a 100644
--- a/drivers/input/touchscreen/raydium_i2c_ts.c
+++ b/drivers/input/touchscreen/raydium_i2c_ts.c
@@ -466,7 +466,7 @@ static bool raydium_i2c_boot_trigger(struct i2c_client *client)
}
}
- return 0;
+ return false;
}
static bool raydium_i2c_fw_trigger(struct i2c_client *client)
@@ -492,7 +492,7 @@ static bool raydium_i2c_fw_trigger(struct i2c_client *client)
}
}
- return 0;
+ return false;
}
static int raydium_i2c_check_path(struct i2c_client *client)
--
2.7.4
^ permalink raw reply related
* Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.
From: Marek Szyprowski @ 2018-08-06 5:29 UTC (permalink / raw)
To: Ravi Chandra Sadineni, Dmitry Torokhov
Cc: Ravi Chandra Sadineni, Dmitry Torokhov, Todd Broch, linux-kernel,
linux-input, linux-samsung-soc
In-Reply-To: <CAEZbON4O0X8Fo6eAbmPOSiB1_Tw7x+Ox3ROoGfZQn72uQGQLkg@mail.gmail.com>
Hi Ravi,
On 2018-08-03 18:53, Ravi Chandra Sadineni wrote:
> Understood. I am trying to reproduce this issue locally. Wanted to
> know the version of the kernel so I can give a try. Marek, can you
> please confirm the kernel version.
>
Yes, sorry for the missing context, I was in hurry writing the report and
I wanted to send it before leaving the office. I'm testing mainline on Snow
with exynos_defconfig.
Suspend/resume is partially broken already with mainline, but if you disable
CPUfreq support, it works fine on Linux v4.17.
I've posted CPUfreq related fixes here if you are interested:
https://patchwork.kernel.org/patch/10554607/
https://patchwork.kernel.org/patch/10554603/
The issue with cros_ec_keyb patch appears first on Linux v4.18-rc1, which is
the first release with that patch. Linux -next from 20180803, which has
a few
more patches for cros_ec_keyb suffers from the same issue.
>
> On Fri, Aug 3, 2018 at 9:08 AM Dmitry Torokhov
> <dmitry.torokhov@gmail.com <mailto:dmitry.torokhov@gmail.com>> wrote:
>
> On Fri, Aug 3, 2018 at 8:51 AM Ravi Chandra Sadineni
> <ravisadineni@chromium.org <mailto:ravisadineni@chromium.org>> wrote:
> >
> > Hi Marek,
> >
> > Can you please give me little more context ? Snow is still on
> 3.8.11. This patch is not backported to 3.8.11. Are you trying to
> flash a different kernel on snow?
> >
>
> Ravi, from upstream perspective what kernel Google uses when shipping
> Snow is completely immaterial. Mainline is supposed to work equally
> well on all devices.
>
> Thanks.
>
> --
> Dmitry
>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox