public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Raviteja Narayanam <rna@xilinx.com>
Cc: "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"jslaby@suse.com" <jslaby@suse.com>,
	Michal Simek <michals@xilinx.com>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	git <git@xilinx.com>
Subject: Re: Need suggestion for 'access_type' of AMBA pl011 serial driver
Date: Thu, 3 Jun 2021 09:13:38 +0200	[thread overview]
Message-ID: <YLiBIvkMVKA96Q5g@kroah.com> (raw)
In-Reply-To: <SN6PR02MB40936F8F2879AD5CFDFC80D2CA3C9@SN6PR02MB4093.namprd02.prod.outlook.com>

On Thu, Jun 03, 2021 at 07:03:25AM +0000, Raviteja Narayanam wrote:
> Hi,
> 
> The uart peripheral on Xilinx Versal platform is ARM primecell.
> Our environment is 32-bit access type but the ARM primecell uart in pl011 driver has default 16 bit access type. 
> (https://github.com/torvalds/linux/blob/master/drivers/tty/serial/amba-pl011.c#L2665 access_32b is false for 'vendor_arm')
> This is causing asynchronous abort on our platform when any UART register is written from the pl011 driver.
> 
> Need suggestion on how we can address this issue and if the below approach is fine.
> 
> As this is platform specific issue, we can have a new device tree property (memory_access_type), specifying the 32 bit type.
> In the probe function, override the behavior (uap->port.iotype) if this property is present in DT.
> In this way, we can have support for our SOC, without breaking any legacy ones.

There is no other way to determine what this device is other than
platform data?  Why not just set the vendor id in your device to a new
one and provide a correct setting in that new vendor data structure,
like all other devices for this chip have done before?

If it is the same id, and works differently, then that is a hardware
issue that you need to take up with your hardware designers to get fixed
as that is obviously a problem.

thanks,

greg k-h

  reply	other threads:[~2021-06-03  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  7:03 Need suggestion for 'access_type' of AMBA pl011 serial driver Raviteja Narayanam
2021-06-03  7:13 ` gregkh [this message]
2021-06-03  8:59 ` Vladimir Zapolskiy

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=YLiBIvkMVKA96Q5g@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=git@xilinx.com \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michals@xilinx.com \
    --cc=rna@xilinx.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