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(-)
--
Are you looking for a loan? How much do you need as a loan and the
duration time you can pay it back? thanks, Mr. Green Rodriguez of
Equity Loan Company.
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:
> &g
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
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
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 !CONFIG_ACPI (Randy
Factor out >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 >dev to dev refactor (Peter)
drivers/i2c/muxes/i2c-mux-gpio.c | 5 +++--
1 file chan
ope 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
drivers/i2c/muxes/i2c-mux-
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-jasperlake.
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(+), 1
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
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-s
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
ope 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
drivers/i2c/muxes/i2c-mux-
Factor out >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 >dev to dev refactor (Peter)
drivers/i2c/muxes/i2c-mux-gpio.c | 5 +++--
1 file chan
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 !CONFIG_ACPI (Randy
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(+), 1
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
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 deletions
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
, 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..f195e95e8a037
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
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
> > introd
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/sc7180
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")
Signed-off-by:
a
> 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
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.
> >
> >
aj
>
> 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 +--
> 1 f
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'd onl
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:
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
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")
Signed-off-by:
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
th10k: 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 e9d12ea708b6
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:
t up.
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
> ---
>
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
> -
e that's running the
modem well.
Tested-by: Evan Green
ies in my inbox.
Tested-by: Evan Green
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)
h 2|
||--< err 28 >--|| (dma0chan2)
|| --
|| --
||--< done 29 >--|ch 3|
||--< err 30 >--|| (dma0chan3)
-- --
Reviewed-by: Vinod Koul
Signed-off-by: Green Wan
Reported-by: kbuil
Update MAINTAINERS for SiFive PDMA driver.
Signed-off-by: Green Wan
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a69e6db80c79..62d5b249be65 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14778,6 +14778,12 @@ F: drivers/media/usb
Add PDMA support to (arch/riscv/boot/dts/sifive/fu540-c000.dtsi)
Signed-off-by: Green Wan
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
b/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
index
Add DT bindings document for Platform DMA(PDMA) driver of board,
HiFive Unleashed Rev A00.
Reviewed-by: Rob Herring
Reviewed-by: Pragnesh Patel
Signed-off-by: Green Wan
---
.../bindings/dma/sifive,fu540-c000-pdma.yaml | 55 +++
1 file changed, 55 insertions(+)
create mode
an2-copy0: summary 45975 tests, 0 failures
41178.48 iops 328740 KB/s (0)
[ 267.590542] dmatest: dma0chan3-copy0: summary 44768 tests, 0 failures
38560.29 iops 307726 KB/s (0)
Green Wan (4):
dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA
riscv: dts: add support for PDMA device of Hi
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;
> > >
> > >
com: 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
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 772493b1f665
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 insertions(+),
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
Update MAINTAINERS for SiFive PDMA driver.
Signed-off-by: Green Wan
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 30a5b4028d2f..6c12da0a324d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14779,6 +14779,12 @@ F: drivers/media/usb
Add PDMA support to (arch/riscv/boot/dts/sifive/fu540-c000.dtsi)
Signed-off-by: Green Wan
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
b/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
index
h 2|
||--< err 28 >--|| (dma0chan2)
|| --
|| --
||--< done 29 >--|ch 3|
||--< err 30 >--| | (dma0chan3)
-- --
Signed-off-by: Green Wan
---
drivers/dma/Kconfig | 2 +
Add DT bindings document for Platform DMA(PDMA) driver of board,
HiFive Unleashed Rev A00.
Signed-off-by: Green Wan
---
.../bindings/dma/sifive,fu540-c000-pdma.yaml | 55 +++
1 file changed, 55 insertions(+)
create mode 100644
Documentation/devicetree/bindings/dma/sifive
an2-copy0: summary 45975 tests, 0 failures
41178.48 iops 328740 KB/s (0)
[ 267.590542] dmatest: dma0chan3-copy0: summary 44768 tests, 0 failures
38560.29 iops 307726 KB/s (0)
Green Wan (4):
dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA
riscv: dts: add support for PDMA device of Hi
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/touchscreen
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_
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
index
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
--
||--< done 27 >--|ch 2|
||--< err 28 >--|| (dma0chan2)
|| --
|| --
||--< done 29 >--|ch 3|
||--< err 30 >--| | (dma0chan3)
-- --
Signed-off-by: Green
Add PDMA support to (arch/riscv/boot/dts/sifive/fu540-c000.dtsi)
Signed-off-by: Green Wan
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
b/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
index
Add DT bindings document for Platform DMA(PDMA) driver of board,
HiFive Unleashed Rev A00.
Signed-off-by: Green Wan
---
.../bindings/dma/sifive,fu540-c000-pdma.yaml | 55 +++
MAINTAINERS | 5 ++
2 files changed, 60 insertions(+)
create mode
t: dma0chan2-copy0: summary 10929638 tests, 0 failures
33984.39 iops 543750 KB/s (0)
[ 7757.003008] dmatest: dma0chan3-copy0: summary 11204208 tests, 0 failures
35759.65 iops 572154 KB/s (0)
Green Wan (3):
dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA
riscv: dts: add support for PDM
--
||--< done 27 >--|ch 2|
||--< err 28 >--|| (dma0chan2)
|| --
|| --
||--< done 29 >--|ch 3|
||--< err 30 >--| | (dma0chan3)
-- --
Signed-off-by: Green
Add PDMA support to (arch/riscv/boot/dts/sifive/fu540-c000.dtsi)
Signed-off-by: Green Wan
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
b/arch/riscv/boot/dts/sifive/fu540-c000.dtsi
index
Add DT bindings document for Platform DMA(PDMA) driver of board,
HiFive Unleashed Rev A00.
Signed-off-by: Green Wan
---
.../bindings/dma/sifive,fu540-c000-pdma.yaml | 63 +++
MAINTAINERS | 5 ++
2 files changed, 68 insertions(+)
create mode
sys/module/dmatest/parameters/run
Green Wan (3):
dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA
riscv: dts: add support for PDMA device of HiFive Unleashed Rev A00
dmaengine: sf-pdma: add platform DMA support for HiFive Unleashed A00
.../bindings/dma/sifive,fu540-c00
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
> --
1 - 100 of 2033 matches
Mail list logo
