Re: [PATCH v1 5/5] tty: serial: 8250: add DFL bus driver for Altera 16550.

Xu Yilun
2022-09-13T02:58:16Z

On 2022-09-12 at 08:29:47 -0700, matthew.gerlach@linux.intel.com wrote:
>
>
> On Sun, 11 Sep 2022, Xu Yilun wrote:
>
> > On 2022-09-06 at 12:04:26 -0700, matthew.gerlach@linux.intel.com wrote:
> > > From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> > >
> > > Add a Device Feature List (DFL) bus driver for the Altera
> > > 16550 implementation of UART.
> > >
> > > Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> > > ---
> > > drivers/tty/serial/8250/8250_dfl.c | 188 +++++++++++++++++++++++++++++
> > > drivers/tty/serial/8250/Kconfig | 9 ++
> > > drivers/tty/serial/8250/Makefile | 1 +
> > > include/linux/dfl.h | 7 ++
> > > 4 files changed, 205 insertions(+)
> > > create mode 100644 drivers/tty/serial/8250/8250_dfl.c
> > >
> > > diff --git a/drivers/tty/serial/8250/8250_dfl.c b/drivers/tty/serial/8250/8250_dfl.c
> > > new file mode 100644
> > > index 000000000000..dcf6638a298c
> > > --- /dev/null
> > > +++ b/drivers/tty/serial/8250/8250_dfl.c
> > > @@ -0,0 +1,188 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > +/*
> > > + * Driver for FPGA UART
> > > + *
> > > + * Copyright (C) 2022 Intel Corporation, Inc.
> > > + *
> > > + * Authors:
> > > + * Ananda Ravuri <ananda.ravuri@intel.com>
> > > + * Matthew Gerlach <matthew.gerlach@linux.intel.com>
> > > + */
> > > +
> > > +#include <linux/dfl.h>
> > > +#include <linux/version.h>
> > > +#include <linux/serial.h>
> > > +#include <linux/serial_8250.h>
> > > +#include <linux/kernel.h>
> > > +#include <linux/module.h>
> > > +#include <linux/bitfield.h>
> > > +#include <linux/io-64-nonatomic-lo-hi.h>
> > > +
> > > +struct dfl_uart {
> > > + void __iomem *csr_base;
> > > + u64 csr_addr;
> > > + unsigned int csr_size;
> > > + struct device *dev;
> > > + u64 uart_clk;
> > > + u64 fifo_len;
> > > + unsigned int fifo_size;
> > > + unsigned int reg_shift;
> > > + unsigned int line;
> > > +};
> > > +
> > > +int feature_uart_walk(struct dfl_uart *dfluart, resource_size_t max)
> > > +{
> > > + void __iomem *param_base;
> > > + int off;
> > > + u64 v;
> > > +
> > > + v = readq(dfluart->csr_base + DFHv1_CSR_ADDR);
> > > + dfluart->csr_addr = FIELD_GET(DFHv1_CSR_ADDR_MASK, v);
> > > +
> > > + v = readq(dfluart->csr_base + DFHv1_CSR_SIZE_GRP);
> > > + dfluart->csr_size = FIELD_GET(DFHv1_CSR_SIZE_GRP_SIZE, v);
> >
> > These are generic for DFHv1, so maybe we parse them in DFL generic code.
>
> I will look into moving this to the DFL generic code.
>
> >
> > > +
> > > + if (dfluart->csr_addr == 0 || dfluart->csr_size == 0) {
> > > + dev_err(dfluart->dev, "FIXME bad dfh address and size\n");
> > > + return -EINVAL;
> > > + }
> > > +
> > > + if (!FIELD_GET(DFHv1_CSR_SIZE_GRP_HAS_PARAMS, v)) {
> > > + dev_err(dfluart->dev, "missing required parameters\n");
> > > + return -EINVAL;
> > > + }
> > > +
> > > + param_base = dfluart->csr_base + DFHv1_PARAM_HDR;
> >
> > The same concern.
> >
> > > +
> > > + off = dfl_find_param(param_base, max, DFHv1_PARAM_ID_CLK_FRQ);
> > > + if (off < 0) {
> > > + dev_err(dfluart->dev, "missing CLK_FRQ param\n");
> > > + return -EINVAL;
> > > + }
> > > +
> > > + dfluart->uart_clk = readq(param_base + off + DFHv1_PARAM_DATA);
> > > + dev_dbg(dfluart->dev, "UART_CLK_ID %llu Hz\n", dfluart->uart_clk);
> >
> > I see the DFHv1_PARAM_ID_CLK_FRQ defined in generic dfl.h, is this
> > param definition global to all features, or specific to uart?
>
> Certainly uart drivers need to know the input clock frequency in order to
> properly calculate baud rate dividers, but drivers for other features/IP
> blocks may need to know the input clock frequency as well. On the other
> hand not all drivers need to know the input clock frequency to the
> feature/IP block.
>
> >
> > Do we have clear definition of generic parameters vs feature specific
> > parameters?
>
> I don't think there is a clear definition of generic versus feature
> specific, but a clock frequency and interrupt information it fairly generic.
>
> >
> > The concern here is to avoid duplicated parameter parsing for each driver.
>
> I understand the concern about avoiding duplicated parameter parsing.

Yeah. Another concern is, reviewers from other domains have to look into
every detail of the DFH param layout to know what happened, which I
think is not that friendly.

Thanks,
Yilun