From: Randy Dunlap <rdunlap@infradead.org>
To: min.li.xe@renesas.com, derek.kiernan@xilinx.com,
dragan.cvetic@xilinx.com, arnd@arndb.de,
gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH net-next v1] misc: Add Renesas Synchronization Management Unit (SMU) support
Date: Wed, 17 Mar 2021 11:03:55 -0700 [thread overview]
Message-ID: <5469b337-c210-617d-f88c-519e773f99b6@infradead.org> (raw)
In-Reply-To: <1616003094-1701-1-git-send-email-min.li.xe@renesas.com>
On 3/17/21 10:44 AM, min.li.xe@renesas.com wrote:
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index f532c59..1e2bc33 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -445,6 +445,16 @@ config HISI_HIKEY_USB
> switching between the dual-role USB-C port and the USB-A host ports
> using only one USB controller.
>
> +config RSMU
> + tristate "Renesas Synchronization Management Unit (SMU)"
> + depends on MFD_RSMU_I2C || MFD_RSMU_SPI
> + help
> + This option enables support for the IDT ClockMatrix(TM) and 82P33xxx
> + families of timing and synchronization devices.It will be used by
devices. It
> + Renesas PTP Clock Manager for Linux (pcm4l) software to provide support
> + for GNSS assisted partial timing support (APTS) and other networking
> + timing functions.
--
~Randy
next prev parent reply other threads:[~2021-03-17 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:44 [PATCH net-next v1] misc: Add Renesas Synchronization Management Unit (SMU) support min.li.xe
2021-03-17 18:03 ` Randy Dunlap [this message]
2021-03-17 19:14 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-03-17 18:59 min.li.xe
2021-03-17 19:19 ` Greg KH
2021-03-17 19:34 ` Min Li
2021-03-17 19:43 ` Greg KH
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=5469b337-c210-617d-f88c-519e773f99b6@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li.xe@renesas.com \
/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).