an opt-out parameter
so there's an emergency valve for people who are deliberately running
old firmware, or as an escape hatch in case of unforeseen regressions.
Signed-off-by: Evan Green
---
drivers/firmware/google/gsmi.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-
On Sun, Jan 17, 2021 at 3:54 AM Wolfram Sang wrote:
>
> On Wed, Nov 18, 2020 at 03:40:25PM -0800, Evan Green wrote:
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> >
On Tue, Jan 5, 2021 at 2:25 AM Wolfram Sang wrote:
>
> On Fri, Nov 20, 2020 at 10:59:12AM -0800, Evan Green wrote:
> > On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
> > wrote:
> > >
> > > On Thu, Nov 19, 2020 at 1:40 AM Evan Green wrote:
> > >
Very sorry to ping. Is there anything I can do to help get this reviewed?
-Evan
On Mon, Nov 30, 2020 at 11:11 AM Evan Green wrote:
>
> Hi Andy, Peter,
>
> On Fri, Nov 20, 2020 at 10:59 AM Evan Green wrote:
> >
> > On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
> &
On Sat, Nov 21, 2020 at 9:43 PM Bjorn Andersson
wrote:
>
> A graceful shutdown of the Qualcomm remote processors where
> traditionally performed by invoking a shared memory state signal and
> waiting for the associated ack.
>
> This was later superseded by the "sysmon" mechanism, where some form o
Hi Andy, Peter,
On Fri, Nov 20, 2020 at 10:59 AM Evan Green wrote:
>
> On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
> wrote:
> >
> > On Thu, Nov 19, 2020 at 1:40 AM Evan Green wrote:
> > >
> > > Enable i2c-mux-gpio devices to be defined via ACPI. T
On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
wrote:
>
> On Thu, Nov 19, 2020 at 1:40 AM Evan Green wrote:
> >
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> > reg
i2c-mux-gpio is
instantiated.
Signed-off-by: Evan Green
---
Changes in v3:
- Update commit message again (Peter)
- Added missing \n (Peter)
- adr64 overflow check (Peter)
- Don't initialize child (Peter)
- Limit scope of dev_handle (Peter)
Changes in v2:
- Make it compile properly when
Factor out &pdev->dev into a local variable in preparation for
the ACPI enablement of this function, which will utilize the variable
more.
Signed-off-by: Evan Green
---
Changes in v3:
- Introduced minor &pdev->dev to dev refactor (Peter)
drivers/i2c/muxes/i2c-mux-gpio.c | 5
r)
- Limit scope of dev_handle (Peter)
Changes in v2:
- Make it compile properly when !CONFIG_ACPI (Randy)
- Update commit message regarding i2c-parent (Peter)
Evan Green (2):
i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt()
i2c: i2c-mux-gpio: Enable this driver in ACPI land
drive
ntel Jasper Lake pin controller
support")
Cc: sta...@vger.kernel.org
Signed-off-by: Evan Green
---
Changes in v2:
- Commit text rewording [Andy]
drivers/pinctrl/intel/pinctrl-jasperlake.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/intel/pinctrl-jasper
On Wed, Nov 11, 2020 at 2:13 PM Andy Shevchenko
wrote:
>
> On Tue, Nov 10, 2020 at 02:49:49PM -0800, Evan Green wrote:
> > GPIOs that attempt to use interrupts get thwarted with a message like:
> > "pin 161 cannot be used as IRQ" (for instance with SD_CD). This is be
On Tue, Nov 10, 2020 at 3:48 PM Andy Shevchenko
wrote:
>
>
>
> On Wednesday, November 11, 2020, Evan Green wrote:
>>
>> GPIOs that attempt to use interrupts get thwarted with a message like:
>> "pin 161 cannot be used as IRQ" (for instance with SD_CD
GPIOs that attempt to use interrupts get thwarted with a message like:
"pin 161 cannot be used as IRQ" (for instance with SD_CD). This is because
the JSL_HOSTSW_OWN offset is incorrect, so every GPIO looks like it's
owned by ACPI.
Signed-off-by: Evan Green
Fixes: e278dcb7048b1 (
On Tue, Oct 20, 2020 at 11:37 AM Evan Green wrote:
>
> On Thu, Oct 15, 2020 at 11:28 AM Sibi Sankar wrote:
> >
> > The modem firmware memory requirements vary between 32M/140M on
> > no-lte/lte skus respectively, so fixup the modem memory region
> > to reflect th
On Thu, Oct 29, 2020 at 5:08 AM Srinivas Kandagatla
wrote:
>
> Thanks Evan for doing this,
>
> On 29/10/2020 00:28, Evan Green wrote:
> > Introduce support into the nvmem core for arrays of register ranges
> > that should not result in actual device access. For these reg
Add SoC-specific compatible strings so that data can be attached
to it in the driver.
Signed-off-by: Evan Green
---
Changes in v3:
- Fixed example (Doug and rob-bot)
Changes in v2:
- Add other soc compatible strings (Doug)
- Fix compatible string definition (Doug)
.../devicetree/bindings
Add the soc-specific compatible string so that it can be matched
more specifically now that the driver cares which SoC it's on.
Signed-off-by: Evan Green
Reviewed-by: Douglas Anderson
---
(no changes since v1)
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 +-
1 file changed, 1 insertion(
regions are protected
from access by Linux because they contain secret info to another part
of the system (like an integrated modem).
Signed-off-by: Evan Green
---
Changes in v3:
- Use min()/max() macros instead of defining my own (Doug)
- Comment changes to indicate sorting (Doug)
- Add function
Some fuse ranges are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Use the newly
introduced per-soc compatible string, and the newly introduced
nvmem keepout support to attach the set of regions
we should not access.
Signed-off-by: Evan Green
compatible strings (Doug)
- Fix compatible string definition (Doug)
- Introduced keepout regions into the core (Srini)
- Use new core support in qfprom (Srini)
Evan Green (4):
dt-bindings: nvmem: Add soc qfprom compatible strings
arm64: dts: qcom: sc7180: Add soc-specific qfprom compat string
On Wed, Oct 21, 2020 at 2:41 PM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Oct 16, 2020 at 12:27 PM Evan Green wrote:
> >
> > Add SoC-specific compatible strings so that data can be attached
> > to it in the driver.
> >
> > Signed-off-by: Evan Green
>
On Wed, Oct 21, 2020 at 2:41 PM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Oct 16, 2020 at 12:27 PM Evan Green wrote:
> >
> > Introduce support into the nvmem core for arrays of register ranges
> > that should not result in actual device access. For these regions a
&
On Mon, Oct 19, 2020 at 9:53 AM Evan Green wrote:
>
> On Sun, Oct 18, 2020 at 11:58 AM Andy Shevchenko
> wrote:
> >
> > On Sat, Oct 17, 2020 at 8:30 AM Evan Green wrote:
> > >
> > > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
On Thu, Oct 15, 2020 at 11:28 AM Sibi Sankar wrote:
>
> The modem firmware memory requirements vary between 32M/140M on
> no-lte/lte skus respectively, so fixup the modem memory region
> to reflect the requirements.
>
> Signed-off-by: Sibi Sankar
Reviewed-by: Evan Green
On Sun, Oct 18, 2020 at 11:58 AM Andy Shevchenko
wrote:
>
> On Sat, Oct 17, 2020 at 8:30 AM Evan Green wrote:
> >
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> > reg
r)
- Limit scope of dev_handle (Peter)
Changes in v2:
- Make it compile properly when !CONFIG_ACPI (Randy)
- Update commit message regarding i2c-parent (Peter)
Evan Green (2):
i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt()
i2c: i2c-mux-gpio: Enable this driver in ACPI land
drive
Factor out &pdev->dev into a local variable in preparation for
the ACPI enablement of this function, which will utilize the variable
more.
Signed-off-by: Evan Green
---
Changes in v3:
- Introduced minor &pdev->dev to dev refactor (Peter)
drivers/i2c/muxes/i2c-mux-gpio.c | 5
i2c-mux-gpio is
instantiated.
Signed-off-by: Evan Green
---
Changes in v3:
- Update commit message again (Peter)
- Added missing \n (Peter)
- adr64 overflow check (Peter)
- Don't initialize child (Peter)
- Limit scope of dev_handle (Peter)
Changes in v2:
- Make it compile properly when
Some fuse ranges are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Use the newly
introduced per-soc compatible string, and the newly introduced
nvmem keepout support to attach the set of regions
we should not access.
Signed-off-by: Evan Green
Add the soc-specific compatible string so that it can be matched
more specifically now that the driver cares which SoC it's on.
Signed-off-by: Evan Green
Reviewed-by: Douglas Anderson
---
(no changes since v1)
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 +-
1 file changed, 1 insertion(
regions are protected
from access by Linux because they contain secret info to another part
of the system (like an integrated modem).
Signed-off-by: Evan Green
---
Changes in v2:
- Introduced keepout regions into the core (Srini)
drivers/nvmem/core.c | 95
Add SoC-specific compatible strings so that data can be attached
to it in the driver.
Signed-off-by: Evan Green
---
Changes in v2:
- Add other soc compatible strings (Doug)
- Fix compatible string definition (Doug)
.../devicetree/bindings/nvmem/qcom,qfprom.yaml | 13 -
1
SErrors when usermode
accesses certain registers.
Changes in v2:
- Add other soc compatible strings (Doug)
- Fix compatible string definition (Doug)
- Introduced keepout regions into the core (Srini)
- Use new core support in qfprom (Srini)
Evan Green (4):
dt-bindings: nvmem: Add soc qfprom
On Thu, Oct 15, 2020 at 3:23 AM Peter Rosin wrote:
>
> Hi!
>
> On 2020-10-15 03:02, Evan Green wrote:
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> > reg property tra
c-mux-gpio is
instantiated.
Signed-off-by: Evan Green
---
Changes in v2:
- Make it compile properly when !CONFIG_ACPI (Randy)
- Update commit message regarding i2c-parent (Peter)
drivers/i2c/muxes/i2c-mux-gpio.c | 103 ++-
1 file changed, 75 insertions(+), 28
On Sat, Oct 10, 2020 at 10:03 AM Peter Rosin wrote:
>
> Hi!
>
> On 2020-10-10 00:43, Evan Green wrote:
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> > reg property
uired, it can be added later.
Signed-off-by: Evan Green
---
drivers/i2c/muxes/i2c-mux-gpio.c | 77 +---
1 file changed, 50 insertions(+), 27 deletions(-)
diff --git a/drivers/i2c/muxes/i2c-mux-gpio.c b/drivers/i2c/muxes/i2c-mux-gpio.c
index 4effe563e9e8d..f195e95e
On Fri, Oct 2, 2020 at 3:20 PM Doug Anderson wrote:
>
> Hi,
>
> On Tue, Sep 29, 2020 at 1:58 PM Evan Green wrote:
> >
> > Add an SoC-specific compatible string so that data can be attached
> > to it in the driver.
> >
> > Signed-off-by: Evan Green
On Thu, Oct 1, 2020 at 9:30 AM Srinivas Kandagatla
wrote:
>
>
>
> On 01/10/2020 17:27, Evan Green wrote:
> > On Thu, Oct 1, 2020 at 7:17 AM Srinivas Kandagatla
> > wrote:
> >>
> >> Hi Evan,
> >>
> >> On 29/09/2020 21:58, Evan Green wrot
On Thu, Oct 1, 2020 at 7:17 AM Srinivas Kandagatla
wrote:
>
> Hi Evan,
>
> On 29/09/2020 21:58, Evan Green wrote:
> > Some fuse ranges are protected by the XPU such that the AP cannot
> > access them. Attempting to do so causes an SError. Use the newly
> > introduce
Some fuse ranges are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Use the newly
introduced per-soc compatible string to attach the set of regions
we should not access. Then tiptoe around those regions.
Signed-off-by: Evan Green
---
drivers
Certain fuses are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Introduce an
SoC-specific compatible string, and then use that to determine
which fuse regions to present as Read as Zero / Write Ignore.
Evan Green (3):
dt-bindings: nvmem: Add
Add the soc-specific compatible string so that it can be matched
more specifically now that the driver cares which SoC it's on.
Signed-off-by: Evan Green
---
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/s
Add an SoC-specific compatible string so that data can be attached
to it in the driver.
Signed-off-by: Evan Green
---
Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/nvmem/qcom
(). IRQ handling of spinlocks should be
consistent to avoid the panic notifier deadlocking because it's
sitting on the thread that's already got the lock via _request_stop().
Found via lockdep.
Fixes: 50e99641413e7 ("soc: qcom: smp2p: Qualcomm Shared Memory Point to Point")
Signe
> re-const of the data member when it is extracted in qcom_icc_set().
>
> Cc: Sibi Sankar
> Cc: Evan Green
> Signed-off-by: Stephen Boyd
Reviewed-by: Evan Green
r disabled
> paths/requests as zero.
>
> Signed-off-by: Matthias Kaehlcke
Looks good to me. I briefly mulled over the idea of showing the
disabled flag as a separate column, but I can't really think of how
that would be useful.
Reviewed-by: Evan Green
On Mon, Aug 17, 2020 at 11:33 AM Raj, Ashok wrote:
>
> Hi Evan
>
> Some details below,
>
> On Mon, Aug 17, 2020 at 11:12:17AM -0700, Evan Green wrote:
> > Hi Ashok,
> > Thank you, Srikanth, and Sukumar for some very impressive debugging here.
> >
> >
hok Raj
>
> To: linux-kernel@vger.kernel.org
> To: Thomas Gleixner
> Cc: Sukumar Ghorai
> Cc: Srikanth Nandamuri
> Cc: Evan Green
> Cc: Mathias Nyman
> Cc: Bjorn Helgaas
> Cc: sta...@vger.kernel.org
> ---
> arch/x86/kernel/smpboot.c | 11 +--
>
On Fri, Jul 10, 2020 at 12:24 PM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 10, 2020 at 12:03 PM Evan Green wrote:
> >
> > On Fri, Jul 10, 2020 at 11:19 AM Doug Anderson
> > wrote:
> > >
> > > Hi,
> > >
> > > On Fri, Jul 10,
On Fri, Jul 10, 2020 at 11:28 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 10, 2020 at 10:46 AM Evan Green wrote:
> >
> > On Fri, Jun 26, 2020 at 1:01 PM Douglas Anderson
> > wrote:
> > >
> > > The geni serial driver had a rule that we'
On Fri, Jul 10, 2020 at 11:19 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 10, 2020 at 10:39 AM Evan Green wrote:
> >
> > On Fri, Jun 26, 2020 at 1:01 PM Douglas Anderson
> > wrote:
> > >
> > > The geni serial driver had the rather sketchy h
On Fri, Jun 26, 2020 at 1:01 PM Douglas Anderson wrote:
>
> The geni serial driver had a rule that we'd only use 1 byte per FIFO
> word for the TX FIFO if we were being used for the serial console.
> This is ugly and a bit of a pain. It's not too hard to fix, so fix
> it.
>
> Signed-off-by: Dougl
On Fri, Jun 26, 2020 at 1:01 PM Douglas Anderson wrote:
>
> The geni serial driver had the rather sketchy hack in it where it
> would adjust the number of bytes per RX FIFO word from 4 down to 1 if
> it detected that CONFIG_CONSOLE_POLL was enabled (for kgdb) and this
> was a console port (defined
On Thu, May 21, 2020 at 9:19 AM Evan Green wrote:
>
> On Tue, May 19, 2020 at 8:57 PM Rakesh Pillai wrote:
> >
> > Add device node for the ath10k SNOC platform driver probe
> > and add resources required for WCN3990 on sc7180 soc.
> >
> > Signed-off-by: Rakesh
(). IRQ handling of spinlocks should be
consistent to avoid the panic notifier deadlocking because it's
sitting on the thread that's already got the lock via _request_stop().
Found via lockdep.
Fixes: 50e99641413e7 ("soc: qcom: smp2p: Qualcomm Shared Memory Point to Point")
Signe
On Mon, Jun 8, 2020 at 4:39 AM Kalle Valo wrote:
>
> Evan Green writes:
>
> > ath10k_htt_tx_free_msdu_id() has a lockdep assertion that htt->tx_lock
> > is held. Acquire the lock in a couple of error paths when calling that
> > function to ensure this c
k: Add support for htt_data_tx_desc_64
descriptor")
Signed-off-by: Evan Green
---
drivers/net/wireless/ath/ath10k/htt_tx.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/htt_tx.c
b/drivers/net/wireless/ath/ath10k/htt_tx.c
index e9d12ea708b62..e8c
On Tue, Jun 2, 2020 at 10:29 PM Sibi Sankar wrote:
>
> Evan,
> Thanks for taking time to review
> the series.
>
> On 2020-06-02 23:14, Evan Green wrote:
> > On Tue, Jun 2, 2020 at 9:33 AM Sibi Sankar
> > wrote:
> >>
> >> Sometimes the stop tr
On Tue, Jun 2, 2020 at 9:33 AM Sibi Sankar wrote:
>
> Sometimes the stop triggers a watchdog rather than a stop-ack. Update
> the running state to false on requesting stop to skip the watchdog
> instead.
>
> Error Logs:
> $ echo stop > /sys/class/remoteproc/remoteproc0/state
> ipa 1e4.ipa: rec
p.
Reviewed-by: Evan Green
On Tue, May 19, 2020 at 8:57 PM Rakesh Pillai wrote:
>
> Add device node for the ath10k SNOC platform driver probe
> and add resources required for WCN3990 on sc7180 soc.
>
> Signed-off-by: Rakesh Pillai
Reviewed-by: Evan Green
On Wed, May 20, 2020 at 6:03 PM Stephen Boyd wrote:
>
> The modem node has an address of 408 and thus should come after tlmm
> and before gpu. Move the node to the right place to maintainer proper
> address sort order.
>
> Cc: Evan Green
> Cc: Sibi Sankar
> Fixes: e
On Sun, May 17, 2020 at 3:47 AM Rakesh Pillai wrote:
>
> Add device node for the ath10k SNOC platform driver probe
> and add resources required for WCN3990 on sc7180 soc.
>
> Signed-off-by: Rakesh Pillai
> ---
> Changes from v8:
> - Removed the qcom,msa-fixed-perm
> ---
> arch/arm64/boot/dts/qco
On Thu, Mar 5, 2020 at 8:28 PM Alex Elder wrote:
>
> This series presents the driver for the Qualcomm IP Accelerator (IPA).
>
> This is version 2 of this updated series. It includes the following
> small changes since the previous version:
> - Now based on net-next instead of v5.6-rc
> - Conf
>
> Sibi Sankar (2):
> dt-bindings: remoteproc: qcom: Replace halt-nav with spare-regs
> remoteproc: qcom_q6v5_mss: Drop accesses to MPSS PERPH register space
I haven't tested things in the "production" fuse configuration yet,
but in my current configuration I've
ies in my inbox.
Tested-by: Evan Green
from memory-region
> arm64: dts: qcom: sc7180: Update reserved memory map
> arm64: dts: qcom: sc7180: Add Q6V5 MSS node
> arm64: dts: qcom: sc7180: Update Q6V5 MSS node
Tested-by: Evan Green
On Mon, Apr 27, 2020 at 6:11 PM Dmitry Torokhov
wrote:
>
> On Mon, Apr 27, 2020 at 02:55:48PM -0700, Evan Green wrote:
> > Fix a use-after-free noticed by running with KASAN enabled. If
> > rmi_irq_fn() is run twice in a row, then rmi_f11_attention() (among
> > others)
On Wed, Oct 9, 2019 at 10:46 AM Bjorn Andersson
wrote:
>
> On Wed 09 Oct 09:01 PDT 2019, Evan Green wrote:
>
> > On Tue, Oct 8, 2019 at 6:58 PM Stephen Boyd wrote:
> > >
> > > Quoting Bjorn Andersson (2019-10-08 16:55:04)
> > > > On
On Tue, Oct 8, 2019 at 6:58 PM Stephen Boyd wrote:
>
> Quoting Bjorn Andersson (2019-10-08 16:55:04)
> > On Tue 08 Oct 16:45 PDT 2019, Stephen Boyd wrote:
> > > @@ drivers/soc/qcom/llcc-slice.c
> > >
> > > static struct llcc_drv_data *drv_data = (void *) -EPROBE_DEFER;
> > >
> > > --
7 ("soc: qcom: Add broadcast base for Last Level Cache
> Controller (LLCC)")
> Cc: Venkata Narendra Kumar Gutta
> Cc: Evan Green
> Signed-off-by: Stephen Boyd
Reviewed-by: Evan Green
_mask
to avoid calling handle_nested_irq() on IRQs that have not yet been
set up.
Signed-off-by: Evan Green
---
drivers/input/rmi4/rmi_driver.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
index 772493b
t; Fixes: 7f9c136216c7 ("soc: qcom: Add broadcast base for Last Level Cache
> Controller (LLCC)")
> Cc: Venkata Narendra Kumar Gutta
> Cc: Evan Green
> Signed-off-by: Stephen Boyd
> ---
> drivers/soc/qcom/llcc-slice.c | 14 +++---
> 1 file changed, 7 inse
On Thu, Oct 3, 2019 at 11:56 AM Stephen Boyd wrote:
>
> Quoting Evan Green (2019-09-18 12:37:34)
> > On Tue, Sep 10, 2019 at 9:09 AM Stephen Boyd wrote:
> > >
> > > @@ -53,6 +60,9 @@ static void *try_ram_remap(resource_size_t offset,
> > > size_t size,
&g
d fix separately.
Signed-off-by: Evan Green
---
Changes in v3:
- Move enable_irq to the beginning of resume (Dmitry)
Changes in v2:
- Enable and disable unconditionally (Dmitry)
drivers/input/touchscreen/atmel_mxt_ts.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/touchs
On Fri, Sep 27, 2019 at 5:16 PM Dmitry Torokhov
wrote:
>
> Hi Evan,
>
> On Tue, Sep 24, 2019 at 02:52:38PM -0700, Evan Green wrote:
> > Across suspend and resume, we are seeing error messages like the following:
> >
> > atmel_mxt_ts i2c-PRP0001:00: __mxt_read_
d fix separately.
Signed-off-by: Evan Green
---
Changes in v2:
- Enable and disable unconditionally (Dmitry)
drivers/input/touchscreen/atmel_mxt_ts.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
pending, but the interrupt is serviced before both the driver and
the underlying I2C bus have been resumed. This causes EREMOTEIO errors.
Disable the IRQ in suspend, and re-enable it if it was previously enabled
in resume.
Signed-off-by: Evan Green
---
drivers/input/touchscreen/atmel_mxt_ts.c
; for random code to corrupt the database and change the contents.
>
> Cc: Evan Green
> Cc: Rob Herring
> Cc: Bjorn Andersson
> Cc: Andy Gross
> Cc: Will Deacon
> Cc: Catalin Marinas
> Cc: Dan Williams
> Reviewed-by: Bjorn Andersson
> Signed-off-by: Stephen Boyd
&g
llows us to map reserved memory regions as read-only. This way, we're
> less likely to see these special memory regions become corrupted by
> stray writes to them.
>
> Cc: Evan Green
> Cc: Rob Herring
> Cc: Bjorn Andersson
> Cc: Andy Gross
> Cc: Will Deacon
> Cc: Cat
Hi Sibi,
On Wed, Aug 7, 2019 at 4:24 AM Sibi Sankar wrote:
>
> On some Qualcomm SoCs, Operating State Manager (OSM) controls the
> resources of scaling L3 caches. Add a driver to handle bandwidth
> requests to OSM L3 from CPU/GPU.
>
> Signed-off-by: Sibi Sankar
This looks good to me, just a cou
> Signed-off-by: Georgi Djakov
Reviewed-by: Evan Green
On Fri, Aug 9, 2019 at 5:13 AM Georgi Djakov wrote:
>
> From: David Dai
>
> Add support for wake and sleep commands by using a tag to indicate
> whether or not the aggregate and set requests fall into execution
> state specific bucket.
>
> Signed-off-by: David Dai
> Signed-off-by: Georgi Djakov
of this for now is that it will significantly simplify the code
> in provider drivers.
>
> Suggested-by: Evan Green
> Signed-off-by: Georgi Djakov
Reviewed-by: Evan Green
river to do the aggregation based on this state.
>
> Introduce icc_set_tag() function that will allow the consumers to append
> an optional tag to each path. The aggregation of these tagged paths is
> platform specific.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Evan Green
of this for now is that it will significantly simplify the code
> in provider drivers.
>
> Suggested-by: Evan Green
> Signed-off-by: Georgi Djakov
Thanks Georgi, I like it! We should confirm that it actually does
allow David to remove the sum_avg_cached and max_peak_cached sh
On Tue, Jul 30, 2019 at 5:37 PM David Dai wrote:
>
>
> On 7/30/2019 3:54 PM, Evan Green wrote:
> > On Thu, Jul 18, 2019 at 10:59 AM David Dai wrote:
> >> On 7/16/2019 1:15 PM, Evan Green wrote:
> >>> On Mon, Jul 15, 2019 at 4:34 PM David Dai
> >>
On Thu, Jul 18, 2019 at 10:59 AM David Dai wrote:
>
> On 7/16/2019 1:15 PM, Evan Green wrote:
> > On Mon, Jul 15, 2019 at 4:34 PM David Dai wrote:
> >> Hi Evan,
> >>
> >> Thanks for the continued help in reviewing these patches!
> > No problem. I want
; On 7/11/2019 10:06 AM, Evan Green wrote:
> > Hi Georgi and David,
> >
> > On Tue, Jun 18, 2019 at 2:17 AM Georgi Djakov
> > wrote:
> >> From: David Dai
> >>
> >> Add support for wake and sleep commands by using a tag to indicate
> >> wh
On Fri, Jul 12, 2019 at 10:04 AM Evan Green wrote:
>
> On Mon, Jul 1, 2019 at 6:41 AM Enric Balletbo i Serra
> wrote:
> >
> >
> >
> > On 1/7/19 8:01, Lee Jones wrote:
> > > On Thu, 27 Jun 2019, Enric Balletbo Serra wrote:
> > >
> > >&
On Mon, Jul 1, 2019 at 6:41 AM Enric Balletbo i Serra
wrote:
>
>
>
> On 1/7/19 8:01, Lee Jones wrote:
> > On Thu, 27 Jun 2019, Enric Balletbo Serra wrote:
> >
> >> Hi Evan, Lee,
> >>
> >> Missatge de Evan Green del dia dj., 27 de juny
> &g
Hi Georgi and David,
On Tue, Jun 18, 2019 at 2:17 AM Georgi Djakov wrote:
>
> From: David Dai
>
> Add support for wake and sleep commands by using a tag to indicate
> whether or not the aggregate and set requests fall into execution
> state specific bucket.
>
> Signed-off-by: David Dai
> Signed
Hi Georgi and David,
On Tue, Jun 18, 2019 at 2:17 AM Georgi Djakov wrote:
>
> Consumers may have use cases with different bandwidth requirements based
> on the system or driver state. The consumer driver can append a specific
> tag to the path and pass this information to the interconnect platfor
that a very old read from that
function doesn't end up clobbering a later update.
Fixes: ed180abba7f1 ("ALSA: hda: Fix race between creating and refreshing sysfs
entries")
Signed-off-by: Evan Green
---
Changes in v3:
- Moved locking back into callers (Takashi)
- Combined update_w
On Mon, Jul 1, 2019 at 7:09 AM Takashi Iwai wrote:
>
> On Wed, 26 Jun 2019 23:22:19 +0200,
> Evan Green wrote:
> >
> > The widget_mutex was introduced to serialize callers to
> > hda_widget_sysfs_{re}init. However, its protection of the sysfs widget array
> >
For ECs that support it, the EC returns the number of slp_s0
transitions and whether or not there was a timeout in the resume
response. Expose the last resume result to usermode via debugfs so
that usermode can detect and report S0ix timeouts.
Signed-off-by: Evan Green
---
Changes in v3
On Thu, Jun 27, 2019 at 9:42 AM Enric Balletbo i Serra
wrote:
>
> Hi Evan,
>
> On 27/6/19 18:07, Evan Green wrote:
> > On Wed, Jun 26, 2019 at 1:55 PM Enric Balletbo i Serra
> > wrote:
> >>
> >> Hi Evan,
> >>
> >> Two few comments a
On Wed, Jun 26, 2019 at 10:26 PM Takashi Iwai wrote:
>
> On Wed, 26 Jun 2019 23:59:33 +0200,
> Evan Green wrote:
> >
> > On Wed, Jun 26, 2019 at 2:16 PM Takashi Iwai wrote:
> > >
> > > On Wed, 26 Jun 2019 22:34:28 +0200,
> > > Evan Green wrote:
1 - 100 of 506 matches
Mail list logo
