Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp2373405pxm; Fri, 25 Feb 2022 00:13:01 -0800 (PST) X-Google-Smtp-Source: ABdhPJxINAVlJZhwGB6LLshPwiBz6GSq2FBB4iz0H0PlFd0sy1RFAZv8RzLASdPGqpG35kL9ONf7 X-Received: by 2002:a05:6a00:1a42:b0:4d1:e81a:64cb with SMTP id h2-20020a056a001a4200b004d1e81a64cbmr6699515pfv.78.1645776781603; Fri, 25 Feb 2022 00:13:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645776781; cv=none; d=google.com; s=arc-20160816; b=pUAN8Oft5yHlB9XWBwEkRn6ZS0NTV6IYFDtmECQRabBAUgKWRiFX6IJAb24f9s6gms 0GHCSGU7Pkmg1zrvSZEZlyiav9f3F3YUhYcWTeTGFLwz2vOUXLQiuPKxHeMIjOYEPWFc kX5FwM0YArQnrFng+pbdpt31bIo3PJdskw+rJARBaAvtbZMyDRyktc4Exn09d4mgfwNC +M38vQrdWrdfxzQbQa8JiMLCSGi7ddHfKgzmJHvIKuJxBzJl3RDRAm3LcIfHSuT8QDWS 0wqg+zdmPbHm5CVam7L4ZuM9XKiq29+bdde9V4NelwrBVtANKh7WjSEgDvYaezaFe7jc RpwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=ZkFXYKTTljtfsfw2EjU16imTOhMh7P/2dVZTAX9pANk=; b=yRpTElJCqWU3vNJ7W24HaGZkXoqJ8vfPJGeNtK22x2AK3DyQOtwXQp3C7wr8sVdTFZ q7byERMDJD/j8M9xzIq3zkBk3aQ4YaKLYVaMXgLMZ7TkPRjrHVFQ8sSYmIbOg9FYcHg8 VSyICM3D3W8NHy50nZHz+hyidZtPpZXqZ2+lMuQuJeyEFBa7baCu3+okZLf6UYOOTCR4 5fFiNJrcjxeMXmAdvOxF0Upu0HMgWpO8I9uGXQ7zJj0/h4pqYtwzK3EdSbUxN4K27G/W aIie7TOySrVBK0F9jY+MlPpgjkiVoJjSuJVmVD2bWGd7qGAVPdlu4jt8tQdG5qpSl/7v cfug== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s1-20020a170902ea0100b0014ee4775042si1336604plg.207.2022.02.25.00.12.33; Fri, 25 Feb 2022 00:13:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238171AbiBYHk3 (ORCPT + 99 others); Fri, 25 Feb 2022 02:40:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232659AbiBYHk3 (ORCPT ); Fri, 25 Feb 2022 02:40:29 -0500 Received: from mail-sh.amlogic.com (mail-sh.amlogic.com [58.32.228.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 55872177764; Thu, 24 Feb 2022 23:39:57 -0800 (PST) Received: from droid06.amlogic.com (10.18.11.248) by mail-sh.amlogic.com (10.18.11.5) with Microsoft SMTP Server id 15.1.2176.14; Fri, 25 Feb 2022 15:39:55 +0800 From: Yu Tu To: , , , CC: Greg Kroah-Hartman , Jiri Slaby , Neil Armstrong , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , Yu Tu Subject: [PATCH V7 0/6] Use CCF to describe the UART baud rate clock Date: Fri, 25 Feb 2022 15:39:16 +0800 Message-ID: <20220225073922.3947-1-yu.tu@amlogic.com> X-Mailer: git-send-email 2.33.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.18.11.248] X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Using the common Clock code to describe the UART baud rate clock makes it easier for the UART driver to be compatible with the baud rate requirements of the UART IP on different meson chips. Add Meson S4 SoC compatible. The test method: Start the console and run the following commands in turn: stty -F /dev/ttyAML0 115200 and stty -F /dev/ttyAML0 921600. Since most SoCs are too old, I was able to find all the platforms myself such as Meson6, Meson8, Meson8b, GXL and so on. I only tested it with G12A and S4. Yu Tu (6): tty: serial: meson: Move request the register region to probe tty: serial: meson: Use devm_ioremap_resource to get register mapped memory tty: serial: meson: Describes the calculation of the UART baud rate clock using a clock frame tty: serial: meson: Make some bit of the REG5 register writable tty: serial: meson: The system stuck when you run the stty command on the console to change the baud rate tty: serial: meson: Added S4 SOC compatibility V6 -> V7: To solve the system stuck when you run the stty command on the console to change the baud rate. V5 -> V6: Change error format as discussed in the email. V4 -> V5: Change error format. V3 -> V4: Change CCF to describe the UART baud rate clock as discussed in the email. V2 -> V3: add compatible = "amlogic,meson-gx-uart". Because it must change the DTS before it can be deleted V1 -> V2: Use CCF to describe the UART baud rate clock.Make some changes as discussed in the email Link:https://lore.kernel.org/linux-amlogic/20220118030911.12815-4-yu.tu@amlogic.com/ drivers/tty/serial/meson_uart.c | 221 ++++++++++++++++++++++---------- 1 file changed, 154 insertions(+), 67 deletions(-) base-commit: a603ca60cebff8589882427a67f870ed946b3fc8 -- 2.33.1