From: gnomes@lxorguk.ukuu.org.uk (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts
Date: Mon, 22 May 2017 19:26:36 +0100 [thread overview]
Message-ID: <20170522192636.5b578d89@alans-desktop> (raw)
In-Reply-To: <517d864d-d230-3abc-eb3c-4b628dc4625f@xilinx.com>
> We have in soc vendor tree similar patch but the reason is different.
>
> tty: serial: Added a CONFIG_SERIAL_XILINX_NR_UARTS option.
>
> This patch Adds CONFIG_SERIAL_XILINX_NR_UARTS option to allow
> the user to provide the Max number of uart ports information.
> If multiple cards (or) PL UARTS are present, the default limit
> of 2 ports should be increased.
>
> I haven't checked all drivers but in our case we have added this as
> quick fix for scenarios where you use serial aliases where alias is
> pointed to serial2 or more.
> In cdns_uart_init() cdns_uart_uart_driver is passed which contains .nr
> which is required to be passed.
>
> What's the best driver to look at dynamic allocation?
So there are quite a few that dynamically allocate the objects as they
are enumerated (eg max3100), but have a maximum set that is just pointers
(so for the max number of ports cheaper than the dynamic code)
The other question is why is it a CONFIG_ option. I'm assuming these
platforms are all ARM and in that case you could just pass the value in
the device tree, or hard code a safe maximum number of pointers to a
value which is the worst case and then install them as they are
enumerated.
There are lots of options better than breaking the "one kernel many
platforms" model.
Alan
next prev parent reply other threads:[~2017-05-22 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 2:21 [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts Sam Povilus
2017-05-20 16:20 ` Alan Cox
2017-05-22 7:02 ` Michal Simek
2017-05-22 18:26 ` Alan Cox [this message]
2017-05-23 11:44 ` Michal Simek
2017-05-23 20:07 ` Alan Cox
2017-05-24 13:06 ` Michal Simek
2017-05-24 13:31 ` Alan Cox
2017-05-24 16:09 ` Michal Simek
2017-05-25 9:27 ` Maarten Brock
2017-05-25 13:29 ` Alan Cox
2017-05-25 15:33 ` Michal Simek
2017-05-24 3:27 ` Sam Povilus
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=20170522192636.5b578d89@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.infradead.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