From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa@kernel.org
Cc: andriy.shevchenko@linux.intel.com, jarkko.nikula@linux.intel.com,
robh@kernel.org, semen.protsenko@linaro.org, sven@svenpeter.dev,
jsd@semihalf.com, rafal@milecki.pl, olof@lixom.net,
arnd@arndb.de, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH RFC i2c-master] i2c: microchip: pci1xxxx: Load I2C driver for I2C endpoint of pci1xxxx switch
Date: Mon, 26 Sep 2022 12:52:09 +0200 [thread overview]
Message-ID: <55f7b60c-85a2-5950-731a-1b578e27ae0d@kernel.org> (raw)
In-Reply-To: <20220926082642.2578447-1-tharunkumar.pasumarthi@microchip.com>
On 26/09/2022 10:26, Tharun Kumar P wrote:
> Microchip PCI1XXXX is an unmanaged PCIe3.1a Switch for Consumer,
> Industrial and Automotive applications. This switch has multiple
> downstream ports. In one of the Switch's Downstream port, there
> is a peripheral endpoint which supports I2C functionality. The I2C
> function in the endpoint operates at 100KHz, 400KHz and 1 MHz and
> has buffer depth of 128 bytes.
> This series of patches provides the I2C controller driver for the
> I2C endpoint of the switch.
>
> Signed-off-by: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
> ---
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. Do not Cc unrelated people.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-26 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:26 [PATCH RFC i2c-master] i2c: microchip: pci1xxxx: Load I2C driver for I2C endpoint of pci1xxxx switch Tharun Kumar P
2022-09-26 8:42 ` Tharunkumar.Pasumarthi
2022-09-26 10:52 ` Krzysztof Kozlowski [this message]
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=55f7b60c-85a2-5950-731a-1b578e27ae0d@kernel.org \
--to=krzk@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sven@svenpeter.dev \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=wsa@kernel.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