Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38
>>On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote:
>> +
>> +static inline void __delay(unsigned long loops) {
>> + __asm__ __volatile__(".align 2\n"
>> +"1:\n"
>> +"\taddi\t%0, %0, -1\n"
>> +"\tbgtz\t%0, 1
FW will know about it.
In particular, in AP mode, clients are added upon receival of an auth
request, at which point there's no knowledge of the client's smps mode.
When the assoc request arrives, the add_sta command is resent to modify
the station parameters. At this point the driver
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Tested-and-acked-by: Bjorn Andersson
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 19 ---
1 file changed, 8 insertions(+), 11
On Fri 21 Jul 03:49 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> This patch refactor code to first load all firmware blobs
> and then update modem proc to authenticate and boot fw.
>
Acked-by: Bjorn Andersson
Regards,
Bjorn
> Signed-off-by: Avaneesh Kumar Dwivedi
> ---
>
> > Prior to that, the min/max_freq of the devfreq device are always zero
> > before the user changes the min/max_freq through sysfs entries.
> > It might make the confusion for the min/max_freq.
> >
> > This patch initializes the available min/max_freq by using the OPP
> > during adding the devfr
wcn36xx_err("Unknown AMPDU action\n");
}
+ mutex_unlock(&wcn->conf_mutex);
+
return 0;
}
@@ -1216,6 +1263,7 @@ static int wcn36xx_probe(struct platform
wcn = hw->priv;
wcn->hw = hw;
wcn->dev = &pdev->dev;
+ mutex_i
Luciano Coelho wrote:
> From: Luca Coelho
>
> The LEDS_CMD command is only supported in some newer FW versions
> (e.g. iwlwifi-8000C-31.ucode), so we can't send it to older versions
> (such as iwlwifi-8000C-27.ucode).
>
> To fix this, check for a new bit in the FW c
Linus Torvalds writes:
> On Thu, Sep 7, 2017 at 5:39 AM, Kalle Valo wrote:
>>
>> Linus, do you want to apply this directly or should we take it via the
>> normal route (wireless-drivers -> net)? If your prefer the latter when
>> I'm planning to submit this to Dave in a day or two and expecting i
On Thu, Sep 7, 2017 at 5:39 AM, Kalle Valo wrote:
>
> Linus, do you want to apply this directly or should we take it via the
> normal route (wireless-drivers -> net)? If your prefer the latter when
> I'm planning to submit this to Dave in a day or two and expecting it to
> get to your tree in abou
Luca Coelho writes:
> From: Luca Coelho
>
> The LEDS_CMD command is only supported in some newer FW versions
> (e.g. iwlwifi-8000C-31.ucode), so we can't send it to older versions
> (such as iwlwifi-8000C-27.ucode).
>
> To fix this, check for a new bit in the FW c
From: Luca Coelho
The LEDS_CMD command is only supported in some newer FW versions
(e.g. iwlwifi-8000C-31.ucode), so we can't send it to older versions
(such as iwlwifi-8000C-27.ucode).
To fix this, check for a new bit in the FW capabilities TLV that tells
when the command is supported.
Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38
Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38
().
>
> This is done by introducing a mutex to cover firmware configuration
> changes, which is made to also ensure mutual exclusion between other
> operations changing the state or configuration of the firmware. With
> this we can drop the rcu read lock.
>
> Cc: sta..
On Thu, 2017-08-03 at 07:47 -0700, João Paulo Rechi Vita wrote:
> These messages are not reporting a real error, just the fact that the
> firmware knows about more flags than the driver.
>
> Currently these messages are presented to the user during boot if there
> is no bootsplash covering the con
@@ EXPORT_SYMBOL_GPL(skl_sst_init_fw);
void skl_sst_dsp_cleanup(struct device *dev, struct skl_sst *ctx)
{
+
+ if (ctx->dsp->fw)
+ release_firmware(ctx->dsp->fw);
skl_clear_module_table(ctx->dsp);
skl_freeup_uuid_list(ctx);
skl_ipc_free(&ctx->ipc);
IWL_WARN(drv,
+"api flags index %d larger than supported by driver\n",
+api_index);
/* don't return an error so we can load FW that has more bits */
return 0;
}
@@ -485,9 +485,9 @@ static int iwl
From: João Paulo Rechi Vita
> Sent: 03 August 2017 15:30
> These messages are not reporting a real error, just the fact that the
> firmware knows about more flags then the driver.
than
>
> Currently these messages are presented to the user during boot if there
> i
"api flags index %d larger than supported by driver\n",
+api_index);
/* don't return an error so we can load FW that has more bits */
return 0;
}
@@ -485,9 +485,9 @@ static int iwl_set_ucode_capabilities(struct iwl_dr
wcn->hw = hw;
wcn->dev = &pdev->dev;
+ mutex_init(&wcn->conf_mutex);
mutex_init(&wcn->hal_mutex);
mutex_init(&wcn->scan_lock);
diff --git a/drivers/net/wireless/ath/wcn36xx/wcn36xx.h
b/drivers/net/wireless/ath/wcn36xx/wcn36xx.
Hi João Paulo,
On Tue, 2017-08-01 at 15:58 -0700, João Paulo Rechi Vita wrote:
> Hello Luca,
>
> On Mon, Jul 24, 2017 at 4:01 AM, Coelho, Luciano
> wrote:
> > On Fri, 2017-07-21 at 07:51 -0700, João Paulo Rechi Vita wrote:
>
> (...)
>
> > > Currently these messages are presented to the user d
Hello Luca,
On Mon, Jul 24, 2017 at 4:01 AM, Coelho, Luciano
wrote:
> On Fri, 2017-07-21 at 07:51 -0700, João Paulo Rechi Vita wrote:
(...)
>> Currently these messages are presented to the user during boot if there
>> is no bootsplash covering the console, sometimes even if the boot splash
>> i
at if the firmware is too new and includes
a TLV that we are not aware of, there can be unexpected issues. For
instance, sometimes the FW API changes some of its structures and we use
TLVs to know which one to use. If a new struct is in use by the
firmware but not by the driver, problems will occur.
"api flags index %d larger than supported by driver\n",
+api_index);
/* don't return an error so we can load FW that has more bits */
return 0;
}
@@ -511,9 +511,9 @@ static int iwl_set_ucode_capabilities(struct i
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers
(skl_sst_init_fw);
void skl_sst_dsp_cleanup(struct device *dev, struct skl_sst *ctx)
{
+
+ if (ctx->dsp->fw)
+ release_firmware(ctx->dsp->fw);
skl_clear_module_table(ctx->dsp);
skl_freeup_uuid_list(ctx);
skl_ipc_free(&ctx->ipc);
--
2.11.0
t for FW readiness on startup')
Signed-off-by: Eli Cohen
Signed-off-by: Saeed Mahameed
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/ethernet/mellanox/mlx5/core/main.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
--- a/drivers/net/ethernet/mellanox/mlx5/core/ma
t for FW readiness on startup')
Signed-off-by: Eli Cohen
Signed-off-by: Saeed Mahameed
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/ethernet/mellanox/mlx5/core/main.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
--- a/drivers/net/ethernet/mellanox/mlx5/core/ma
t for FW readiness on startup')
Signed-off-by: Eli Cohen
Signed-off-by: Saeed Mahameed
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/ethernet/mellanox/mlx5/core/main.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
--- a/drivers/net/ethernet/mellanox/mlx5/c
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers
Andrew, this seems to have fallen through the cracks. It addresses a
real bug with possible security considerations and should probably get
merged with a CC: stable...?
jon
Begin forwarded message:
Date: Mon, 22 May 2017 19:53:47 +0400
From: Ilya Matveychikov
To: linux-kernel@vger.kernel.org
C
From: Johan Hovold
commit e35d6d7c4e6532a89732cf4bace0e910ee684c88 upstream.
Bind to the interface, but do not register any ports, after having
downloaded the firmware. The device will still disconnect and
re-enumerate, but this way we avoid an error messages from being logged
as part of the pro
This flag lets userspace know which firmware partitions are actually
currently in use as opposed to just active. (Active meaning they will
be in use for the next reboot, where as running means they are currently
in use.)
If an old kernel is in use, or the firmware doesn't support these
fields, the
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Carnuccio
commit ce6c668b146cc4f4442111e2bcee4c3af94e1ddf upstream.
Firmware dump allows for debugging customer issues. This patch fixes
start/end pointer calculation to capture T262 templ
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Carnuccio
commit ce6c668b146cc4f4442111e2bcee4c3af94e1ddf upstream.
Firmware dump allows for debugging customer issues. This patch fixes
start/end pointer calculation to capture T262 templa
On Thursday, June 01, 2017 01:08:16 AM Jongman Heo wrote:
> >
> >- Original Message -
> >Sender : Rafael J. Wysocki
> >Date : 2017-06-01 08:58 (GMT+9)
> >Title : Re: FW: [4.12 regression] "cpufreq: intel_pstate: Active mode
> >P-state
On Thu 01 Jun 12:17 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> This patch refactor code to first load all firmware blobs
> and then update modem proc to authenticate and boot fw.
>
This looks good, but I have not had a chance to test this on older
platforms yet.
Acked-by: Bjorn
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers
alized previously by either the BMC own FW
or the VBIOS. This fixes it.
Signed-off-by: Y.C. Chen
Signed-off-by: Benjamin Herrenschmidt
Tested-by: Y.C. Chen
Acked-by: Joel Stanley
Signed-off-by: Dave Airlie
Signed-off-by: Ben Hutchings
---
drivers/gpu/drm
>
>- Original Message -
>Sender : Rafael J. Wysocki
>Date : 2017-06-01 08:58 (GMT+9)
>Title : Re: FW: [4.12 regression] "cpufreq: intel_pstate: Active mode P-state
>limits rework"
>
>On Monday, May 29, 2017 02:18:52 AM Jongman Heo wrote:
>
On Monday, May 29, 2017 02:18:52 AM Jongman Heo wrote:
>
> Hi,
>
> FYI, 4.12-rc3 still has this issue.
>
>
> - Original Message -
> Sender : 허종만
> Date : 2017-05-16 13:25 (GMT+9)
> Title : [4.12 regression] "cpufreq: intel_pstate: Active mode P-state limits
> rework"
>
>
On Sun, May 28, 2017 at 9:50 AM, Chris Healy wrote:
>
>
>
>
> From: Jonathan Cameron
> Sent: Sunday, May 28, 2017 8:48 AM
> To: Nikita Yoush
> Cc: Hartmut Knaack; Lars-Peter Clausen; Peter Meerwald-Stadler; Sanchayan
> Maity; Gregor Boirie; Matt Ranostay; linux-..
On 5/26/2017 12:43 AM, Bjorn Andersson wrote:
On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote:
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Nice, I like this! Just some style details below.
Thanks. Sure will
for the SCM PILs, the
> self-authenticated PILs and the non-PIL SCM users.
>
> Further more with the upcoming ramdump support we will need to extract
> segment information from the mdt header, so we will have to revisit this
> topic.
>
>
> Regardless, I would
On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> This patch refactor code to first load all firmware blobs
> and then update modem proc to authenticate and boot fw.
Nice, I like this! Just some style details below.
> Also make a trivial change in a error log.
>
>
equivalent routine has
> not been used. Bjorn may further add in this.
I have not been able to come up with a clean way to provide a useful
mdt-loader abstraction that works for the SCM PILs, the
self-authenticated PILs and the non-PIL SCM users.
Further more with the upcoming ramdump support
> phoe...@emc.com.tw
> Subject: Re: [PATCH] Input: elan_i2c - Prevent breaking of FW updating from
> unexpected signal
>
> Hi KT,
>
> On Tue, May 23, 2017 at 10:32:02PM +0800, KT Liao wrote:
> > Use wait_for_completion_timeout to prevent breaking of FW updating from
>
On Wed, May 24, 2017 at 05:43:39PM +0800, KT Liao wrote:
> Some old touchapd FWs have interrupt issue after FW updating.
> Use reading 34 bytes before IC reset command to clean INT stauts
> The modification has been tested in some chromebook system
> It should not affect general touch
static int mwifiex_prog_fw_w_helper(struct
mwifiex_adapter *adapter,
"info: Downloading FW image (%d bytes)\n",
firmware_len);
- if (__mwifiex_pcie_disable_host_int(adapter)) {
- mwifiex_dbg(adapter, ERROR,
- "%s: D
Some old touchapd FWs have interrupt issue after FW updating.
Use reading 34 bytes before IC reset command to clean INT stauts
The modification has been tested in some chromebook system
It should not affect general touchpad in Linux system.
Signed-off-by: KT Liao
---
drivers/input/mouse
Hi Dmitry
-Original Message-
From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
Sent: Wednesday, May 24, 2017 5:14 AM
To: KT Liao
Cc: linux-kernel@vger.kernel.org; linux-in...@vger.kernel.org;
phoe...@emc.com.tw
Subject: Re: [PATCH] Input: elan_i2c - Prevent breaking of FW updating
Hi KT,
On Tue, May 23, 2017 at 10:32:02PM +0800, KT Liao wrote:
> Use wait_for_completion_timeout to prevent breaking of FW updating from
> unexpected signal
>
> Signed-off-by: KT Liao
> ---
> drivers/input/mouse/elan_i2c_i2c.c | 2 +-
> 1 file changed, 1 insertion(+), 1
Use wait_for_completion_timeout to prevent breaking of FW updating from
unexpected signal
Signed-off-by: KT Liao
---
drivers/input/mouse/elan_i2c_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/mouse/elan_i2c_i2c.c
b/drivers/input/mouse/elan_i2c_i2c.c
update modem proc to authenticate and boot fw.
Also make a trivial change in a error log.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/drivers/remoteproc
bs
>>> and then update modem proc to authenticate and boot fw.
>>> Also make a trivial change in a error log.
>>>
>>> Signed-off-by: Avaneesh Kumar Dwivedi
>>> ---
>>> drivers/remoteproc/qcom_q6v5_pil.c | 25 -
>&
On 5/20/2017 8:25 AM, Sricharan R wrote:
Hi Bjorn/Avaneesh,
On 5/16/2017 11:32 PM, Avaneesh Kumar Dwivedi wrote:
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Also make a trivial change in a error log.
Signed-off-by
Hi Bjorn/Avaneesh,
On 5/16/2017 11:32 PM, Avaneesh Kumar Dwivedi wrote:
> This patch refactor code to first load all firmware blobs
> and then update modem proc to authenticate and boot fw.
> Also make a trivial change in a error log.
>
> Signed-off-by: Avaneesh Kumar Dwivedi
&
The patch
ASoC: da7213: Update driver to use device_property* FW functions
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The driver now supports ACPI based initialisation as well as DT
and old pdata methods. However the FW data handling still uses
DT specific calls to read firmware data (of_property*) so for
ACPI based initialisation the FW data will only be set to default
values. This patch updates the FW handling
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Maxim Altshul
commit 42c7372a111630dab200c2f959424f5ec3bf79a4 upstream.
When starting a new BA session, we must pass the win_size to the FW.
To do this we take max_rx_aggregation_subframes
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Also make a trivial change in a error log.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 25 -
1 file changed, 12 insertions
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Also make a trivial change in a error log.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 25 -
1 file changed, 12 insertions
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Maxim Altshul
commit 42c7372a111630dab200c2f959424f5ec3bf79a4 upstream.
When starting a new BA session, we must pass the win_size to the FW.
To do this we take max_rx_aggregation_subframes
We kill pending fallback requests on suspend and reboot,
the only difference is that on suspend we only kill custom
fallback requests. Provide a wrapper that lets us customize
the request with a flag.
This also lets us simplify the #ifdef'ery over the calls.
Signed-off-by: Luis R. Rodriguez
---
Hi Arnd,
> 2017-04-28 19:41 GMT+08:00 Arnd Bergmann :
>
> On Fri, Apr 28, 2017 at 4:46 AM, Ryder Lee
> wrote:
> > On Thu, 2017-04-27 at 21:06 +0200, Arnd Bergmann wrote:
> >> On Wed, Apr 26, 2017 at 10:10 AM, Ryder Lee
> wrote:
> >> > On Tue, 201
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mohamad Haj Yahia
[ Upstream commit 55378a238e04b39cc82957d91d16499704ea719b ]
If FW is stuck in initializing state we will skip the driver load, but
current error handling flow doesn't
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mohamad Haj Yahia
[ Upstream commit 55378a238e04b39cc82957d91d16499704ea719b ]
If FW is stuck in initializing state we will skip the driver load, but
current error handling flow doesn&#
On Thu, Apr 06, 2017 at 06:38:47AM +, Coelho, Luciano wrote:
> Hi Luis,
> > diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
> > index ac350c518e0c..d2e2d83aaf26 100644
> > --- a/drivers/base/firmware_class.c
> > +++ b/drivers/base/firmware_class.c
> > @@ -562,16 +562,
Hi Sebastian,
> Avoid NULL pointer dereference occurring due to freeing
> skb containing an error pointer. It can easily be triggered
> by using the driver with broken uart (i.e. due to misconfigured
> pinmuxing).
>
> Fixes: 371805522f87 ("bluetooth: hci_uart: add LL protocol serdev driver
> sup
viously by either the BMC own FW
or the VBIOS. This fixes it.
Signed-off-by: Y.C. Chen
Signed-off-by: Benjamin Herrenschmidt
Tested-by: Y.C. Chen
Acked-by: Joel Stanley
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/ast/ast_pos
Avoid NULL pointer dereference occurring due to freeing
skb containing an error pointer. It can easily be triggered
by using the driver with broken uart (i.e. due to misconfigured
pinmuxing).
Fixes: 371805522f87 ("bluetooth: hci_uart: add LL protocol serdev driver
support")
Signed-off-by: Sebasti
Hi Luis,
On Wed, 2017-03-29 at 20:24 -0700, Luis R. Rodriguez wrote:
> We kill pending fallback requests on suspend and reboot,
> the only difference is that on suspend we only kill custom
> fallback requests. Provide a wrapper that lets us customize
> the request with a flag.
>
> This also lets
Brian Norris wrote:
> If we fail to reinit the FW when resetting the device (in the
> synchronous version of mwifiex_init_hw_fw() -> mwifiex_fw_dpc()),
> mwifiex_fw_dpc() will tear down the interface and free up the adapter.
> But we don't actually check for all failure cas
On 03/30/2017 01:49 PM, Peter Senna Tschudin wrote:
Reordering of the device nodes based on unit address resulted in
ge_b850v3_lvds_attach() being called before
ge_b850v3_lvds_ptr->stdp4028_i2c was populated.
This patch moves the drm bridge initialization from
ge_b850v3_lvds_init() to stdp4028
Reordering of the device nodes based on unit address resulted in
ge_b850v3_lvds_attach() being called before
ge_b850v3_lvds_ptr->stdp4028_i2c was populated.
This patch moves the drm bridge initialization from
ge_b850v3_lvds_init() to stdp4028_ge_b850v3_fw_probe() ensuring that
ge_b850v3_lvds_ptr->
We kill pending fallback requests on suspend and reboot,
the only difference is that on suspend we only kill custom
fallback requests. Provide a wrapper that lets us customize
the request with a flag.
This also lets us simplify the #ifdef'ery over the calls.
Signed-off-by: Luis R. Rodriguez
---
If we fail to reinit the FW when resetting the device (in the
synchronous version of mwifiex_init_hw_fw() -> mwifiex_fw_dpc()),
mwifiex_fw_dpc() will tear down the interface and free up the adapter.
But we don't actually check for all failure cases of mwifiex_fw_dpc(),
so some of them fall
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matjaz Hegedic
commit 92ef6f97a66e580189a41a132d0f8a9f78d6ddce upstream.
EeeBook X205TA is yet another ASUS device with a special touchpad
firmware that needs to be accounted for during initial
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matjaz Hegedic
commit 92ef6f97a66e580189a41a132d0f8a9f78d6ddce upstream.
EeeBook X205TA is yet another ASUS device with a special touchpad
firmware that needs to be accounted for during initial
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matjaz Hegedic
commit 92ef6f97a66e580189a41a132d0f8a9f78d6ddce upstream.
EeeBook X205TA is yet another ASUS device with a special touchpad
firmware that needs to be accounted for during initia
bool rproc_is_running(struct rproc *rproc)
return (rproc->state == RPROC_RUNNING) ? true : false;
}
+/**
+ * rproc_handle_fw_chksum() - handle firmware checksum resource
+ * @rproc: rproc handle
+ * @fw: firmware
+ * @offset: returns fw_chksum resource offset.
+ *
+ * This function w
truct rproc *rproc, const struct firmware *fw)
+{
+ (void)rproc;
+ (void) fw;
+
+ return false;
+}
+
+/*
* take a firmware and boot a remote processor with it.
*/
static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw)
@@ -906,6 +917,7 @@ static int rproc_fw
Greg, hope you had not faced any issue (tab converted to spaces) with this
patch.
In case still facing any issue please let me know.
> There is race condition when two USB class drivers try to call
> init_usb_class at the same time and leads to crash.
> code path: probe->usb_register_dev->init_u
On Thu, Mar 16, 2017 at 09:41:03AM +0100, Daniel Vetter wrote:
> On Thu, Mar 16, 2017 at 10:34:59AM +0800, Shawn Guo wrote:
> > I fixed up all of them and applied patch.
>
> +1 on doing review like this. And for committers you can do "with all that
> fixed r-b: me" and let them fix it up & push th
On Thu, Mar 16, 2017 at 10:34:59AM +0800, Shawn Guo wrote:
> I fixed up all of them and applied patch.
+1 on doing review like this. And for committers you can do "with all that
fixed r-b: me" and let them fix it up & push themselves, even less work
:-)
Cheers, Daniel
--
Daniel Vetter
Software E
On Tue, Mar 14, 2017 at 10:23:02AM +0100, Peter Senna Tschudin wrote:
> Configures the megachips-stdp-ge-b850v3-fw bridges on the GE
> B850v3 dts file.
>
> Cc: Laurent Pinchart
> Cc: Martyn Welch
> Cc: Martin Donnelly
> Cc: Javier Martinez Canillas
> Cc: Enri
Configures the megachips-stdp-ge-b850v3-fw bridges on the GE
B850v3 dts file.
Cc: Laurent Pinchart
Cc: Martyn Welch
Cc: Martin Donnelly
Cc: Javier Martinez Canillas
Cc: Enric Balletbo i Serra
Cc: Philipp Zabel
Cc: Rob Herring
Cc: Fabio Estevam
Signed-off-by: Peter Senna Tschudin
On Fri, Mar 03, 2017 at 04:57:10PM +0100, Peter Senna Tschudin wrote:
> Configures the megachips-stdp-ge-b850v3-fw bridges on the GE
> B850v3 dts file.
>
> Cc: Laurent Pinchart
> Cc: Martyn Welch
> Cc: Martin Donnelly
> Cc: Javier Martinez Canillas
> Cc: Enri
viously by either the BMC own FW
or the VBIOS. This fixes it.
Signed-off-by: Y.C. Chen
Signed-off-by: Benjamin Herrenschmidt
Tested-by: Y.C. Chen
Acked-by: Joel Stanley
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/ast/ast_pos
viously by either the BMC own FW
or the VBIOS. This fixes it.
Signed-off-by: Y.C. Chen
Signed-off-by: Benjamin Herrenschmidt
Tested-by: Y.C. Chen
Acked-by: Joel Stanley
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/ast/ast_pos
viously by either the BMC own FW
or the VBIOS. This fixes it.
Signed-off-by: Y.C. Chen
Signed-off-by: Benjamin Herrenschmidt
Tested-by: Y.C. Chen
Acked-by: Joel Stanley
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/ast/ast_pos
-kernel@vger.kernel.org; 黃世鵬 經理;
> miller_w...@emc.com.tw
> Subject: Re: [PATCH] Input: elan_i2c - add ASUS EeeBook X205TA special
> touchpad fw
>
> Hi Dmitry, KT!
>
> On 2017-03-07 08:05, 廖崇榮 wrote:
> > Hi Dmitry
> >
> > -Original Message-
> >
hat in this design neither the STDP4028
> > > nor the STDP2690 behave as the stock bridges would. The compatible
> > > strings include the suffix "-ge-b850v3-fw" to make it clear that the
> > > driver is for the bridges with the firmware which is specific for the GE
&
On Fri, Mar 03, 2017 at 04:57:10PM +0100, Peter Senna Tschudin wrote:
Hi Shawn Guo,
Now that the driver and binding are in, can you pick this up?
Thank you!
> Configures the megachips-stdp-ge-b850v3-fw bridges on the GE
> B850v3 dts file.
>
> Cc: Laurent Pinchart
> Cc: Mar
(STDP2690)--|DP++ -> Video output
> >
> > Each bridge has a dedicated flash containing firmware for supporting the
> > custom design. The result is that in this design neither the STDP4028
> > nor the STDP2690 behave as the stock bridges would. The compatible
> > st
_i2c - add ASUS EeeBook X205TA special touchpad
fw
Hi Dmitry, KT!
On 2017-03-07 08:05, 廖崇榮 wrote:
> Hi Dmitry
>
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Tuesday, March 07, 2017 3:55 AM
> To: KT Liao
> Cc: linux-in..
] Input: elan_i2c - add ASUS EeeBook X205TA special
touchpad fw
On Sun, Mar 05, 2017 at 03:13:02AM +0100, Matjaz Hegedic wrote:
EeeBook X205TA is yet another ASUS device with a special touchpad
firmware that needs to be accounted for during initialization, or else
the touchpad will go into an invalid
touchpad fw
On Sun, Mar 05, 2017 at 03:13:02AM +0100, Matjaz Hegedic wrote:
> EeeBook X205TA is yet another ASUS device with a special touchpad
> firmware that needs to be accounted for during initialization, or else
> the touchpad will go into an invalid state upon suspend/resume.
>
On Sun, Mar 05, 2017 at 03:13:02AM +0100, Matjaz Hegedic wrote:
> EeeBook X205TA is yet another ASUS device with a special touchpad
> firmware that needs to be accounted for during initialization, or
> else the touchpad will go into an invalid state upon suspend/resume.
> Adding the appropriate ic_
701 - 800 of 2016 matches
Mail list logo
