openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ChiaWei Wang <chiawei_wang@aspeedtech.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"andrew@aj.id.au" <andrew@aj.id.au>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"yulei.sh@bytedance.com" <yulei.sh@bytedance.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"osk@google.com" <osk@google.com>
Subject: RE: [PATCH v5 2/4] dt-bindings: aspeed: Add UART routing controller
Date: Fri, 17 Sep 2021 00:46:02 +0000	[thread overview]
Message-ID: <HK0PR06MB377954A91F788E4B091CAA1891DD9@HK0PR06MB3779.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <YUOmq4hLoP2ds18w@robh.at.kernel.org>

Hi Rob,

> From: Rob Herring <robh@kernel.org>
> Sent: Friday, September 17, 2021 4:19 AM
> 
> On Thu, Sep 16, 2021 at 05:25:13PM +0800, Chia-Wei Wang wrote:
> > Add dt-bindings for Aspeed UART routing controller.
> >
> > Signed-off-by: Oskar Senft <osk@google.com>
> > Signed-off-by: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
> > ---
> >  .../devicetree/bindings/mfd/aspeed-lpc.yaml   |  4 ++
> >  .../bindings/soc/aspeed/uart-routing.yaml     | 70
> +++++++++++++++++++
> >  2 files changed, 74 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
> > b/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
> > index 54f080df5e2f..697331d840a0 100644
> > --- a/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
> > @@ -142,6 +142,10 @@ patternProperties:
> >        - interrupts
> >        - snoop-ports
> >
> > +  "^uart-routing@[0-9a-f]+$":
> > +    $ref: /schemas/soc/aspeed/uart-routing.yaml#
> > +    description: The UART routing control under LPC register space
> > +
> >  required:
> >    - compatible
> >    - reg
> > diff --git
> > a/Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml
> > b/Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml
> > new file mode 100644
> > index 000000000000..534b2a9340ce
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml
> > @@ -0,0 +1,70 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) # #
> > +Copyright (c) 2018 Google LLC # # Copyright (c) 2021 Aspeed
> > +Technology Inc.
> > +%YAML 1.2
> > +---
> > +$id: "http://devicetree.org/schemas/soc/aspeed/uart-routing.yaml#"
> > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > +
> > +title: Aspeed UART Routing Controller
> > +
> > +maintainers:
> > +  - Oskar Senft <osk@google.com>
> > +  - Chia-Wei Wang <chiawei_wang@aspeedtech.com>
> > +
> > +description:
> > +  The Aspeed UART routing control allow to dynamically route the
> > +inputs for
> > +  the built-in UARTS and physical serial I/O ports.
> > +
> > +  This allows, for example, to connect the output of UART to another UART.
> > +  This can be used to enable Host <-> BMC communication via UARTs,
> > + e.g. to  allow access to the Host's serial console.
> > +
> > +  This driver is for the BMC side. The sysfs files allow the BMC
> > + userspace  which owns the system configuration policy, to configure
> > + how UARTs and  physical serial I/O ports are routed.
> > +
> > +  Two types of files, uart* and io*, are presented in sysfs. The
> > + uart*  configures the input signal of a UART controller whereas io*
> > + configures  that of a physical serial port.
> > +
> > +  When read, each file shows the list of available options with
> > + currently  selected option marked by brackets "[]". The list of
> > + available options  depends on the selected file.
> > +
> > +  e.g.
> > +  cat
> > + /sys/bus/platform/drivers/aspeed-uart-routing/*.uart_routing/uart1
> > +  [io1] io2 io3 io4 uart2 uart3 uart4 io6
> > +
> > +  In this case, UART1 gets its input from IO1 (physical serial port 1).
> 
> This is about documenting the hardware, not an OS driver.
> 
> sysfs files have their own documentation.
> 

Understood. I will remove this sysfs description from bindings in the next revision.
Thanks.

Chiawei


  reply	other threads:[~2021-09-17  0:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  9:25 [PATCH v5 0/4] arm: aspeed: Add UART routing support Chia-Wei Wang
2021-09-16  9:25 ` [PATCH v5 1/4] dt-bindings: mfd: aspeed-lpc: Convert to YAML schema Chia-Wei Wang
2021-09-16 12:21   ` Rob Herring
2021-09-16 14:31   ` Rob Herring
2021-09-22  5:54     ` ChiaWei Wang
2021-09-16  9:25 ` [PATCH v5 2/4] dt-bindings: aspeed: Add UART routing controller Chia-Wei Wang
2021-09-16 20:18   ` Rob Herring
2021-09-17  0:46     ` ChiaWei Wang [this message]
2021-09-16  9:25 ` [PATCH v5 3/4] soc: aspeed: Add UART routing support Chia-Wei Wang
2021-09-16  9:25 ` [PATCH v5 4/4] ARM: dts: aspeed: Add uart routing to device tree Chia-Wei Wang

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=HK0PR06MB377954A91F788E4B091CAA1891DD9@HK0PR06MB3779.apcprd06.prod.outlook.com \
    --to=chiawei_wang@aspeedtech.com \
    --cc=andrew@aj.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=osk@google.com \
    --cc=robh@kernel.org \
    --cc=yulei.sh@bytedance.com \
    --subject='RE: [PATCH v5 2/4] dt-bindings: aspeed: Add UART routing controller' \
    /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: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).