From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Cc: mark.rutland@arm.com, alsa-devel@alsa-project.org, michael.opdenacker@free-electrons.com, poeschel@lemonage.de, andreas.noever@gmail.com, gong.chen@linux.intel.com, arnd@arndb.de, kheitke@audience.com, treding@nvidia.com, devicetree@vger.kernel.org, james.hogan@imgtec.com, pawel.moll@arm.com, linux-arm-msm@vger.kernel.org, sharon.dvir1@mail.huji.ac.il, robh+dt@kernel.org, sdharia@codeaurora.org, alan@linux.intel.com, bp@suse.de, mathieu.poirier@linaro.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, broonie@kernel.org, daniel@ffwll.ch, jkosina@suse.cz, joe@perches.com, davem@davemloft.net Subject: Re: [Patch v6 3/7] slimbus: qcom: Add Qualcomm Slimbus controller driver Date: Sat, 7 Oct 2017 11:24:40 +0100 [thread overview] Message-ID: <91b69203-65a7-175f-53bd-aeb6ee787233@linaro.org> (raw) In-Reply-To: <20171007074539.mdvl5nw66it67l3g@latitude> Thanks for the review comments On 07/10/17 08:45, Jonathan Neuschäfer wrote: > Hi, > > On Fri, Oct 06, 2017 at 05:51:32PM +0200, srinivas.kandagatla@linaro.org wrote: >> From: Sagar Dharia <sdharia@codeaurora.org> >> >> This controller driver programs manager, interface, and framer >> devices for Qualcomm's slimbus HW block. >> Manager component currently implements logical address setting, >> and messaging interface. >> Interface device reports bus synchronization information, and framer >> device clocks the bus from the time it's woken up, until clock-pause >> is executed by the manager device. >> >> Signed-off-by: Sagar Dharia <sdharia@codeaurora.org> >> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> >> --- >> .../devicetree/bindings/slimbus/slim-qcom-ctrl.txt | 43 ++ >> drivers/slimbus/Kconfig | 9 + >> drivers/slimbus/Makefile | 3 + >> drivers/slimbus/slim-qcom-ctrl.c | 594 +++++++++++++++++++++ >> drivers/slimbus/slim-qcom.h | 63 +++ >> 5 files changed, 712 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> create mode 100644 drivers/slimbus/slim-qcom-ctrl.c >> create mode 100644 drivers/slimbus/slim-qcom.h >> >> diff --git a/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt b/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> new file mode 100644 >> index 0000000..081110d >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> @@ -0,0 +1,43 @@ >> +Qualcomm SLIMBUS controller >> +This controller is used if applications processor driver controls slimbus >> +master component. >> + >> +Required properties: >> + >> + - #address-cells - refer to Documentation/devicetree/bindings/slimbus/bus.txt >> + - #size-cells - refer to Documentation/devicetree/bindings/slimbus/bus.txt >> + >> + - reg : Offset and length of the register region(s) for the device >> + - reg-names : Register region name(s) referenced in reg above >> + Required register resource entries are: >> + "ctrl": Physical adderess of controller register blocks > > s/adderess/address/ Will fix this in next version. > >> +} > [...] >> +static void msm_slim_prg_slew(struct platform_device *pdev, >> + struct msm_slim_ctrl *dev) >> +{ >> + void __iomem *slew_reg; >> + >> + /* SLEW RATE register for this slimbus */ >> + dev->slew_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM, >> + "slew"); >> + if (!dev->slew_mem) { >> + dev_warn(&pdev->dev, "no slimbus slew resource\n"); >> + return; >> + } >> + >> + slew_reg = devm_ioremap(&pdev->dev, dev->slew_mem->start, >> + resource_size(dev->slew_mem)); > > How often will the driver program a slew rate? > This should be programmed only once after power on. > If it's often, you'll have a "soft" memory leak over the life time of a > SLIM controller instance, because the mappings for slew_reg will > accumulate in the driver instance's devm area until they are all freed > in the end (If I'm reading the code correctly). I think you'll either > have to unmap slew_reg when this function returns (and not use devm), or > cache slew_reg so that subsequent calls to msm_slim_prg_slew won't > create more mappings. Yep .. I revisit this part once again before sending next version to see if we can do any better! > >> + if (!slew_reg) { >> + dev_err(dev->dev, "slew register mapping failed"); >> + release_mem_region(dev->slew_mem->start, >> + resource_size(dev->slew_mem)); >> + dev->slew_mem = NULL; >> + return; >> + } >> + writel_relaxed(1, slew_reg); >> + /* Make sure slimbus-slew rate enabling goes through */ >> + wmb(); >> +} >> + >> +static int msm_slim_probe(struct platform_device *pdev) >> +{ >> + struct msm_slim_ctrl *dev; >> + struct slim_controller *ctrl; >> + struct resource *slim_mem; >> + struct resource *irq; >> + struct clk *hclk, *rclk; >> + int ret; >> + >> + hclk = devm_clk_get(&pdev->dev, "iface_clk"); >> + if (IS_ERR(hclk)) >> + return PTR_ERR(hclk); >> + >> + rclk = devm_clk_get(&pdev->dev, "core_clk"); >> + if (IS_ERR(rclk)) { >> + /* unlikely that this is probe-defer */ >> + dev_err(&pdev->dev, "rclk get failed:%ld\n", PTR_ERR(rclk)); >> + return PTR_ERR(rclk); >> + } >> + >> + ret = clk_set_rate(rclk, SLIM_ROOT_FREQ); >> + if (ret) { >> + dev_err(&pdev->dev, "ref-clock set-rate failed:%d\n", ret); >> + return ret; >> + } >> + >> + slim_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM, "ctrl"); >> + if (!slim_mem) { >> + dev_err(&pdev->dev, "no slimbus physical memory resource\n"); >> + return -ENODEV; >> + } >> + >> + irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0); >> + if (!irq) { >> + dev_err(&pdev->dev, "no slimbus IRQ resource\n"); >> + return -ENODEV; >> + } >> + >> + dev = devm_kzalloc(&pdev->dev, sizeof(*dev), GFP_KERNEL); >> + if (!dev) >> + return -ENOMEM; >> + >> + dev->hclk = hclk; >> + dev->rclk = rclk; >> + ctrl = &dev->ctrl; >> + dev->dev = &pdev->dev; >> + platform_set_drvdata(pdev, dev); >> + slim_set_ctrldata(&dev->ctrl, dev); >> + dev->base = devm_ioremap(dev->dev, slim_mem->start, >> + resource_size(slim_mem)); >> + if (!dev->base) { >> + dev_err(&pdev->dev, "IOremap failed\n"); >> + return -ENOMEM; >> + } >> + >> + dev->ctrl.set_laddr = msm_set_laddr; >> + dev->ctrl.xfer_msg = msm_xfer_msg; >> + dev->ctrl.tx.n = MSM_TX_MSGS; >> + dev->ctrl.rx.n = MSM_RX_MSGS; >> + dev->ctrl.tx.sl_sz = SLIM_MSGQ_BUF_LEN; >> + dev->ctrl.rx.sl_sz = SLIM_MSGQ_BUF_LEN; >> + >> + dev->irq = irq->start; >> + >> + INIT_WORK(&dev->wd, msm_slim_rxwq); >> + dev->rxwq = create_singlethread_workqueue("msm_slim_rx"); >> + if (!dev->rxwq) { >> + dev_err(dev->dev, "Failed to start Rx WQ\n"); >> + return -ENOMEM; >> + } >> + >> + dev->framer.rootfreq = SLIM_ROOT_FREQ >> 3; >> + dev->framer.superfreq = >> + dev->framer.rootfreq / SLIM_CL_PER_SUPERFRAME_DIV8; >> + dev->ctrl.a_framer = &dev->framer; >> + dev->ctrl.clkgear = SLIM_MAX_CLK_GEAR; >> + dev->ctrl.dev.parent = &pdev->dev; >> + dev->ctrl.dev.of_node = pdev->dev.of_node; >> + >> + msm_slim_prg_slew(pdev, dev); >> + >> + ret = devm_request_irq(&pdev->dev, dev->irq, msm_slim_interrupt, >> + IRQF_TRIGGER_HIGH, "msm_slim_irq", dev); >> + if (ret) { >> + dev_err(&pdev->dev, "request IRQ failed\n"); >> + goto err_request_irq_failed; >> + } >> + >> + ret = clk_prepare_enable(hclk); >> + if (ret) >> + goto err_hclk_enable_failed; >> + >> + ret = clk_prepare_enable(rclk); >> + if (ret) >> + goto err_rclk_enable_failed; >> + >> + >> + ctrl->tx.base = dma_alloc_coherent(&pdev->dev, >> + (ctrl->tx.sl_sz * ctrl->tx.n), >> + &ctrl->tx.phy, GFP_KERNEL); > > Use dmam_alloc_coherent? > Yep, makes sense.. Will use it as suggested. >> + if (!ctrl->tx.base) { >> + ret = -ENOMEM; >> + goto tx_alloc_failed; >> + } >> + >> + ctrl->rx.base = dma_alloc_coherent(&pdev->dev, >> + (ctrl->rx.sl_sz * ctrl->rx.n), >> + &ctrl->rx.phy, GFP_KERNEL); > _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Cc: gregkh@linuxfoundation.org, broonie@kernel.org, alsa-devel@alsa-project.org, sdharia@codeaurora.org, bp@suse.de, poeschel@lemonage.de, treding@nvidia.com, gong.chen@linux.intel.com, andreas.noever@gmail.com, alan@linux.intel.com, mathieu.poirier@linaro.org, daniel@ffwll.ch, jkosina@suse.cz, sharon.dvir1@mail.huji.ac.il, joe@perches.com, davem@davemloft.net, james.hogan@imgtec.com, michael.opdenacker@free-electrons.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kheitke@audience.com, linux-arm-msm@vger.kernel.org, arnd@arndb.de Subject: Re: [Patch v6 3/7] slimbus: qcom: Add Qualcomm Slimbus controller driver Date: Sat, 7 Oct 2017 11:24:40 +0100 [thread overview] Message-ID: <91b69203-65a7-175f-53bd-aeb6ee787233@linaro.org> (raw) In-Reply-To: <20171007074539.mdvl5nw66it67l3g@latitude> Thanks for the review comments On 07/10/17 08:45, Jonathan Neuschäfer wrote: > Hi, > > On Fri, Oct 06, 2017 at 05:51:32PM +0200, srinivas.kandagatla@linaro.org wrote: >> From: Sagar Dharia <sdharia@codeaurora.org> >> >> This controller driver programs manager, interface, and framer >> devices for Qualcomm's slimbus HW block. >> Manager component currently implements logical address setting, >> and messaging interface. >> Interface device reports bus synchronization information, and framer >> device clocks the bus from the time it's woken up, until clock-pause >> is executed by the manager device. >> >> Signed-off-by: Sagar Dharia <sdharia@codeaurora.org> >> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> >> --- >> .../devicetree/bindings/slimbus/slim-qcom-ctrl.txt | 43 ++ >> drivers/slimbus/Kconfig | 9 + >> drivers/slimbus/Makefile | 3 + >> drivers/slimbus/slim-qcom-ctrl.c | 594 +++++++++++++++++++++ >> drivers/slimbus/slim-qcom.h | 63 +++ >> 5 files changed, 712 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> create mode 100644 drivers/slimbus/slim-qcom-ctrl.c >> create mode 100644 drivers/slimbus/slim-qcom.h >> >> diff --git a/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt b/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> new file mode 100644 >> index 0000000..081110d >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt >> @@ -0,0 +1,43 @@ >> +Qualcomm SLIMBUS controller >> +This controller is used if applications processor driver controls slimbus >> +master component. >> + >> +Required properties: >> + >> + - #address-cells - refer to Documentation/devicetree/bindings/slimbus/bus.txt >> + - #size-cells - refer to Documentation/devicetree/bindings/slimbus/bus.txt >> + >> + - reg : Offset and length of the register region(s) for the device >> + - reg-names : Register region name(s) referenced in reg above >> + Required register resource entries are: >> + "ctrl": Physical adderess of controller register blocks > > s/adderess/address/ Will fix this in next version. > >> +} > [...] >> +static void msm_slim_prg_slew(struct platform_device *pdev, >> + struct msm_slim_ctrl *dev) >> +{ >> + void __iomem *slew_reg; >> + >> + /* SLEW RATE register for this slimbus */ >> + dev->slew_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM, >> + "slew"); >> + if (!dev->slew_mem) { >> + dev_warn(&pdev->dev, "no slimbus slew resource\n"); >> + return; >> + } >> + >> + slew_reg = devm_ioremap(&pdev->dev, dev->slew_mem->start, >> + resource_size(dev->slew_mem)); > > How often will the driver program a slew rate? > This should be programmed only once after power on. > If it's often, you'll have a "soft" memory leak over the life time of a > SLIM controller instance, because the mappings for slew_reg will > accumulate in the driver instance's devm area until they are all freed > in the end (If I'm reading the code correctly). I think you'll either > have to unmap slew_reg when this function returns (and not use devm), or > cache slew_reg so that subsequent calls to msm_slim_prg_slew won't > create more mappings. Yep .. I revisit this part once again before sending next version to see if we can do any better! > >> + if (!slew_reg) { >> + dev_err(dev->dev, "slew register mapping failed"); >> + release_mem_region(dev->slew_mem->start, >> + resource_size(dev->slew_mem)); >> + dev->slew_mem = NULL; >> + return; >> + } >> + writel_relaxed(1, slew_reg); >> + /* Make sure slimbus-slew rate enabling goes through */ >> + wmb(); >> +} >> + >> +static int msm_slim_probe(struct platform_device *pdev) >> +{ >> + struct msm_slim_ctrl *dev; >> + struct slim_controller *ctrl; >> + struct resource *slim_mem; >> + struct resource *irq; >> + struct clk *hclk, *rclk; >> + int ret; >> + >> + hclk = devm_clk_get(&pdev->dev, "iface_clk"); >> + if (IS_ERR(hclk)) >> + return PTR_ERR(hclk); >> + >> + rclk = devm_clk_get(&pdev->dev, "core_clk"); >> + if (IS_ERR(rclk)) { >> + /* unlikely that this is probe-defer */ >> + dev_err(&pdev->dev, "rclk get failed:%ld\n", PTR_ERR(rclk)); >> + return PTR_ERR(rclk); >> + } >> + >> + ret = clk_set_rate(rclk, SLIM_ROOT_FREQ); >> + if (ret) { >> + dev_err(&pdev->dev, "ref-clock set-rate failed:%d\n", ret); >> + return ret; >> + } >> + >> + slim_mem = platform_get_resource_byname(pdev, IORESOURCE_MEM, "ctrl"); >> + if (!slim_mem) { >> + dev_err(&pdev->dev, "no slimbus physical memory resource\n"); >> + return -ENODEV; >> + } >> + >> + irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0); >> + if (!irq) { >> + dev_err(&pdev->dev, "no slimbus IRQ resource\n"); >> + return -ENODEV; >> + } >> + >> + dev = devm_kzalloc(&pdev->dev, sizeof(*dev), GFP_KERNEL); >> + if (!dev) >> + return -ENOMEM; >> + >> + dev->hclk = hclk; >> + dev->rclk = rclk; >> + ctrl = &dev->ctrl; >> + dev->dev = &pdev->dev; >> + platform_set_drvdata(pdev, dev); >> + slim_set_ctrldata(&dev->ctrl, dev); >> + dev->base = devm_ioremap(dev->dev, slim_mem->start, >> + resource_size(slim_mem)); >> + if (!dev->base) { >> + dev_err(&pdev->dev, "IOremap failed\n"); >> + return -ENOMEM; >> + } >> + >> + dev->ctrl.set_laddr = msm_set_laddr; >> + dev->ctrl.xfer_msg = msm_xfer_msg; >> + dev->ctrl.tx.n = MSM_TX_MSGS; >> + dev->ctrl.rx.n = MSM_RX_MSGS; >> + dev->ctrl.tx.sl_sz = SLIM_MSGQ_BUF_LEN; >> + dev->ctrl.rx.sl_sz = SLIM_MSGQ_BUF_LEN; >> + >> + dev->irq = irq->start; >> + >> + INIT_WORK(&dev->wd, msm_slim_rxwq); >> + dev->rxwq = create_singlethread_workqueue("msm_slim_rx"); >> + if (!dev->rxwq) { >> + dev_err(dev->dev, "Failed to start Rx WQ\n"); >> + return -ENOMEM; >> + } >> + >> + dev->framer.rootfreq = SLIM_ROOT_FREQ >> 3; >> + dev->framer.superfreq = >> + dev->framer.rootfreq / SLIM_CL_PER_SUPERFRAME_DIV8; >> + dev->ctrl.a_framer = &dev->framer; >> + dev->ctrl.clkgear = SLIM_MAX_CLK_GEAR; >> + dev->ctrl.dev.parent = &pdev->dev; >> + dev->ctrl.dev.of_node = pdev->dev.of_node; >> + >> + msm_slim_prg_slew(pdev, dev); >> + >> + ret = devm_request_irq(&pdev->dev, dev->irq, msm_slim_interrupt, >> + IRQF_TRIGGER_HIGH, "msm_slim_irq", dev); >> + if (ret) { >> + dev_err(&pdev->dev, "request IRQ failed\n"); >> + goto err_request_irq_failed; >> + } >> + >> + ret = clk_prepare_enable(hclk); >> + if (ret) >> + goto err_hclk_enable_failed; >> + >> + ret = clk_prepare_enable(rclk); >> + if (ret) >> + goto err_rclk_enable_failed; >> + >> + >> + ctrl->tx.base = dma_alloc_coherent(&pdev->dev, >> + (ctrl->tx.sl_sz * ctrl->tx.n), >> + &ctrl->tx.phy, GFP_KERNEL); > > Use dmam_alloc_coherent? > Yep, makes sense.. Will use it as suggested. >> + if (!ctrl->tx.base) { >> + ret = -ENOMEM; >> + goto tx_alloc_failed; >> + } >> + >> + ctrl->rx.base = dma_alloc_coherent(&pdev->dev, >> + (ctrl->rx.sl_sz * ctrl->rx.n), >> + &ctrl->rx.phy, GFP_KERNEL); >
next prev parent reply other threads:[~2017-10-07 10:24 UTC|newest] Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-06 15:51 [Patch v6 0/7] Introduce framework for SLIMbus device drivers srinivas.kandagatla 2017-10-06 15:51 ` [Patch v6 1/7] slimbus: Device management on SLIMbus srinivas.kandagatla 2017-10-06 15:51 ` srinivas.kandagatla 2017-10-10 10:05 ` Charles Keepax 2017-10-10 10:05 ` [alsa-devel] " Charles Keepax 2017-10-10 12:34 ` Srinivas Kandagatla 2017-10-10 12:34 ` [alsa-devel] " Srinivas Kandagatla 2017-10-10 12:56 ` Charles Keepax 2017-10-10 12:56 ` [alsa-devel] " Charles Keepax 2017-10-11 10:23 ` Mark Brown 2017-10-11 10:23 ` [alsa-devel] " Mark Brown [not found] ` <20171006155136.4682-2-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2017-10-07 4:14 ` Jonathan Neuschäfer 2017-10-07 4:14 ` Jonathan Neuschäfer 2017-10-07 10:24 ` Srinivas Kandagatla 2017-10-07 10:24 ` Srinivas Kandagatla 2017-10-10 10:45 ` [alsa-devel] " Vinod Koul 2017-10-10 10:45 ` Vinod Koul 2017-10-10 12:34 ` Srinivas Kandagatla 2017-10-10 16:49 ` Vinod Koul 2017-10-10 16:49 ` [alsa-devel] " Vinod Koul 2017-10-10 17:21 ` Srinivas Kandagatla 2017-10-11 4:07 ` Vinod Koul 2017-10-11 9:42 ` Srinivas Kandagatla 2017-10-11 10:21 ` Vinod Koul 2017-10-11 11:23 ` Srinivas Kandagatla 2017-10-13 19:26 ` Rob Herring 2017-10-13 19:26 ` Rob Herring 2017-10-16 9:28 ` Srinivas Kandagatla 2017-10-16 9:28 ` Srinivas Kandagatla 2017-10-17 6:23 ` Bjorn Andersson 2017-10-17 6:23 ` Bjorn Andersson 2017-10-18 16:38 ` Srinivas Kandagatla 2017-10-18 16:38 ` Srinivas Kandagatla [not found] ` <1a1d2777-be69-98ca-afba-0ffd0e3dd80f-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2017-11-01 23:08 ` Bjorn Andersson 2017-11-01 23:08 ` Bjorn Andersson 2017-10-25 0:16 ` Stephen Boyd 2017-10-25 0:16 ` Stephen Boyd 2017-10-12 11:01 ` [alsa-devel] " Sanyog Kale 2017-10-12 13:26 ` Srinivas Kandagatla 2017-10-12 13:26 ` Srinivas Kandagatla 2017-10-23 9:06 ` Mark Brown 2017-10-06 15:51 ` [Patch v6 3/7] slimbus: qcom: Add Qualcomm Slimbus controller driver srinivas.kandagatla 2017-10-07 7:45 ` Jonathan Neuschäfer 2017-10-07 10:24 ` Srinivas Kandagatla [this message] 2017-10-07 10:24 ` Srinivas Kandagatla 2017-10-13 19:17 ` Rob Herring 2017-10-16 9:28 ` Srinivas Kandagatla 2017-10-18 7:27 ` Bjorn Andersson 2017-10-18 16:39 ` Srinivas Kandagatla 2017-10-06 15:51 ` [Patch v6 4/7] slimbus: Add support for 'clock-pause' feature srinivas.kandagatla 2017-10-07 8:06 ` Jonathan Neuschäfer 2017-10-07 10:24 ` Srinivas Kandagatla [not found] ` <20171006155136.4682-1-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2017-10-06 15:51 ` [Patch v6 2/7] slimbus: Add messaging APIs to slimbus framework srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A 2017-10-06 15:51 ` srinivas.kandagatla 2017-10-07 6:42 ` Jonathan Neuschäfer 2017-10-07 10:24 ` Srinivas Kandagatla 2017-10-07 10:24 ` Srinivas Kandagatla 2017-10-07 12:29 ` Jonathan Neuschäfer 2017-10-10 12:19 ` Charles Keepax 2017-10-10 12:19 ` [alsa-devel] " Charles Keepax 2017-10-10 13:01 ` Srinivas Kandagatla 2017-10-10 13:01 ` [alsa-devel] " Srinivas Kandagatla 2017-10-11 4:38 ` Vinod Koul 2017-10-11 7:53 ` Arnd Bergmann 2017-10-11 7:53 ` Arnd Bergmann 2017-10-11 9:42 ` Srinivas Kandagatla 2017-10-11 9:42 ` [alsa-devel] " Srinivas Kandagatla [not found] ` <aa117cb8-ba59-894c-5a82-1b38facfa841-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2017-10-11 10:24 ` Vinod Koul 2017-10-11 10:24 ` Vinod Koul 2017-10-11 11:12 ` Srinivas Kandagatla 2017-10-18 6:15 ` Bjorn Andersson 2017-10-18 16:39 ` Srinivas Kandagatla 2017-10-20 5:00 ` Bjorn Andersson 2017-10-20 5:00 ` Bjorn Andersson 2017-10-06 15:51 ` [Patch v6 5/7] slimbus: qcom: Add runtime-pm support using clock-pause feature srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A 2017-10-06 15:51 ` srinivas.kandagatla 2017-10-07 8:22 ` Jonathan Neuschäfer 2017-10-07 10:25 ` Srinivas Kandagatla 2017-10-06 15:51 ` [Patch v6 7/7] MAINTAINERS: Add SLIMbus maintainer srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A 2017-10-06 15:51 ` srinivas.kandagatla 2017-10-20 5:00 ` Bjorn Andersson 2017-10-20 5:00 ` Bjorn Andersson 2017-10-06 15:51 ` [Patch v6 6/7] regmap: add SLIMBUS support srinivas.kandagatla 2017-10-07 5:02 ` Jonathan Neuschäfer 2017-10-07 10:25 ` Srinivas Kandagatla 2017-10-20 5:00 ` Bjorn Andersson 2017-10-20 5:00 ` Bjorn Andersson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=91b69203-65a7-175f-53bd-aeb6ee787233@linaro.org \ --to=srinivas.kandagatla@linaro.org \ --cc=alan@linux.intel.com \ --cc=alsa-devel@alsa-project.org \ --cc=andreas.noever@gmail.com \ --cc=arnd@arndb.de \ --cc=bp@suse.de \ --cc=broonie@kernel.org \ --cc=daniel@ffwll.ch \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=gong.chen@linux.intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=j.neuschaefer@gmx.net \ --cc=james.hogan@imgtec.com \ --cc=jkosina@suse.cz \ --cc=joe@perches.com \ --cc=kheitke@audience.com \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=mathieu.poirier@linaro.org \ --cc=michael.opdenacker@free-electrons.com \ --cc=pawel.moll@arm.com \ --cc=poeschel@lemonage.de \ --cc=robh+dt@kernel.org \ --cc=sdharia@codeaurora.org \ --cc=sharon.dvir1@mail.huji.ac.il \ --cc=treding@nvidia.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.