From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 0/5] soc: imx: add scu firmware api support
Date: Tue, 28 Aug 2018 08:15:09 +0200 [thread overview]
Message-ID: <20180828061509.ujjjigfjanprro5i@pengutronix.de> (raw)
In-Reply-To: <AM0PR04MB4211E5D66FD8502278765EC8800B0@AM0PR04MB4211.eurprd04.prod.outlook.com>
On Mon, Aug 27, 2018 at 09:59:36AM +0000, A.s. Dong wrote:
> > -----Original Message-----
> > From: Sascha Hauer [mailto:s.hauer at pengutronix.de]
> > Sent: Monday, August 27, 2018 4:33 PM
> > To: A.s. Dong <aisheng.dong@nxp.com>
> > Cc: Jassi Brar <jassisinghbrar@gmail.com>; dongas86 at gmail.com;
> > kernel at pengutronix.de; shawnguo at kernel.org; Fabio Estevam
> > <fabio.estevam@nxp.com>; dl-linux-imx <linux-imx@nxp.com>;
> > linux-arm-kernel at lists.infradead.org
> > Subject: Re: [PATCH V5 0/5] soc: imx: add scu firmware api support
> >
> > On Fri, Aug 24, 2018 at 07:36:38AM +0000, A.s. Dong wrote:
> > > Hi Jassi & Sasha,
> > >
> > > Do you have some suggestions about this patch series?
> >
> > I still think that the users like clk and pinctrl should directly call sc_call_rpc(),
> > no need for this shim at all.
> >
>
> Sorry, I'm a bit confuse.
> What specific shim do you mean not needed?
>
> Do you mean we don't need all the SCU SVC APIs (clk/pm/pinctrl/misc and etc)
> Implemented in this patch series and instead directly implement them in client
> driver?
> For example:
> drivers/soc/imx/sc/svc/pm/rpc_clnt.c
> sc_err_t sc_pm_get_clock_rate(sc_ipc_t ipc, sc_rsrc_t resource,
> sc_pm_clk_t clk, sc_pm_clock_rate_t *rate)
> Change to:
> drivers/clk/imx/scu/scu_clock.c ?
> sc_err_t sc_pm_get_clock_rate(sc_ipc_t ipc, sc_rsrc_t resource,
> sc_pm_clk_t clk, sc_pm_clock_rate_t *rate)
That particular function would go into drivers/clk/imx/scu/clk-divider-scu.c
and probably would be no separate function at all but go into
clk_divider_scu_recalc_rate(), but yes, that's the idea.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2018-08-28 6:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 16:08 [PATCH V5 0/5] soc: imx: add scu firmware api support Dong Aisheng
2018-08-20 16:08 ` [PATCH V5 1/5] dt-bindings: arm: fsl: add scu binding doc Dong Aisheng
2018-08-20 18:11 ` Rob Herring
2018-08-21 3:00 ` A.s. Dong
2018-08-21 11:51 ` A.s. Dong
2018-08-24 9:36 ` Jassi Brar
2018-08-24 9:51 ` A.s. Dong
2018-08-20 16:08 ` [PATCH V5 2/5] soc: imx: add SC firmware IPC and APIs Dong Aisheng
2018-09-10 8:40 ` Sascha Hauer
2018-09-10 9:44 ` A.s. Dong
2018-09-10 12:11 ` Sascha Hauer
2018-09-11 10:38 ` A.s. Dong
2018-09-16 13:23 ` A.s. Dong
2018-09-18 6:22 ` Sascha Hauer
2018-09-18 7:54 ` A.s. Dong
2018-08-20 16:08 ` [PATCH V5 3/5] soc: imx: sc: add pm svc support Dong Aisheng
2018-08-20 16:08 ` [PATCH V5 4/5] soc: imx: sc: add pad " Dong Aisheng
2018-08-20 16:08 ` [PATCH V5 5/5] soc: imx: sc: add misc " Dong Aisheng
2018-08-20 16:31 ` [PATCH V5 0/5] soc: imx: add scu firmware api support A.s. Dong
2018-08-24 7:36 ` A.s. Dong
2018-08-24 9:54 ` Jassi Brar
2018-08-24 11:02 ` A.s. Dong
2018-08-27 8:33 ` Sascha Hauer
2018-08-27 9:59 ` A.s. Dong
2018-08-27 10:21 ` A.s. Dong
2018-08-28 6:21 ` Sascha Hauer
2018-08-28 8:53 ` A.s. Dong
2018-08-29 6:53 ` Sascha Hauer
2018-08-29 8:35 ` A.s. Dong
2018-09-03 8:57 ` A.s. Dong
2018-09-03 11:44 ` Sascha Hauer
2018-09-06 3:21 ` A.s. Dong
2018-09-10 7:03 ` Sascha Hauer
2018-09-10 7:53 ` A.s. Dong
2018-08-28 6:15 ` Sascha Hauer [this message]
2018-08-28 9:02 ` A.s. Dong
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=20180828061509.ujjjigfjanprro5i@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).