| Message ID | cover.1687945879.git.quic_schowdhu@quicinc.com |
|---|---|
| Headers | show |
| Series | misc: Add driver support for Data Capture and Compare unit(DCC) | expand |
On Wed, Jun 28, 2023 at 05:18:36AM -0600, Rob Herring wrote: > > On Wed, 28 Jun 2023 15:53:30 +0530, Souradeep Chowdhury wrote: > > Add the device tree bindings for Data Capture and Compare(DCC). > > > > Signed-off-by: Souradeep Chowdhury <quic_schowdhu@quicinc.com> > > Reviewed-by: Rob Herring <robh@kernel.org> > > Reviewed-by: Bjorn Andersson <andersson@kernel.org> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > --- > > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 +++++++++++++++++++ > > 1 file changed, 44 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.example.dtb: /example-0/pmic: failed to match any schema with compatible: ['ti,twl6035-pmic', 'ti,palmas-pmic'] > Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.example.dtb: /example-0/pmic: failed to match any schema with compatible: ['ti,twl6035-pmic', 'ti,palmas-pmic'] > Documentation/devicetree/bindings/i2c/qcom,i2c-cci.example.dtb: /example-0/cci@ac4a000/i2c-bus@1/camera@60: failed to match any schema with compatible: ['ovti,ov7251'] > Documentation/devicetree/bindings/net/marvell,mvusb.example.dtb: /example-0/usb/mdio@1/switch@0: failed to match any schema with compatible: ['marvell,mv88e6190'] > Documentation/devicetree/bindings/net/qca,ar71xx.example.dtb: /example-0/ethernet@1a000000/mdio/switch@10: failed to match any schema with compatible: ['qca,ar9331-switch'] > Documentation/devicetree/bindings/memory-controllers/ingenic,nemc.example.dtb: /example-0/memory-controller@13410000/ethernet@6: failed to match any schema with compatible: ['davicom,dm9000'] > Documentation/devicetree/bindings/reset/hisilicon,hi3660-reset.example.dtb: /example-0/iomcu@ffd7e000: failed to match any schema with compatible: ['hisilicon,hi3660-iomcu', 'syscon'] > Documentation/devicetree/bindings/leds/common.example.dtb: /example-2/i2c/led-controller@30: failed to match any schema with compatible: ['panasonic,an30259a'] > Documentation/devicetree/bindings/dma/dma-router.example.dtb: /example-0/dma-router@4a002b78: failed to match any schema with compatible: ['ti,dra7-dma-crossbar'] > Documentation/devicetree/bindings/dma/dma-controller.example.dtb: /example-0/dma-controller@48000000: failed to match any schema with compatible: ['ti,omap-sdma'] > Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: /example-0/parent/i2c/camera@36: failed to match any schema with compatible: ['ovti,ov5695'] > Documentation/devicetree/bindings/clock/sprd,sc9863a-clk.example.dtb: /example-1/syscon@20e00000: failed to match any schema with compatible: ['sprd,sc9863a-glbregs', 'syscon', 'simple-mfd'] > Documentation/devicetree/bindings/clock/milbeaut-clock.example.dtb: /example-2/serial@1e700010: failed to match any schema with compatible: ['socionext,milbeaut-usio-uart'] > Documentation/devicetree/bindings/arm/hisilicon/controller/cpuctrl.example.dtb: /example-0/cpuctrl@a22000/clock@0: failed to match any schema with compatible: ['hisilicon,hix5hd2-clock'] > Documentation/devicetree/bindings/arm/hisilicon/controller/hi3798cv200-perictrl.example.dtb: /example-0/peripheral-controller@8a20000/phy@850: failed to match any schema with compatible: ['hisilicon,hi3798cv200-combphy'] > Documentation/devicetree/bindings/arm/hisilicon/controller/sysctrl.example.dtb: /example-0/system-controller@802000/clock@0: failed to match any schema with compatible: ['hisilicon,hi3620-clock'] > Documentation/devicetree/bindings/sound/audio-graph-card2.example.dtb: /example-0/cpu: failed to match any schema with compatible: ['cpu-driver'] > Documentation/devicetree/bindings/sound/audio-graph-card2.example.dtb: /example-0/codec: failed to match any schema with compatible: ['codec-driver'] > Documentation/devicetree/bindings/input/sprd,sc27xx-vibrator.example.dtb: /example-0/pmic@0: failed to match any schema with compatible: ['sprd,sc2731'] > Documentation/devicetree/bindings/input/mediatek,pmic-keys.example.dtb: /example-0/pmic: failed to match any schema with compatible: ['mediatek,mt6397'] > Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.example.dtb: /example-0/avs-monitor@7d5d2000: failed to match any schema with compatible: ['brcm,bcm2711-avs-monitor', 'syscon', 'simple-mfd'] > Documentation/devicetree/bindings/thermal/imx-thermal.example.dtb: /example-0/anatop@20c8000: failed to match any schema with compatible: ['fsl,imx6q-anatop', 'syscon', 'simple-mfd'] This can be ignored. Rob
On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > DCC(Data Capture and Compare) is a DMA engine designed for debugging purposes. > In case of a system crash or manual software triggers by the user the DCC hardware > stores the value at the register addresses which can be used for debugging purposes. > The DCC driver provides the user with debugfs interface to configure the register > addresses. The options that the DCC hardware provides include reading from registers, > writing to registers, first reading and then writing to registers and looping > through the values of the same register. > > In certain cases a register write needs to be executed for accessing the rest of the > registers, also the user might want to record the changing values of a register with > time for which he has the option to use the loop feature. > > The options mentioned above are exposed to the user by debugfs files once the driver > is probed. The details and usage of this debugfs files are documented in > Documentation/ABI/testing/debugfs-driver-dcc. > > As an example let us consider a couple of debug scenarios where DCC has been proved to be > effective for debugging purposes:- > > i)TimeStamp Related Issue > > On SC7180, there was a coresight timestamp issue where it would occasionally be all 0 > instead of proper timestamp values. > > Proper timestamp: > Idx:3373; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x13004d8f5b7aa; CC=0x9e > > Zero timestamp: > Idx:3387; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x0; CC=0xa2 > > Now this is a non-fatal issue and doesn't need a system reset, but still needs > to be rootcaused and fixed for those who do care about coresight etm traces. > Since this is a timestamp issue, we would be looking for any timestamp related > clocks and such. > > We get all the clk register details from IP documentation and configure it > via DCC config_read debugfs node. Before that we set the current linked list. > > /* Program the linked list with the addresses */ > echo R 0x10c004 > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c008 > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c00c > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c010 > /sys/kernel/debug/qcom-dcc/../3/config > ..... and so on for other timestamp related clk registers > > /* Other way of specifying is in "addr len" pair, in below case it > specifies to capture 4 words starting 0x10C004 */ > > echo R 0x10C004 4 > /sys/kernel/debug/qcom-dcc/../3/config_read > > /* Enable DCC */ > echo 1 > /sys/kernel/debug/qcom-dcc/../3/enable > > /* Run the timestamp test for working case */ > > /* Send SW trigger */ > echo 1 > /sys/kernel/debug/qcom-dcc/../trigger > > /* Read SRAM */ > cat /dev/dcc_sram > dcc_sram1.bin > > /* Run the timestamp test for non-working case */ > > /* Send SW trigger */ > echo 1 > /sys/kernel/debug/qcom-dcc/../trigger > > /* Read SRAM */ > cat /dev/dcc_sram > dcc_sram2.bin > > Get the parser from [1] and checkout the latest branch. > > /* Parse the SRAM bin */ > python dcc_parser.py -s dcc_sram1.bin --v2 -o output/ > python dcc_parser.py -s dcc_sram2.bin --v2 -o output/ > > Sample parsed output of dcc_sram1.bin: > > <hwioDump version="1"> > <timestamp>03/14/21</timestamp> > <generator>Linux DCC Parser</generator> > <chip name="None" version="None"> > <register address="0x0010c004" value="0x80000000" /> > <register address="0x0010c008" value="0x00000008" /> > <register address="0x0010c00c" value="0x80004220" /> > <register address="0x0010c010" value="0x80000000" /> > </chip> > <next_ll_offset>next_ll_offset : 0x1c </next_ll_offset> > </hwioDump> > > ii)NOC register errors > > A particular class of registers called NOC which are functional registers was reporting > errors while logging the values.To trace these errors the DCC has been used effectively. > The steps followed were similar to the ones mentioned above. > In addition to NOC registers a few other dependent registers were configured in DCC to > monitor it's values during a crash. A look at the dependent register values revealed that > the crash was happening due to a secured access to one of these dependent registers. > All these debugging activity and finding the root cause was achieved using DCC. > > DCC parser is available at the following open source location > > https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser > > Changes in v25 > > * Updated the documentation of the structure dcc_config_entry as per the comments in V23 > * Updated the documentation of the dcc Kconfig definition as per comment in V24 > * Used u64 where applicable > * Removed the mutex locks where it is not needed > * Removed the use of unlikely keyword > * Renamed "nr_link_list" to "max_link_list" > > Souradeep Chowdhury (3): > dt-bindings: misc: qcom,dcc: Add the dtschema > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > support > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > MAINTAINERS | 8 + > drivers/misc/Kconfig | 8 + > drivers/misc/Makefile | 1 + > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > 6 files changed, 1378 insertions(+), 5 deletions(-) > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > create mode 100644 drivers/misc/qcom-dcc.c > Gentle ping
On Tue, Jul 18, 2023 at 10:33:09AM +0530, Souradeep Chowdhury wrote: > On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > > Souradeep Chowdhury (3): > > dt-bindings: misc: qcom,dcc: Add the dtschema > > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > > support > > > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > > MAINTAINERS | 8 + > > drivers/misc/Kconfig | 8 + > > drivers/misc/Makefile | 1 + > > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > > 6 files changed, 1378 insertions(+), 5 deletions(-) > > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > > create mode 100644 drivers/misc/qcom-dcc.c > > > > Gentle ping $ mdfrm -c mail/todo/ 1480 messages in todo/ Please relax, and help out by reviewing other patches on the mailing lists in order to relieve the burden of maintainers and move your patches higher up the list. thanks, greg k-h
On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > DCC(Data Capture and Compare) is a DMA engine designed for debugging purposes. > In case of a system crash or manual software triggers by the user the DCC hardware > stores the value at the register addresses which can be used for debugging purposes. > The DCC driver provides the user with debugfs interface to configure the register > addresses. The options that the DCC hardware provides include reading from registers, > writing to registers, first reading and then writing to registers and looping > through the values of the same register. > > In certain cases a register write needs to be executed for accessing the rest of the > registers, also the user might want to record the changing values of a register with > time for which he has the option to use the loop feature. > > The options mentioned above are exposed to the user by debugfs files once the driver > is probed. The details and usage of this debugfs files are documented in > Documentation/ABI/testing/debugfs-driver-dcc. > > As an example let us consider a couple of debug scenarios where DCC has been proved to be > effective for debugging purposes:- > > i)TimeStamp Related Issue > > On SC7180, there was a coresight timestamp issue where it would occasionally be all 0 > instead of proper timestamp values. > > Proper timestamp: > Idx:3373; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x13004d8f5b7aa; CC=0x9e > > Zero timestamp: > Idx:3387; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x0; CC=0xa2 > > Now this is a non-fatal issue and doesn't need a system reset, but still needs > to be rootcaused and fixed for those who do care about coresight etm traces. > Since this is a timestamp issue, we would be looking for any timestamp related > clocks and such. > > We get all the clk register details from IP documentation and configure it > via DCC config_read debugfs node. Before that we set the current linked list. > > /* Program the linked list with the addresses */ > echo R 0x10c004 > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c008 > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c00c > /sys/kernel/debug/qcom-dcc/../3/config > echo R 0x10c010 > /sys/kernel/debug/qcom-dcc/../3/config > ..... and so on for other timestamp related clk registers > > /* Other way of specifying is in "addr len" pair, in below case it > specifies to capture 4 words starting 0x10C004 */ > > echo R 0x10C004 4 > /sys/kernel/debug/qcom-dcc/../3/config_read > > /* Enable DCC */ > echo 1 > /sys/kernel/debug/qcom-dcc/../3/enable > > /* Run the timestamp test for working case */ > > /* Send SW trigger */ > echo 1 > /sys/kernel/debug/qcom-dcc/../trigger > > /* Read SRAM */ > cat /dev/dcc_sram > dcc_sram1.bin > > /* Run the timestamp test for non-working case */ > > /* Send SW trigger */ > echo 1 > /sys/kernel/debug/qcom-dcc/../trigger > > /* Read SRAM */ > cat /dev/dcc_sram > dcc_sram2.bin > > Get the parser from [1] and checkout the latest branch. > > /* Parse the SRAM bin */ > python dcc_parser.py -s dcc_sram1.bin --v2 -o output/ > python dcc_parser.py -s dcc_sram2.bin --v2 -o output/ > > Sample parsed output of dcc_sram1.bin: > > <hwioDump version="1"> > <timestamp>03/14/21</timestamp> > <generator>Linux DCC Parser</generator> > <chip name="None" version="None"> > <register address="0x0010c004" value="0x80000000" /> > <register address="0x0010c008" value="0x00000008" /> > <register address="0x0010c00c" value="0x80004220" /> > <register address="0x0010c010" value="0x80000000" /> > </chip> > <next_ll_offset>next_ll_offset : 0x1c </next_ll_offset> > </hwioDump> > > ii)NOC register errors > > A particular class of registers called NOC which are functional registers was reporting > errors while logging the values.To trace these errors the DCC has been used effectively. > The steps followed were similar to the ones mentioned above. > In addition to NOC registers a few other dependent registers were configured in DCC to > monitor it's values during a crash. A look at the dependent register values revealed that > the crash was happening due to a secured access to one of these dependent registers. > All these debugging activity and finding the root cause was achieved using DCC. > > DCC parser is available at the following open source location > > https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser > > Changes in v25 > > * Updated the documentation of the structure dcc_config_entry as per the comments in V23 > * Updated the documentation of the dcc Kconfig definition as per comment in V24 > * Used u64 where applicable > * Removed the mutex locks where it is not needed > * Removed the use of unlikely keyword > * Renamed "nr_link_list" to "max_link_list" > > Souradeep Chowdhury (3): > dt-bindings: misc: qcom,dcc: Add the dtschema > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > support > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > MAINTAINERS | 8 + > drivers/misc/Kconfig | 8 + > drivers/misc/Makefile | 1 + > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > 6 files changed, 1378 insertions(+), 5 deletions(-) > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > create mode 100644 drivers/misc/qcom-dcc.c Gentle Ping
On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: > > > On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: ... >> >> https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser >> >> Changes in v25 >> >> * Updated the documentation of the structure dcc_config_entry as per >> the comments in V23 >> * Updated the documentation of the dcc Kconfig definition as per >> comment in V24 >> * Used u64 where applicable >> * Removed the mutex locks where it is not needed >> * Removed the use of unlikely keyword >> * Renamed "nr_link_list" to "max_link_list" >> >> Souradeep Chowdhury (3): >> dt-bindings: misc: qcom,dcc: Add the dtschema >> misc: dcc: Add driver support for Data Capture and Compare unit(DCC) >> MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver >> support >> >> Documentation/ABI/testing/debugfs-driver-dcc | 10 +- >> .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + >> MAINTAINERS | 8 + >> drivers/misc/Kconfig | 8 + >> drivers/misc/Makefile | 1 + >> drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ >> 6 files changed, 1378 insertions(+), 5 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml >> create mode 100644 drivers/misc/qcom-dcc.c > > Gentle Ping Thank you for the reminder Souradeep. Greg and others, please see if we need any changes here or it can be picked up?
On Thu, Aug 03, 2023 at 07:35:18AM -0700, Trilok Soni wrote: > On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: > > > > > > On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > > ... > > > > > > > https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser > > > > > > Changes in v25 > > > > > > * Updated the documentation of the structure dcc_config_entry as per > > > the comments in V23 > > > * Updated the documentation of the dcc Kconfig definition as per > > > comment in V24 > > > * Used u64 where applicable > > > * Removed the mutex locks where it is not needed > > > * Removed the use of unlikely keyword > > > * Renamed "nr_link_list" to "max_link_list" > > > > > > Souradeep Chowdhury (3): > > > dt-bindings: misc: qcom,dcc: Add the dtschema > > > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > > > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > > > support > > > > > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > > > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > > > MAINTAINERS | 8 + > > > drivers/misc/Kconfig | 8 + > > > drivers/misc/Makefile | 1 + > > > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > > > 6 files changed, 1378 insertions(+), 5 deletions(-) > > > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > > > create mode 100644 drivers/misc/qcom-dcc.c > > > > Gentle Ping > > Thank you for the reminder Souradeep. Greg and others, please see if we need > any changes here or it can be picked up? It would help if the code would actually build: drivers/misc/qcom-dcc.c: In function ‘ready_read’: drivers/misc/qcom-dcc.c:853:13: error: unused variable ‘ret’ [-Werror=unused-variable] 853 | int ret = 0; | ^~~ {sigh} How in the world was this ever tested? greg k-h
On Fri, Aug 04, 2023 at 03:47:26PM +0200, Greg Kroah-Hartman wrote: > On Thu, Aug 03, 2023 at 07:35:18AM -0700, Trilok Soni wrote: > > On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: > > > > > > > > > On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > > > > ... > > > > > > > > > > https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser > > > > > > > > Changes in v25 > > > > > > > > * Updated the documentation of the structure dcc_config_entry as per > > > > the comments in V23 > > > > * Updated the documentation of the dcc Kconfig definition as per > > > > comment in V24 > > > > * Used u64 where applicable > > > > * Removed the mutex locks where it is not needed > > > > * Removed the use of unlikely keyword > > > > * Renamed "nr_link_list" to "max_link_list" > > > > > > > > Souradeep Chowdhury (3): > > > > dt-bindings: misc: qcom,dcc: Add the dtschema > > > > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > > > > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > > > > support > > > > > > > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > > > > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > > > > MAINTAINERS | 8 + > > > > drivers/misc/Kconfig | 8 + > > > > drivers/misc/Makefile | 1 + > > > > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > > > > 6 files changed, 1378 insertions(+), 5 deletions(-) > > > > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > > > > create mode 100644 drivers/misc/qcom-dcc.c > > > > > > Gentle Ping > > > > Thank you for the reminder Souradeep. Greg and others, please see if we need > > any changes here or it can be picked up? > > It would help if the code would actually build: > > drivers/misc/qcom-dcc.c: In function ‘ready_read’: > drivers/misc/qcom-dcc.c:853:13: error: unused variable ‘ret’ [-Werror=unused-variable] > 853 | int ret = 0; > | ^~~ > > {sigh} > > How in the world was this ever tested? Ok, next time I want to see some QCOM engineers to sign off on this that it was actually tested and they can back it up that this is ready to be merged. When the code doesn't even build, that is a huge red flag that this whole thing is being rushed as it obviously was never tested in the form that was submitted for inclusion. You all know better than this. greg k-h
On 8/4/2023 7:19 PM, Greg Kroah-Hartman wrote: > On Fri, Aug 04, 2023 at 03:47:26PM +0200, Greg Kroah-Hartman wrote: >> On Thu, Aug 03, 2023 at 07:35:18AM -0700, Trilok Soni wrote: >>> On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: >>>> >>>> >>>> On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: >>> >>> ... >>> >>>>> >>>>> https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser >>>>> >>>>> Changes in v25 >>>>> >>>>> * Updated the documentation of the structure dcc_config_entry as per >>>>> the comments in V23 >>>>> * Updated the documentation of the dcc Kconfig definition as per >>>>> comment in V24 >>>>> * Used u64 where applicable >>>>> * Removed the mutex locks where it is not needed >>>>> * Removed the use of unlikely keyword >>>>> * Renamed "nr_link_list" to "max_link_list" >>>>> >>>>> Souradeep Chowdhury (3): >>>>> dt-bindings: misc: qcom,dcc: Add the dtschema >>>>> misc: dcc: Add driver support for Data Capture and Compare unit(DCC) >>>>> MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver >>>>> support >>>>> >>>>> Documentation/ABI/testing/debugfs-driver-dcc | 10 +- >>>>> .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + >>>>> MAINTAINERS | 8 + >>>>> drivers/misc/Kconfig | 8 + >>>>> drivers/misc/Makefile | 1 + >>>>> drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ >>>>> 6 files changed, 1378 insertions(+), 5 deletions(-) >>>>> create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml >>>>> create mode 100644 drivers/misc/qcom-dcc.c >>>> >>>> Gentle Ping >>> >>> Thank you for the reminder Souradeep. Greg and others, please see if we need >>> any changes here or it can be picked up? >> >> It would help if the code would actually build: >> >> drivers/misc/qcom-dcc.c: In function ‘ready_read’: >> drivers/misc/qcom-dcc.c:853:13: error: unused variable ‘ret’ [-Werror=unused-variable] >> 853 | int ret = 0; >> | ^~~ >> >> {sigh} >> >> How in the world was this ever tested? > > Ok, next time I want to see some QCOM engineers to sign off on this that > it was actually tested and they can back it up that this is ready to be > merged. When the code doesn't even build, that is a huge red flag that > this whole thing is being rushed as it obviously was never tested in the > form that was submitted for inclusion. > > You all know better than this. My apologies on missing out on this, it is a W=1 level compilation warning that got suppressed on a normal kernel build. I will be posting V26 by correcting this. Otherwise, this driver has no functional issues and is already ported in downstream kernels. > > greg k-h
On Mon, Aug 07, 2023 at 11:03:45PM +0530, Souradeep Chowdhury wrote: > > > On 8/4/2023 7:19 PM, Greg Kroah-Hartman wrote: > > On Fri, Aug 04, 2023 at 03:47:26PM +0200, Greg Kroah-Hartman wrote: > > > On Thu, Aug 03, 2023 at 07:35:18AM -0700, Trilok Soni wrote: > > > > On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: > > > > > > > > > > > > > > > On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: > > > > > > > > ... > > > > > > > > > > > > > > > > https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser > > > > > > > > > > > > Changes in v25 > > > > > > > > > > > > * Updated the documentation of the structure dcc_config_entry as per > > > > > > the comments in V23 > > > > > > * Updated the documentation of the dcc Kconfig definition as per > > > > > > comment in V24 > > > > > > * Used u64 where applicable > > > > > > * Removed the mutex locks where it is not needed > > > > > > * Removed the use of unlikely keyword > > > > > > * Renamed "nr_link_list" to "max_link_list" > > > > > > > > > > > > Souradeep Chowdhury (3): > > > > > > dt-bindings: misc: qcom,dcc: Add the dtschema > > > > > > misc: dcc: Add driver support for Data Capture and Compare unit(DCC) > > > > > > MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver > > > > > > support > > > > > > > > > > > > Documentation/ABI/testing/debugfs-driver-dcc | 10 +- > > > > > > .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + > > > > > > MAINTAINERS | 8 + > > > > > > drivers/misc/Kconfig | 8 + > > > > > > drivers/misc/Makefile | 1 + > > > > > > drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ > > > > > > 6 files changed, 1378 insertions(+), 5 deletions(-) > > > > > > create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml > > > > > > create mode 100644 drivers/misc/qcom-dcc.c > > > > > > > > > > Gentle Ping > > > > > > > > Thank you for the reminder Souradeep. Greg and others, please see if we need > > > > any changes here or it can be picked up? > > > > > > It would help if the code would actually build: > > > > > > drivers/misc/qcom-dcc.c: In function ‘ready_read’: > > > drivers/misc/qcom-dcc.c:853:13: error: unused variable ‘ret’ [-Werror=unused-variable] > > > 853 | int ret = 0; > > > | ^~~ > > > > > > {sigh} > > > > > > How in the world was this ever tested? > > > > Ok, next time I want to see some QCOM engineers to sign off on this that > > it was actually tested and they can back it up that this is ready to be > > merged. When the code doesn't even build, that is a huge red flag that > > this whole thing is being rushed as it obviously was never tested in the > > form that was submitted for inclusion. > > > > You all know better than this. > > My apologies on missing out on this, it is a W=1 level compilation warning > that got suppressed on a normal kernel build. No, not at all, it showed up on my "normal kernel build", I do not have "W=1" set at all. If you did a simple "make allmodconfig" I am pretty sure it would have tripped this. How exactly was this tested? thanks, greg k-h
On 8/7/2023 11:14 PM, Greg Kroah-Hartman wrote: > On Mon, Aug 07, 2023 at 11:03:45PM +0530, Souradeep Chowdhury wrote: >> >> >> On 8/4/2023 7:19 PM, Greg Kroah-Hartman wrote: >>> On Fri, Aug 04, 2023 at 03:47:26PM +0200, Greg Kroah-Hartman wrote: >>>> On Thu, Aug 03, 2023 at 07:35:18AM -0700, Trilok Soni wrote: >>>>> On 8/3/2023 12:06 AM, Souradeep Chowdhury wrote: >>>>>> >>>>>> >>>>>> On 6/28/2023 3:53 PM, Souradeep Chowdhury wrote: >>>>> >>>>> ... >>>>> >>>>>>> >>>>>>> https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser >>>>>>> >>>>>>> Changes in v25 >>>>>>> >>>>>>> * Updated the documentation of the structure dcc_config_entry as per >>>>>>> the comments in V23 >>>>>>> * Updated the documentation of the dcc Kconfig definition as per >>>>>>> comment in V24 >>>>>>> * Used u64 where applicable >>>>>>> * Removed the mutex locks where it is not needed >>>>>>> * Removed the use of unlikely keyword >>>>>>> * Renamed "nr_link_list" to "max_link_list" >>>>>>> >>>>>>> Souradeep Chowdhury (3): >>>>>>> dt-bindings: misc: qcom,dcc: Add the dtschema >>>>>>> misc: dcc: Add driver support for Data Capture and Compare unit(DCC) >>>>>>> MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver >>>>>>> support >>>>>>> >>>>>>> Documentation/ABI/testing/debugfs-driver-dcc | 10 +- >>>>>>> .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + >>>>>>> MAINTAINERS | 8 + >>>>>>> drivers/misc/Kconfig | 8 + >>>>>>> drivers/misc/Makefile | 1 + >>>>>>> drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ >>>>>>> 6 files changed, 1378 insertions(+), 5 deletions(-) >>>>>>> create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml >>>>>>> create mode 100644 drivers/misc/qcom-dcc.c >>>>>> >>>>>> Gentle Ping >>>>> >>>>> Thank you for the reminder Souradeep. Greg and others, please see if we need >>>>> any changes here or it can be picked up? >>>> >>>> It would help if the code would actually build: >>>> >>>> drivers/misc/qcom-dcc.c: In function ‘ready_read’: >>>> drivers/misc/qcom-dcc.c:853:13: error: unused variable ‘ret’ [-Werror=unused-variable] >>>> 853 | int ret = 0; >>>> | ^~~ >>>> >>>> {sigh} >>>> >>>> How in the world was this ever tested? >>> >>> Ok, next time I want to see some QCOM engineers to sign off on this that >>> it was actually tested and they can back it up that this is ready to be >>> merged. When the code doesn't even build, that is a huge red flag that >>> this whole thing is being rushed as it obviously was never tested in the >>> form that was submitted for inclusion. >>> >>> You all know better than this. >> >> My apologies on missing out on this, it is a W=1 level compilation warning >> that got suppressed on a normal kernel build. > > No, not at all, it showed up on my "normal kernel build", I do not have > "W=1" set at all. > > If you did a simple "make allmodconfig" I am pretty sure it would have > tripped this. > > How exactly was this tested? My toolchain interprets this as a W=1 level warning rather than an error. So I am able to build the kernel with it. Probably because I am using an older version. Will correct this in the next version. > > thanks, > > greg k-h
DCC(Data Capture and Compare) is a DMA engine designed for debugging purposes. In case of a system crash or manual software triggers by the user the DCC hardware stores the value at the register addresses which can be used for debugging purposes. The DCC driver provides the user with debugfs interface to configure the register addresses. The options that the DCC hardware provides include reading from registers, writing to registers, first reading and then writing to registers and looping through the values of the same register. In certain cases a register write needs to be executed for accessing the rest of the registers, also the user might want to record the changing values of a register with time for which he has the option to use the loop feature. The options mentioned above are exposed to the user by debugfs files once the driver is probed. The details and usage of this debugfs files are documented in Documentation/ABI/testing/debugfs-driver-dcc. As an example let us consider a couple of debug scenarios where DCC has been proved to be effective for debugging purposes:- i)TimeStamp Related Issue On SC7180, there was a coresight timestamp issue where it would occasionally be all 0 instead of proper timestamp values. Proper timestamp: Idx:3373; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x13004d8f5b7aa; CC=0x9e Zero timestamp: Idx:3387; ID:10; I_TIMESTAMP : Timestamp.; Updated val = 0x0; CC=0xa2 Now this is a non-fatal issue and doesn't need a system reset, but still needs to be rootcaused and fixed for those who do care about coresight etm traces. Since this is a timestamp issue, we would be looking for any timestamp related clocks and such. We get all the clk register details from IP documentation and configure it via DCC config_read debugfs node. Before that we set the current linked list. /* Program the linked list with the addresses */ echo R 0x10c004 > /sys/kernel/debug/qcom-dcc/../3/config echo R 0x10c008 > /sys/kernel/debug/qcom-dcc/../3/config echo R 0x10c00c > /sys/kernel/debug/qcom-dcc/../3/config echo R 0x10c010 > /sys/kernel/debug/qcom-dcc/../3/config ..... and so on for other timestamp related clk registers /* Other way of specifying is in "addr len" pair, in below case it specifies to capture 4 words starting 0x10C004 */ echo R 0x10C004 4 > /sys/kernel/debug/qcom-dcc/../3/config_read /* Enable DCC */ echo 1 > /sys/kernel/debug/qcom-dcc/../3/enable /* Run the timestamp test for working case */ /* Send SW trigger */ echo 1 > /sys/kernel/debug/qcom-dcc/../trigger /* Read SRAM */ cat /dev/dcc_sram > dcc_sram1.bin /* Run the timestamp test for non-working case */ /* Send SW trigger */ echo 1 > /sys/kernel/debug/qcom-dcc/../trigger /* Read SRAM */ cat /dev/dcc_sram > dcc_sram2.bin Get the parser from [1] and checkout the latest branch. /* Parse the SRAM bin */ python dcc_parser.py -s dcc_sram1.bin --v2 -o output/ python dcc_parser.py -s dcc_sram2.bin --v2 -o output/ Sample parsed output of dcc_sram1.bin: <hwioDump version="1"> <timestamp>03/14/21</timestamp> <generator>Linux DCC Parser</generator> <chip name="None" version="None"> <register address="0x0010c004" value="0x80000000" /> <register address="0x0010c008" value="0x00000008" /> <register address="0x0010c00c" value="0x80004220" /> <register address="0x0010c010" value="0x80000000" /> </chip> <next_ll_offset>next_ll_offset : 0x1c </next_ll_offset> </hwioDump> ii)NOC register errors A particular class of registers called NOC which are functional registers was reporting errors while logging the values.To trace these errors the DCC has been used effectively. The steps followed were similar to the ones mentioned above. In addition to NOC registers a few other dependent registers were configured in DCC to monitor it's values during a crash. A look at the dependent register values revealed that the crash was happening due to a secured access to one of these dependent registers. All these debugging activity and finding the root cause was achieved using DCC. DCC parser is available at the following open source location https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/tools/-/tree/opensource-tools.lnx.1.0.r176-rel/dcc_parser Changes in v25 * Updated the documentation of the structure dcc_config_entry as per the comments in V23 * Updated the documentation of the dcc Kconfig definition as per comment in V24 * Used u64 where applicable * Removed the mutex locks where it is not needed * Removed the use of unlikely keyword * Renamed "nr_link_list" to "max_link_list" Souradeep Chowdhury (3): dt-bindings: misc: qcom,dcc: Add the dtschema misc: dcc: Add driver support for Data Capture and Compare unit(DCC) MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver support Documentation/ABI/testing/debugfs-driver-dcc | 10 +- .../devicetree/bindings/misc/qcom,dcc.yaml | 44 + MAINTAINERS | 8 + drivers/misc/Kconfig | 8 + drivers/misc/Makefile | 1 + drivers/misc/qcom-dcc.c | 1312 +++++++++++++++++ 6 files changed, 1378 insertions(+), 5 deletions(-) create mode 100644 Documentation/devicetree/bindings/misc/qcom,dcc.yaml create mode 100644 drivers/misc/qcom-dcc.c