From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 57A9AC433FE for ; Sun, 16 Oct 2022 12:05:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229461AbiJPMFq (ORCPT ); Sun, 16 Oct 2022 08:05:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52358 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229633AbiJPMFq (ORCPT ); Sun, 16 Oct 2022 08:05:46 -0400 Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8BE252F39E for ; Sun, 16 Oct 2022 05:05:44 -0700 (PDT) Received: by mail-qk1-x72c.google.com with SMTP id j21so5192418qkk.9 for ; Sun, 16 Oct 2022 05:05:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=UmI04icaYYevz8erTj5VumVzXOApiqD62eBBl7puraY=; b=qtT0dLgoP8gq5FOWhmRjCFCwDD61Tr+gqDYRdhXsTrxyF5nLMFs7IKgjiOMKH5F4l5 I5CC/lowN/7J/INdR5JiQGFq9Ao8Q/l3LjpSMAyuFBa+MXQuHNgzwfs7YNblXrBwsWXM 3VG0q3bZTJrP1RIeTbobQQcBZ9/onb+dz8y0rKuALIc16BZ0o4pdtn4+JzogIOz8tHXo jgUM/AY1SpsEQ1uQmmTooVqm1cQ6HmsxLwgb/Mt4QhbyUSLDj/Pr8lqY/5tp+8IC0CBa PAKCRY8ozzixXu02pJ5azNoQw5CPV5aXjU9mYIw8pbduoe+Xwrk9Lw8xTf6xH3wXNiFX Fd2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UmI04icaYYevz8erTj5VumVzXOApiqD62eBBl7puraY=; b=6ntURLSInyoCng+H+GkH1RV0jzmAFhkx9E+7VAPHhmcvnKgNbbnuTK9Qw+MYiOh2Z5 FGlH07kL8Dqa2vhxnJP6bJtGza2eX20ZPQGcBbGYsfJX4R4EbGufrnXgD7z5tCRQ2F7R vYJrGqBhHQzAw49RHSPwMK/9nhZ5V0tfyw8akzbYCf7JQ3oZC22hexyQH2z4SPTNLN1W JQqVoxQ31hkiYwaN5ygkX8HO9TTtLKU03j/f+DaW4/jrpwtT0vxpW0pcink7kOjxkGqH X50QozSKIiUjgpvXY/vVzuNo162omJTH1CpOmWPVxTnN1IsnBR9v+K1NYUaDwpo8UJ4h lICA== X-Gm-Message-State: ACrzQf1f/kbVR6g3YmhO1+sMXdBfgtUx4olFaHqV73USGq80+3+WVfDT 58cMoOHhKmiM+Fg8ueFhyid5fg== X-Google-Smtp-Source: AMsMyM7L06TcpOGp8BEqPcSmNwY3HduQhD2Ygu7LrmAfwqVeAp05tdZ+NzI25BMTnWyukqtxML2mhw== X-Received: by 2002:a37:4553:0:b0:6cf:4dbd:b5f6 with SMTP id s80-20020a374553000000b006cf4dbdb5f6mr4382912qka.339.1665921943627; Sun, 16 Oct 2022 05:05:43 -0700 (PDT) Received: from fedora (69-109-179-158.lightspeed.dybhfl.sbcglobal.net. [69.109.179.158]) by smtp.gmail.com with ESMTPSA id q4-20020a05620a2a4400b006ec09d7d357sm7187342qkp.47.2022.10.16.05.05.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 16 Oct 2022 05:05:42 -0700 (PDT) Date: Sun, 16 Oct 2022 08:05:40 -0400 From: William Breathitt Gray To: jic23@kernel.org, lars@metafoo.de, benjamin.gaignard@st.com, mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com Cc: fabrice.gasnier@foss.st.com, linux-iio@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Removing the last of IIO_COUNT (stm32-timer-trigger) Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HRMrcOk/7EdR9IuO" Content-Disposition: inline Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org --HRMrcOk/7EdR9IuO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, The drivers/iio/trigger/stm32-timer-trigger.c file remains the last consumer if the IIO_COUNT type. The IIO_COUNT type was deprecated some time ago with the introduction of the Counter subsystem. Most of the previous IIO_COUNT consumers were migrated successfully to the Counter subsystem, but the stm32-timer-trigger driver remains as the sole module preventing the final removal of IIO_COUNT. At the time we deprecated IIO_COUNT, the Counter subsystem was nascent and lacked some of the functionality we have nowadays such as a character device interface, timestamping, hardware buffer support, etc. If I recall correctly, the decision to delay the migration of stm32-timer-trigger to the Counter subsystem was a lack of some functionality the Counter subsystem could not provide at the time. I hoping someone can evaluate stm32-timer-trigger to see if we are able transition now to the Counter subsystem, or if that necessary functionality is still missing today. Even if it turns out that we are unable to migrate, it'll be useful to know what's left to implement in the Counter subsystem to support stm32-timer-trigger or similar devices in the future. Thanks, William Breathitt Gray --HRMrcOk/7EdR9IuO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQSNN83d4NIlKPjon7a1SFbKvhIjKwUCY0vzlAAKCRC1SFbKvhIj KzBaAP0TAsZHUhqetvOPlAMcDxL+BLNrmOVVk2noaEurAxJBBAEAg3wWG3/TM4jB pZMQoTnLR84Z69Y4AoEgwfVbXnhPNwA= =j1dt -----END PGP SIGNATURE----- --HRMrcOk/7EdR9IuO--