[Scilab-users] Xcos electrical simulation returns error "make: *** [Makelib:131: clean] Error 127"

Hello, I am trying to run the 'RLC circuit' simulation which is in the demonstrations>xcos>electrical systems menu. But I am getting the following error in the console: __ Main Modelica : C:\Users\monis\AppData\Local\Temp\SCI_TMP_11304_24317\RLC_Modelica_im.mo

[ED] La UDL - Uboldo Disc League indoor tournament

Who wants to play outdoor ultimate in mid-january in northern Italy?! Exactly... NO ONE! After 20 years of activity, Frasba is organizing its first proper indoor tournament and even we continue to ask ourselves why we didn't do it before. You are all invited to join us and make this first

[Discover] [Bug 472673] New: Discover se cierra al iniciar

https://bugs.kde.org/show_bug.cgi?id=472673 Bug ID: 472673 Summary: Discover se cierra al iniciar Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status:

Re: [PATCH v20 1/2] scsi: ufs: Enable power management for wlun

On 4/19/2021 11:37 AM, Adrian Hunter wrote: On 16/04/21 10:49 pm, Asutosh Das wrote: Co-developed-by: Can Guo Signed-off-by: Can Guo Signed-off-by: Asutosh Das --- I came across 3 issues while testing. See comments below. Hi Adrian Thanks for the comments. @@ -5794,7 +5839,7 @@

Re: [PATCH v18 1/2] scsi: ufs: Enable power management for wlun

On 4/15/2021 4:11 PM, Bart Van Assche wrote: On 4/14/21 11:58 AM, Asutosh Das wrote: [ ... ] Hi Bart, Thanks for the comments. I will fix the comments in the next version. The following code is executed before ufshcd_async_scan() is called: dev = hba->dev; [ ... ]

Re: [PATCH v17 1/2] scsi: ufs: Enable power management for wlun

On 4/9/2021 3:07 AM, Adrian Hunter wrote: On 9/04/21 5:27 am, Daejun Park wrote: Hi Asutosh Das, During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them. But the ufs host sends SSU (START_STOP_UNIT) to wlun during its

Re: [PATCH v15 1/2] scsi: ufs: Enable power management for wlun

Yikes! Thanks, let me fix this and push the correct series. -asd -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, Linux Foundation Collaborative Project

Re: [PATCH v14 1/2] scsi: ufs: Enable power management for wlun

On 3/31/2021 11:19 AM, Adrian Hunter wrote: On 31/03/21 1:31 am, Asutosh Das wrote: During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them. But the ufs host sends SSU (START_STOP_UNIT) to wlun during its runtime-suspend. During the

Re: [PATCH V2 2/3] scsi: ufs: add a vops to configure VCC voltage level

On 3/21/2021 2:57 PM, Nitin Rawat wrote: Add a vops to configure VCC voltage VCC voltage level for platform supporting both ufs2.x and ufs 3.x devices. Suggested-by: Stanley Chu Suggested-by: Asutosh Das Suggested-by: Bjorn Andersson Signed-off-by: Nitin Rawat Signed-off-by: Veerabhadrarao

Re: [PATCH v12 1/2] scsi: ufs: Enable power management for wlun

On 3/23/2021 12:19 PM, Adrian Hunter wrote: On 23/03/21 5:13 pm, Asutosh Das (asd) wrote: On 3/22/2021 11:12 PM, Adrian Hunter wrote: On 22/03/21 9:53 pm, Asutosh Das (asd) wrote: On 3/19/2021 10:47 AM, Adrian Hunter wrote: On 19/03/21 2:35 am, Asutosh Das wrote: During runtime-suspend

Re: [PATCH v12 1/2] scsi: ufs: Enable power management for wlun

On 3/22/2021 11:12 PM, Adrian Hunter wrote: On 22/03/21 9:53 pm, Asutosh Das (asd) wrote: On 3/19/2021 10:47 AM, Adrian Hunter wrote: On 19/03/21 2:35 am, Asutosh Das wrote: During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them

Re: [PATCH v12 1/2] scsi: ufs: Enable power management for wlun

s(). Am not sure if I'm missing something in this. Do you think, the current changes alone can fix the above issue? -asd --- drivers/scsi/ufs/cdns-pltfrm.c | 2 + drivers/scsi/ufs/tc-dwc-g210-pci.c | 2 + drivers/scsi/ufs/ufs-debugfs.c | 2 +- drivers/scsi/ufs/ufs-debugfs.h

Re: [PATCH v12 1/2] scsi: ufs: Enable power management for wlun

thing of resume, if * resume fails, irq and clocks can be OFF, and powers * can be OFF or in LPM. */ Please make better use of the horizontal space in the above comment by making comment lines longer. Ok Sure. Thanks, Bart. -asd -- The Qualcomm Innovat

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/18/2021 12:16 PM, Adrian Hunter wrote: On 18/03/21 7:58 pm, Asutosh Das (asd) wrote: On 3/18/2021 10:54 AM, Rafael J. Wysocki wrote: On Thu, Mar 18, 2021 at 6:33 PM Asutosh Das (asd) wrote: On 3/18/2021 7:00 AM, Rafael J. Wysocki wrote: On Wed, Mar 17, 2021 at 7:37 AM Adrian Hunter

Re: [PATCH v11 1/2] scsi: ufs: Enable power management for wlun

On 3/15/2021 7:29 AM, Adrian Hunter wrote: On 12/03/21 12:19 am, Asutosh Das wrote: During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them. But the ufs host sends SSU to wlun during its runtime-suspend. During the process

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/18/2021 10:54 AM, Rafael J. Wysocki wrote: On Thu, Mar 18, 2021 at 6:33 PM Asutosh Das (asd) wrote: On 3/18/2021 7:00 AM, Rafael J. Wysocki wrote: On Wed, Mar 17, 2021 at 7:37 AM Adrian Hunter wrote: On 16/03/21 10:35 pm, Asutosh Das (asd) wrote: On 3/16/2021 12:48 AM, Adrian Hunter

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/18/2021 7:00 AM, Rafael J. Wysocki wrote: On Wed, Mar 17, 2021 at 7:37 AM Adrian Hunter wrote: On 16/03/21 10:35 pm, Asutosh Das (asd) wrote: On 3/16/2021 12:48 AM, Adrian Hunter wrote: On 16/03/21 12:22 am, Asutosh Das (asd) wrote: On 3/14/2021 1:11 AM, Adrian Hunter wrote: On 10/03

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/16/2021 12:48 AM, Adrian Hunter wrote: On 16/03/21 12:22 am, Asutosh Das (asd) wrote: On 3/14/2021 1:11 AM, Adrian Hunter wrote: On 10/03/21 5:04 am, Asutosh Das (asd) wrote: On 3/9/2021 7:56 AM, Asutosh Das (asd) wrote: On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote: On Mon, Mar 8, 2021

Re: [PATCH v11 1/2] scsi: ufs: Enable power management for wlun

On 3/15/2021 7:29 AM, Adrian Hunter wrote: On 12/03/21 12:19 am, Asutosh Das wrote: During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them. But the ufs host sends SSU to wlun during its runtime-suspend. During the process

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/14/2021 1:11 AM, Adrian Hunter wrote: On 10/03/21 5:04 am, Asutosh Das (asd) wrote: On 3/9/2021 7:56 AM, Asutosh Das (asd) wrote: On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote: On Mon, Mar 8, 2021 at 5:21 PM Rafael J. Wysocki wrote: On Sat, Mar 6, 2021 at 5:17 PM Alan Stern wrote

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/10/2021 8:27 AM, Alan Stern wrote: On Tue, Mar 09, 2021 at 08:04:53PM -0800, Asutosh Das (asd) wrote: On 3/9/2021 7:14 PM, Alan Stern wrote: On Tue, Mar 09, 2021 at 07:04:34PM -0800, Asutosh Das (asd) wrote: Hello I & Can (thanks CanG) debugged this further: Looks like this issue

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/9/2021 7:14 PM, Alan Stern wrote: On Tue, Mar 09, 2021 at 07:04:34PM -0800, Asutosh Das (asd) wrote: Hello I & Can (thanks CanG) debugged this further: Looks like this issue can occur if the sd probe is asynchronous. Essentially, the sd_probe() is done asynchrono

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/9/2021 7:56 AM, Asutosh Das (asd) wrote: On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote: On Mon, Mar 8, 2021 at 5:21 PM Rafael J. Wysocki wrote: On Sat, Mar 6, 2021 at 5:17 PM Alan Stern wrote: On Fri, Mar 05, 2021 at 06:54:24PM -0800, Asutosh Das (asd) wrote: Now during my testing

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote: On Mon, Mar 8, 2021 at 5:21 PM Rafael J. Wysocki wrote: On Sat, Mar 6, 2021 at 5:17 PM Alan Stern wrote: On Fri, Mar 05, 2021 at 06:54:24PM -0800, Asutosh Das (asd) wrote: Now during my testing I see a weird issue sometimes (1 in 7). Scenario

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

On 3/4/2021 7:35 AM, Adrian Hunter wrote: On 3/03/21 12:52 am, Asutosh Das wrote: During runtime-suspend of ufs host, the scsi devices are already suspended and so are the queues associated with them. But the ufs host sends SSU to wlun during its runtime-suspend. During the process

Re: [PATCH v1] scsi: ufs-mediatek: Enable UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL

On 12/24/2020 5:47 AM, Stanley Chu wrote: Hi Avri, Bean, On Thu, 2020-12-24 at 13:01 +0100, Bean Huo wrote: On Thu, 2020-12-24 at 11:03 +, Avri Altman wrote: Do you see any substantial benefit of having fWriteBoosterBufferFlushEn disabled? 1. The definition of fWriteBoosterBufferFlushEn

Re: [PATCH v2 2/2] scsi: ufs: Uninline ufshcd_vops_device_reset function

On 12/8/2020 5:56 AM, Stanley Chu wrote: Since more and more statements showing up in ufshcd_vops_device_reset(), uninline it to allow compiler making possibly better optimization. Signed-off-by: Stanley Chu --- Reviewed-by: Asutosh Das drivers/scsi/ufs/ufshcd.c | 27

Re: [PATCH v1 0/3] Refine error history and introduce notify_event vop

On 11/25/2020 9:38 PM, Stanley Chu wrote: Hi, This series refines error history functions and introduce a new notify_event vop to allow vendor to get notified of important events. Stanley Chu (3): scsi: ufs: Add error history for abort event in UFS Device W-LUN scsi: ufs: Refine error

Re: [PATCH 1/3] scsi: ufs: Add "wb_on" sysfs node to control WB on/off

On 12/2/2020 8:20 AM, Bean Huo wrote: On Mon, 2020-11-30 at 15:19 -0800, Asutosh Das (asd) wrote: + return -EINVAL; + + pm_runtime_get_sync(hba->dev); + res = ufshcd_wb_ctrl(hba, wb_enable); Say, a platform supports clock-scaling and this bit is toggled. The control g

Re: [PATCH v3 1/2] scsi: ufs: Refactor ufshcd_setup_clocks() to remove skip_ref_clk

On 11/30/2020 7:11 PM, Can Guo wrote: On 2020-12-01 07:01, Asutosh Das (asd) wrote: On 11/25/2020 6:01 PM, Can Guo wrote: Remove the param skip_ref_clk from __ufshcd_setup_clocks(), but keep a flag in struct ufs_clk_info to tell whether a clock can be disabled or not while the link is active

Re: [PATCH v2] scsi: ufs: Remove pre-defined initial voltage values of device powers

On 11/30/2020 10:51 PM, Stanley Chu wrote: UFS specficication allows different VCC configurations for UFS devices, for example, (1). 2.70V - 3.60V (Activated by default in UFS core driver) (2). 1.70V - 1.95V (Activated if "vcc-supply-1p8" is declared in

Re: [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values

On 11/30/2020 6:53 PM, Bjorn Andersson wrote: On Mon 30 Nov 17:54 CST 2020, Asutosh Das (asd) wrote: On 11/30/2020 3:14 PM, Bjorn Andersson wrote: On Mon 30 Nov 16:51 CST 2020, Asutosh Das (asd) wrote: On 11/30/2020 1:16 AM, Stanley Chu wrote: UFS specficication allows different VCC

Re: [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values

On 11/30/2020 5:25 PM, Stanley Chu wrote: On Mon, 2020-11-30 at 15:54 -0800, Asutosh Das (asd) wrote: On 11/30/2020 3:14 PM, Bjorn Andersson wrote: On Mon 30 Nov 16:51 CST 2020, Asutosh Das (asd) wrote: On 11/30/2020 1:16 AM, Stanley Chu wrote: UFS specficication allows different VCC

Re: [PATCH v3 2/3] scsi: ufs: Fix a racing problem between ufshcd_abort and eh_work

On 11/16/2020 11:04 PM, Can Guo wrote: In current task abort routine, if task abort happens to the device W-LU, the code directly jumps to ufshcd_eh_host_reset_handler() to perform a full reset and restore then returns FAIL or SUCCESS. Commands sent to the device W-LU are most likely the SSU

Re: [PATCH v3 1/3] scsi: ufs: Serialize eh_work with system PM events and async scan

On 11/16/2020 11:04 PM, Can Guo wrote: Serialize eh_work with system PM events and async scan to make sure eh_work does not run in parallel with them. Signed-off-by: Can Guo --- Reviewed-by: Asutosh Das drivers/scsi/ufs/ufshcd.c | 64 +--

Re: [PATCH v3 2/2] scsi: ufs-qcom: Keep core_clk_unipro ON while link is active

On 11/25/2020 6:01 PM, Can Guo wrote: If we want to disable clocks to save power but still keep the link active, core_clk_unipro, as same as ref_clk, should not be the one being disabled. Reviewed-by: Hongwu Su Signed-off-by: Can Guo --- Reviewed-by: Asutosh Das

Re: [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values

On 11/30/2020 3:14 PM, Bjorn Andersson wrote: On Mon 30 Nov 16:51 CST 2020, Asutosh Das (asd) wrote: On 11/30/2020 1:16 AM, Stanley Chu wrote: UFS specficication allows different VCC configurations for UFS devices, for example, (1). 2.70V - 3.60V (By default) (2). 1.70V

Re: [PATCH 1/3] scsi: ufs: Add "wb_on" sysfs node to control WB on/off

On 11/30/2020 10:11 AM, Bean Huo wrote: From: Bean Huo Currently we let UFS WriteBooster driver use clock scaling up/down to set WB on/off, for the platform which doesn't support UFSHCD_CAP_CLK_SCALING, WB will be always on. Provide a sysfs attribute to enable/disable WB during runtime.

Re: [PATCH v3 1/2] scsi: ufs: Refactor ufshcd_setup_clocks() to remove skip_ref_clk

On 11/25/2020 6:01 PM, Can Guo wrote: Remove the param skip_ref_clk from __ufshcd_setup_clocks(), but keep a flag in struct ufs_clk_info to tell whether a clock can be disabled or not while the link is active. Reviewed-by: Hongwu Su Reviewed-by: Bean Huo Reviewed-by: Stanley Chu

Re: [PATCH 1/1] scsi: ufs: Remove scale down gear hard code

On 11/26/2020 5:58 PM, Can Guo wrote: Instead of making the scale down gear a hard code, make it a member of ufs_clk_scaling struct. Signed-off-by: Can Guo --- Reviewed-by: Asutosh Das drivers/scsi/ufs/ufshcd.c | 12 +++- drivers/scsi/ufs/ufshcd.h | 2 ++ 2 files changed, 9

Re: [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values

Hi Stanley Thanks for the patch. Bao (nguyenb) was also working towards something similar. Would it be possible for you to take into account the scenario in which the same platform supports both 2.x and 3.x UFS devices? These've different voltage requirements, 2.4v-3.6v. I'm not sure if standar

Re: [PATCH v3 3/3] scsi: ufs: Print host regs in IRQ handler when AH8 error happens

On 11/16/2020 11:04 PM, Can Guo wrote: When AH8 error happens, all the regs and states are dumped in err handler. Sometime we need to look into host regs right after AH8 error happens, which is before leaving the IRQ handler. Signed-off-by: Can Guo --- Reviewed-by: Asutosh Das

Re: [PATCH v1 1/2] scsi: ufs: Fix unbalanced scsi_block_reqs_cnt caused by ufshcd_hold()

On 11/2/2020 10:24 PM, Can Guo wrote: The scsi_block_reqs_cnt increased in ufshcd_hold() is supposed to be decreased back in ufshcd_ungate_work() in a paired way. However, if specific ufshcd_hold/release sequences are met, it is possible that scsi_block_reqs_cnt is increased twice but only one

Re: [PATCH v2 1/1] scsi: ufs: Fix unexpected values get from ufshcd_read_desc_param()

On 10/21/2020 10:59 PM, Can Guo wrote: Since WB feature has been added, WB related sysfs entries can be accessed even when an UFS device does not support WB feature. In that case, the descriptors which are not supported by the UFS device may be wrongly reported when they are accessed from their

Re: [PATCH v2] scsi: ufshcd: fix missing destroy_workqueue()

On 11/9/2020 11:42 PM, Qinglang Miao wrote: Add the missing destroy_workqueue() before return from ufshcd_init in the error handling case as well as in ufshcd_remove. Fixes: 4db7a2360597 ("scsi: ufs: Fix concurrency of error handler and other error recovery paths") Suggested-by: Avri Altman

Re: [PATCH V4 1/2] scsi: ufs: Add DeepSleep feature

On 11/3/2020 6:14 AM, Adrian Hunter wrote: DeepSleep is a UFS v3.1 feature that achieves the lowest power consumption of the device, apart from power off. In DeepSleep mode, no commands are accepted, and the only way to exit is using a hardware reset or power cycle. This patch assumes that if

Re: [PATCH V4 2/2] scsi: ufs: Allow an error return value from ->device_reset()

On 11/3/2020 6:14 AM, Adrian Hunter wrote: It is simpler for drivers to provide a ->device_reset() callback irrespective of whether the GPIO, or firmware interface necessary to do the reset, is discovered during probe. Change ->device_reset() to return an error code. Drivers that provide the

Re: [PATCH v9 7/9] scsi: ufs: Move dumps in IRQ handler to error handler

On 8/3/2020 2:04 AM, Can Guo wrote: Sometime dumps in IRQ handler are heavy enough to cause system stability issues, move them to error handler and only print basic host regs here. Signed-off-by: Can Guo Reviewed-by: Bean Huo --- Reviewed-by: Asutosh Das drivers/scsi/ufs/ufshcd.c | 23

Re: [PATCH v7 7/8] scsi: ufs: Move dumps in IRQ handler to error handler

On 7/29/2020 6:02 AM, Can Guo wrote: Hi Asutosh, On 2020-07-29 02:06, Asutosh Das (asd) wrote: On 7/27/2020 10:00 PM, Can Guo wrote: Sometime dumps in IRQ handler are heavy enough to cause system stability issues, move them to error handler. Signed-off-by: Can Guo ---   drivers/scsi/ufs

Re: [PATCH v7 7/8] scsi: ufs: Move dumps in IRQ handler to error handler

On 7/27/2020 10:00 PM, Can Guo wrote: Sometime dumps in IRQ handler are heavy enough to cause system stability issues, move them to error handler. Signed-off-by: Can Guo --- drivers/scsi/ufs/ufshcd.c | 31 +++ 1 file changed, 15 insertions(+), 16 deletions(-)

Re: [PATCH v7 4/8] scsi: ufs: Add some debug infos to ufshcd_print_host_state

On 7/27/2020 10:00 PM, Can Guo wrote: The infos of the last interrupt status and its timestamp are very helpful when debug system stability issues, e.g. IRQ starvation, so add them to ufshcd_print_host_state. Meanwhile, UFS device infos like model name and its FW version also come in handy

Re: [PATCH v2] scsi: ufs: Disable WriteBooster capability in non-supported UFS device

On 6/24/2020 12:41 AM, Stanley Chu wrote: If UFS device is not qualified to enter the detection of WriteBooster probing by disallowed UFS version or device quirks, then WriteBooster capability in host shall be disabled to prevent any WriteBooster operations in the future. Fixes: 3d17b9b5ab11

Re: [PATCH v4 0/4] scsi: ufs: Fix WriteBooster and cleanup UFS driver

On 5/22/2020 1:32 AM, Stanley Chu wrote: Hi, This patch set fixes some WriteBooster issues and do small cleanup in UFS driver v3 -> v4 - Squash patch [4] and [5] (Asutosh) - Fix commit message in patch [4] v2 -> v3 - Introduce patch [5] to fix possible VCC power drain during runtime

Re: [PATCH v2 1/3] scsi: ufshcd: Update the set frequency to devfreq

Hi Jeffrey On 5/25/2020 3:19 PM, Jeffrey Hugo wrote: On Wed, Mar 25, 2020 at 12:29 PM Asutosh Das wrote: Currently, the frequency that devfreq provides the driver to set always leads the clocks to be scaled up. Hence, round the clock-rate to the nearest frequency before deciding to scale.

Re: [PATCH v4 2/2] scsi: ufs-qcom: enter and exit hibern8 during clock scaling

years old, so you might want to elaborate on how come hibernation is now needed. Thanks, Avri Thanks for the review. Hibernation was needed since long actually. I guess it was never pushed upstream. Thanks, -asd -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum

Re: [PATCH v3 2/2] scsi: ufs-qcom: enter and exit hibern8 during clock scaling

Hi Pedro, On 11/11/2019 7:54 AM, Pedro Sousa wrote: Hi Asutosh, Please check comments. Sorry for missing out on this and thanks for your review. -Original Message- From: Asutosh Das Sent: Wednesday, October 23, 2019 5:49 PM To: c...@codeaurora.org; rna...@codeaurora.org;

Re: [PATCH v3 5/5] scsi: ufs: Fix possible VCC power drain during runtime suspend

Hi Stanley, On 5/16/2020 10:46 AM, Stanley Chu wrote: The commit "scsi: ufs: Fix WriteBooster flush during runtime suspend" promises essential resource, i.e., for UFS devices doing WriteBooster buffer flush and Auto BKOPs. However if device finishes its job but not resumed for a very long time,

Re: [PATCH v2 4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend

On 5/14/2020 8:01 AM, Stanley Chu wrote: Currently UFS host driver promises VCC supply if UFS device needs to do WriteBooster flush during runtime suspend. However the UFS specification mentions, "While the flushing operation is in progress, the device is in Active power mode." Therefore UFS

Re: [PATCH v1 4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend

On 5/14/2020 7:49 AM, Stanley Chu wrote: Hi Asutosh, On Thu, 2020-05-14 at 10:23 +0800, Stanley Chu wrote: Hi Asutosh, On Wed, 2020-05-13 at 12:31 -0700, Asutosh Das (asd) wrote: On 5/12/2020 3:47 AM, Stanley Chu wrote: Currently UFS host driver promises VCC supply if UFS device needs to do

Re: [PATCH v1 4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend

On 5/12/2020 3:47 AM, Stanley Chu wrote: Currently UFS host driver promises VCC supply if UFS device needs to do WriteBooster flush during runtime suspend. However the UFS specification mentions, "While the flushing operation is in progress, the device is in Active power mode." Therefore UFS

Re: [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy

On 5/12/2020 9:21 AM, Martin K. Petersen wrote: Hi Asutosh! Patchset looks good to me. Reviewed-by: Asutosh Das When you want to approve an entire series, please respond to the cover letter email. Otherwise the kernel.org tooling will only record the tag for the individual patch you are

Re: [PATCH v1 4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend

confirm that you've tested and found that with the previous code, the flush operation in the device was not happening. If so, please can you let me know the test-case that you ran to figure this out. I'd like to verify this at my end. -- Thanks, -asd -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, Linux Foundation Collaborative Project

Re: [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy

On 5/9/2020 2:37 AM, Stanley Chu wrote: Change the WriteBooster policy to keep VCC on during runtime suspend if available WriteBooster buffer is less than 80%. Signed-off-by: Stanley Chu --- drivers/scsi/ufs/ufs-mediatek.c | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH v1 3/5] scsi: ufs: customize flush threshold for WriteBooster

On 5/8/2020 10:15 AM, Stanley Chu wrote: Allow flush threshold for WriteBooster to be customizable by vendors. To achieve this, make the value as a variable in struct ufs_hba first. Signed-off-by: Stanley Chu --- drivers/scsi/ufs/ufshcd.c | 6 -- drivers/scsi/ufs/ufshcd.h | 1 + 2

Re: [PATCH v8 8/8] scsi: ufs: cleanup WriteBooster feature

On 5/8/2020 1:01 AM, Stanley Chu wrote: Small cleanup as below items, 1. Use ufshcd_is_wb_allowed() directly instead of ufshcd_wb_sup() since ufshcd_wb_sup() just returns the result of ufshcd_is_wb_allowed(). 2. In ufshcd_suspend(), "else if (!ufshcd_is_runtime_pm(pm_op)) can be

debian-www@lists.debian.org

1. Agencja Reklamowa Logoworld, Konin, Poland 2. Commercial 3. https://logoworld.pl 4. We are running Debian on one of our workstation. We decided to work on Debian because we find it very usefull and handy.

Re: [PATCH 1/2] mmc: cqhci: replace NUM_SLOTS with cq_host->num_slots

On 2/8/2019 8:07 AM, Ritesh Harjani wrote: Hi Alamy, On 2/8/2019 1:00 AM, Alamy Liu wrote: It says in B.2.1 in the JESD84-B51.pdf (I don't have JESD84-B51A.pdf): /The TDL is located in a memory location known to the CQE, and is comprised of up to 32 fixed-size slots. Each slot is

Re: [ 1/1] scsi: qcom-ufs: Add support for bus voting using ICB framework

and ported to ufs-next. Let me check internally on this anyway. I'll wait to review the rest of the patch until rev 2, since it's hard to reason about the patch with all the downstream stuff in there. -Evan Hi Evan - thanks for the comments. -asd -- Qualcomm Innovation Center, Inc. is a member

Re: [ 1/1] scsi: qcom-ufs: Add support for bus voting using ICB framework

+ } + } + + qsd->usecase = usecase; + return qsd; +err: + if (mem_err) { + for (; i > 0; i--) + kfree(usecase[i].vec); + } + return NULL; +} We wouldn't need all the above DT parsing if we add a sdm845

[Qemu-devel] [Bug 1703506] Re: SMT not supported by QEMU on AMD Ryzen CPU

I got it to work: sudo nano /etc/modprobe.d/kvm.conf add "options kvm ignore_msrs=1" (without quotes) reboot Then changing "-machine q35" to "-machine pc" kept it from crashing randomly. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Qemu-devel] [Bug 1703506] Re: SMT not supported by QEMU on AMD Ryzen CPU

Error I see in terminal: AMD CPU doesn't support hyperthreading. Please configure -smp options properly. Error I see in my windows 10 vm: SYSTEM THREAD EXCEPTION NOT HANDLED I am unable to use Qemu at all. Serious problem. CPU: AMD Ryzen 5 1600X Six-Core Processor × 6 -- You received this bug

Re: [PATCH 1/4] scsi: ufs: add quirk to fix mishandling utrlclr/utmrlclr

On 5/6/2018 3:44 PM, Alim Akhtar wrote: In the right behavior, setting the bit to '0' indicates clear and '1' indicates no change. If host controller handles this the other way, UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used. Signed-off-by: Seungwon Jeon Signed-off-by: Alim

Re: [PATCH 1/4] scsi: ufs: add quirk to fix mishandling utrlclr/utmrlclr

On 5/6/2018 3:44 PM, Alim Akhtar wrote: In the right behavior, setting the bit to '0' indicates clear and '1' indicates no change. If host controller handles this the other way, UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used. Signed-off-by: Seungwon Jeon Signed-off-by: Alim

Re: [PATCH 1/4] scsi: ufs: add quirk to fix mishandling utrlclr/utmrlclr

On 5/6/2018 3:44 PM, Alim Akhtar wrote: In the right behavior, setting the bit to '0' indicates clear and '1' indicates no change. If host controller handles this the other way, UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used. Signed-off-by: Seungwon Jeon Signed-off-by: Alim Akhtar ---

[jira] [Created] (WEEX-246) weex 文档中部分链接地址not found

asd-kk created WEEX-246: --- Summary: weex 文档中部分链接地址not found Key: WEEX-246 URL: https://issues.apache.org/jira/browse/WEEX-246 Project: Weex Issue Type: Bug Reporter: asd-kk

Re: [PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

nc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. Hi Miguel Thanks for the review. I'll check this and put up the changes in v2. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

ruct workqueue_struct *clk_gating_workq; }; struct ufs_saved_pwr_info { -- Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. Hi Miguel Thanks for the review. I'

Re: [PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

nc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. Hi Miguel Thanks for the review. I'll check this and put up the changes in v2. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/9] scsi: ufs: Allowing power mode change

Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. Hi Choi Thanks for the review. No - I can't say if every host has the same issue. However, I get your point. It could be done with a quirk. I'll fix this in v2 after collating all the co

Re: [PATCH 1/9] scsi: ufs: Allowing power mode change

me issue. However, I get your point. It could be done with a quirk. I'll fix this in v2 after collating all the comments from the rest of the patches. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/9] scsi: ufs: Allowing power mode change

Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. Hi Choi Thanks for the review. No - I can't say if every host has the same issue. However, I get your point. It could be done with a quirk. I'll fix this in v2 after collating all the co

Re: [PATCH 5/9] scsi: ufs: add reference counting for scsi block requests

uld be used for the reference counting. This will allow to avoid usage of the locks. 2. Why are the ufshcd_scsi_block_requests/ ufshcd_scsi_unblock_requests functions not defined as static? They are not used outside ufshcd.c. Regards Stanislav Hi Thanks. Let me check this and get back. I'll wait for comm

Re: [PATCH 5/9] scsi: ufs: add reference counting for scsi block requests

uld be used for the reference counting. This will allow to avoid usage of the locks. 2. Why are the ufshcd_scsi_block_requests/ ufshcd_scsi_unblock_requests functions not defined as static? They are not used outside ufshcd.c. Regards Stanislav Hi Thanks. Let me check this and get back. I'll wait for comm

Re: [PATCH 5/9] scsi: ufs: add reference counting for scsi block requests

not used outside ufshcd.c. Regards Stanislav Hi Thanks. Let me check this and get back. I'll wait for comments on the other patches before posting a v2. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

On 2/2/2018 8:53 AM, Asutosh Das (asd) wrote: On 1/31/2018 1:09 PM, Avri Altman wrote: Hi, Can you elaborate how this can even happen? Isn't the interrupt aggregation capability should attend for those cases? Thanks, Avri -Original Message- From: linux-scsi-ow...@vger.kernel.org

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

On 2/2/2018 8:53 AM, Asutosh Das (asd) wrote: On 1/31/2018 1:09 PM, Avri Altman wrote: Hi, Can you elaborate how this can even happen? Isn't the interrupt aggregation capability should attend for those cases? Thanks, Avri -Original Message- From: linux-scsi-ow...@vger.kernel.org

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

On 2/2/2018 8:53 AM, Asutosh Das (asd) wrote: On 1/31/2018 1:09 PM, Avri Altman wrote: Hi, Can you elaborate how this can even happen? Isn't the interrupt aggregation capability should attend for those cases? Thanks, Avri -Original Message- From: linux-scsi-ow...@vger.kernel.org

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

have the data to back that up now though. However, I can code it up and check it. Will post it in some time. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

yes - interrupt aggregation makes sense here. But there were some performance concerns with it; well, I don't have the data to back that up now though. However, I can code it up and check it. Will post it in some time. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,

Re: [PATCH 1/1] scsi: ufs: make sure all interrupts are processed

have the data to back that up now though. However, I can code it up and check it. Will post it in some time. -asd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/1] scsi: ufs-qcom: remove broken hci version quirk

On 1/30/2018 11:33 AM, Vivek Gautam wrote: Hi Asutosh, On 1/30/2018 10:11 AM, Asutosh Das wrote: From: Subhash Jadavani UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION is only applicable for QCOM UFS host controller version 2.x.y and this has been fixed from version 3.x.y

Re: [PATCH 1/1] scsi: ufs-qcom: remove broken hci version quirk

On 1/30/2018 11:33 AM, Vivek Gautam wrote: Hi Asutosh, On 1/30/2018 10:11 AM, Asutosh Das wrote: From: Subhash Jadavani UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION is only applicable for QCOM UFS host controller version 2.x.y and this has been fixed from version 3.x.y onwards, hence this change

Re: [PATCH 1/1] scsi: ufs-qcom: remove broken hci version quirk

On 1/30/2018 11:33 AM, Vivek Gautam wrote: Hi Asutosh, On 1/30/2018 10:11 AM, Asutosh Das wrote: From: Subhash Jadavani UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION is only applicable for QCOM UFS host controller version 2.x.y and this has been fixed from version 3.x.y

[jira] [Created] (ACE-629) asd

asd palkon created ACE-629: -- Summary: asd Key: ACE-629 URL: https://issues.apache.org/jira/browse/ACE-629 Project: ACE Issue Type: New Feature Reporter: asd palkon Priority

Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code

eering -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Asutosh Das (asd) Qualcomm Innovation Center, Inc. is a member of Code Aurora

Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code

: send the line "unsubscribe linux-arm-msm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Asutosh Das (asd) Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code

eering -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Asutosh Das (asd) Qualcomm Innovation Center, Inc. is a member of Code Aurora

RE: reelect cluster_leader

I am sorry. Please ignore this email. I will send another e-mail account. Best Regards, -Original Message- From: TED ASD Nakabayashi Minoru Sent: Monday, July 10, 2017 12:14 PM To: riak-users@lists.basho.com Cc: TED ASD Nakabayashi Minoru Subject: reelect cluster_leader Hello, I am

reelect cluster_leader

Hello, I am facing issue #685 using Riak KV 2.1.3. https://github.com/basho/riak/issues/685 I am supposing reelect a cluster_leader might be the workaround. Does anyone know how to reelect a cluster_leader by riak attach ? I used to doing exit(riak_repl2_leader:helper_pid(), reelect) in 1.4.x.

Re: [ufs]: [scsi]: BUG: spinlock recursion on CPU#4

On 6/1/2017 7:32 PM, Bart Van Assche wrote: On Thu, 2017-06-01 at 12:28 +0530, Asutosh Das (asd) wrote: Please can you check if this is actually a bug and my understanding is correct. Hello Asutosh, Spinlock recursion is always a bug. With what kernel version did you encounter

  1   2   3   4   5   >