The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: <Rengarajan.S@microchip.com>
To: <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v1 for-next] spi: mchp-pci1xxxx: Updated memcpy implementation for x64 and bcm2711 processors
Date: Wed, 19 Mar 2025 13:58:38 +0000	[thread overview]
Message-ID: <a322bf90b6b02f6dd96023e34d32eb78b1c23ca9.camel@microchip.com> (raw)
In-Reply-To: <188ffb7d-47e2-45fd-80b1-b31ca58f0c0b@sirena.org.uk>

Hi Mark,

Thanks for reviewing the patch and apologies for delayed response.

On Mon, 2025-02-24 at 14:30 +0000, Mark Brown wrote:
> [Some people who received this message don't often get email from
> broonie@kernel.org. Learn why this is important at 
> https://aka.ms/LearnAboutSenderIdentification ]
> 
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe

I went through several patches related to similar issues, and mostsuggest handling it on a SoC basis. The reasoning is that a system
may have an affected PCIe root complex while still having other
devices in the SoC that can, or even require, 64-bit accesses.

The following are some of the patches that I had looked into:
https://lore.kernel.org/lkml/20210226140305.26356-2-nsaenzjulienne@suse.de/T/#u

https://lore.kernel.org/linux-arm-kernel/c188698ca0de3ed6c56a0cf7880e1578aa753077.camel@suse.de/T/#u

Can you please suggest any alternate methods that we could use to
handle this in a more generic manner instead of making it Soc-specific.

Thanks,
Rengarajan S




  reply	other threads:[~2025-03-19 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 12:51 [PATCH v1 for-next] spi: mchp-pci1xxxx: Updated memcpy implementation for x64 and bcm2711 processors Rengarajan S
2025-02-24 14:30 ` Mark Brown
2025-03-19 13:58   ` Rengarajan.S [this message]
2025-03-19 14:33     ` Mark Brown
2025-02-27 14:00 ` kernel test robot
2025-02-27 19:50 ` kernel test robot

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=a322bf90b6b02f6dd96023e34d32eb78b1c23ca9.camel@microchip.com \
    --to=rengarajan.s@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.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