linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Manikanta Guntupalli <manikanta.guntupalli@amd.com>,
	git@amd.com, michal.simek@amd.com, jacmet@sunsite.dk,
	gregkh@linuxfoundation.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	christophe.leroy@csgroup.eu, rdunlap@infradead.org,
	airlied@redhat.com, ogabbay@kernel.org,
	linux-doc@vger.kernel.org
Cc: radhey.shyam.pandey@amd.com, srinivas.goud@amd.com,
	shubhrajyoti.datta@amd.com, manion05gk@gmail.com
Subject: Re: [PATCH V2 1/2] Documentation: devices.txt: Update ttyUL major number allocation details
Date: Tue, 14 Nov 2023 10:49:02 +0100	[thread overview]
Message-ID: <1fbb7691-398c-4b69-abdd-b57606085cd1@kernel.org> (raw)
In-Reply-To: <20231114093303.2718141-2-manikanta.guntupalli@amd.com>

On 14. 11. 23, 10:33, Manikanta Guntupalli wrote:
> Describe when uartlite driver uses static/dynamic allocation for major
> number based on maximum number of uartlite serial ports.
> 
> Signed-off-by: Manikanta Guntupalli <manikanta.guntupalli@amd.com>
> ---
> Changes for V2:
> This patch introduced in V2.
> ---
>   Documentation/admin-guide/devices.txt | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/admin-guide/devices.txt b/Documentation/admin-guide/devices.txt
> index 839054923530..d2f2c9f436db 100644
> --- a/Documentation/admin-guide/devices.txt
> +++ b/Documentation/admin-guide/devices.txt
> @@ -2707,6 +2707,10 @@
>   		 187 = /dev/ttyUL0		Xilinx uartlite - port 0
>   		    ...
>   		 190 = /dev/ttyUL3		Xilinx uartlite - port 3
> +
> +		 If maximum number of uartlite serial ports more than 4, then driver uses
> +		 dynamic allocation instead of static allocation for major number.

I am not sure about the placement of this comment. This looks like it 
holds for xvc below.

>   		 191 = /dev/xvc0		Xen virtual console - port 0
>   		 192 = /dev/ttyPZ0		pmac_zilog - port 0
>   		    ...

-- 
js
suse labs


  reply	other threads:[~2023-11-14  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:33 [PATCH V2 0/2] Use dynamic allocation for major number when uart ports > 4 Manikanta Guntupalli
2023-11-14  9:33 ` [PATCH V2 1/2] Documentation: devices.txt: Update ttyUL major number allocation details Manikanta Guntupalli
2023-11-14  9:49   ` Jiri Slaby [this message]
2023-11-14  9:33 ` [PATCH V2 2/2] serial: uartlite: Use dynamic allocation for major number when uart ports > 4 Manikanta Guntupalli
2023-11-14  9:48   ` Jiri Slaby

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=1fbb7691-398c-4b69-abdd-b57606085cd1@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=airlied@redhat.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=corbet@lwn.net \
    --cc=git@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacmet@sunsite.dk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=manikanta.guntupalli@amd.com \
    --cc=manion05gk@gmail.com \
    --cc=michal.simek@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=rdunlap@infradead.org \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=srinivas.goud@amd.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).