linux-kernel - RE: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M Mini

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DB7PR04MB5178EA739587B2DB084570B9872F0@DB7PR04MB5178.eurprd04.prod.outlook.com>
Date:   Sun, 22 Dec 2019 08:33:40 +0000
From:   Jacky Bai <ping.bai@....com>
To:     Adam Ford <aford173@...il.com>,
        arm-soc <linux-arm-kernel@...ts.infradead.org>
CC:     Peng Fan <peng.fan@....com>, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        dl-linux-imx <linux-imx@....com>,
        devicetree <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Leonard Crestez <leonard.crestez@....com>
Subject: RE: [PATCH V2 0/7] soc: imx: Enable additional functionality of
 i.MX8M Mini

> -----Original Message-----
> From: Adam Ford <aford173@...il.com>
> Sent: Saturday, December 21, 2019 11:07 PM
> To: arm-soc <linux-arm-kernel@...ts.infradead.org>
> Cc: Peng Fan <peng.fan@....com>; Jacky Bai <ping.bai@....com>; Rob
> Herring <robh+dt@...nel.org>; Mark Rutland <mark.rutland@....com>;
> Shawn Guo <shawnguo@...nel.org>; Sascha Hauer
> <s.hauer@...gutronix.de>; Pengutronix Kernel Team
> <kernel@...gutronix.de>; Fabio Estevam <festevam@...il.com>;
> dl-linux-imx <linux-imx@....com>; devicetree <devicetree@...r.kernel.org>;
> Linux Kernel Mailing List <linux-kernel@...r.kernel.org>; Leonard Crestez
> <leonard.crestez@....com>
> Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of
> i.MX8M Mini
> 
> On Fri, Dec 13, 2019 at 10:05 AM Adam Ford <aford173@...il.com> wrote:
> >
> > The GPCv2 controller on the i.MX8M Mini is compatible with the driver
> > used for the i.MX8MQ except for the register locations and names.
> > The GPCv2 controller is used to enable additional periperals currently
> > unavailable on the i.MX8M Mini.  In order to make them function, the
> > GPCv2 needs to be adapted so the drivers can associate their power
> > domain to the GPCv2 to enable them.
> >
> > This series makes one include file slightly more generic, adds the
> > iMX8M Mini entries, updates the bindings, adds them to the device
> > tree, then associates the new power domain to both the OTG and PCIe
> > controllers.
> >
> > Some peripherals may need additional power domain drivers in the
> > future due to limitations of the GPC driver, but the drivers for VPU
> > and others are not available yet.
> 
> Before I do a V3 to address Rob's comments, I am thinking I'll drop the items
> on the GPC that Jacky suggested would not work, and we don't have drivers
> for those other peripherals (GPU, VPU, etc.) anyway.  My main goal here was
> to try and get the USB OTG ports working, so I'd like to enabled enough of the
> items on the GPC that are similar to the i.MX8MQ and leave the more
> challenging items until we have either a better driver available and/or actual
> peripheral support coming.  I haven't seen LCDIF or DSI drivers pushed
> upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
> 
> Does anyone from the NXP team have any other comments/concerns?
> 

If you look into NXP's release code, you will find that it is not easy to handle the
power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use
SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version
power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think
we need to use SCMI to implement it. as there is no SCMI over SMC available, upstream is
on the way, so the power domain for i.MX8MM/MN is pending.

Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in
the future, It seems the SMCC function ID still need to choose from SIP service function id bank.

Another concern for adding power domain support in GPCv2 is that, each time a new
SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way
to keep driver reuse. The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ,
as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the
case.

There is another concern, we don't want to export GPC module to rich OS side, it is not a must.

BR
Jacky Bai

> adam
> >

> > Adam Ford (7):
> >   soc: imx: gpcv2: Rename imx8mq-power.h to imx8m-power.h
> >   soc: imx: gpcv2: Update imx8m-power.h to include iMX8M Mini
> >   soc: imx: gpcv2: add support for i.MX8M Mini SoC
> >   dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
> >   arm64: dts: imx8mm: add GPC power domains
> >   ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
> >   arm64: dts: imx8mm: Add PCIe support
> >
> >  .../bindings/power/fsl,imx-gpcv2.txt          |   6 +-
> >  arch/arm64/boot/dts/freescale/imx8mm.dtsi     | 127 ++++++++-
> >  arch/arm64/boot/dts/freescale/imx8mq.dtsi     |   2 +-
> >  drivers/soc/imx/gpcv2.c                       | 246
> +++++++++++++++++-
> >  .../power/{imx8mq-power.h => imx8m-power.h}   |  14 +
> >  5 files changed, 387 insertions(+), 8 deletions(-)  rename
> > include/dt-bindings/power/{imx8mq-power.h => imx8m-power.h} (57%)
> >
> > --
> > 2.20.1
> >