From: Mark Brown <broonie@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Kuldip Dwivedi <kuldip.dwivedi@puresoftware.com>,
Qiang Zhao <qiang.zhao@nxp.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Pankaj Bansal <pankaj.bansal@nxp.com>,
Varun Sethi <V.Sethi@nxp.com>,
Tanveer Alam <tanveer.alam@puresoftware.com>
Subject: Re: [PATCH] spi: spi-fsl-dspi: Add ACPI support
Date: Wed, 26 Aug 2020 19:36:03 +0100 [thread overview]
Message-ID: <20200826183603.GP4965@sirena.org.uk> (raw)
In-Reply-To: <20200826183044.4g6jvfrgkhpxki3k@skbuf>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On Wed, Aug 26, 2020 at 09:30:44PM +0300, Vladimir Oltean wrote:
> On Wed, Aug 26, 2020 at 06:02:05PM +0100, Mark Brown wrote:
> > That's not something that it's particularly idiomatic to actually use in
> > ACPI and you end up with the same namespacing problem assigning IDs so
> > I'm not sure it makes life any better.
> So what's the idiomatic thing to do in this case, allocate the first
> free PNP ID now for DSPI controller on LS2085A, then another one for
> DSPI on LX2160A later, etc etc?
AFAICT yes, assuming you don't make it look like a PCI device and
enumerate that way which is more how these things more normally end up
getting done.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-26 18:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 13:10 [PATCH] spi: spi-fsl-dspi: Add ACPI support kuldip dwivedi
2020-08-21 14:07 ` Mark Brown
2020-08-22 14:07 ` Kuldip Dwivedi
2020-08-22 15:21 ` Vladimir Oltean
2020-08-24 11:25 ` Mark Brown
2020-08-26 8:19 ` Qiang Zhao
2020-08-26 10:19 ` Mark Brown
2020-08-26 11:10 ` Qiang Zhao
2020-08-26 11:47 ` Vladimir Oltean
2020-08-26 14:23 ` Mark Brown
2020-08-26 14:47 ` Vladimir Oltean
2020-08-26 15:13 ` Kuldip Dwivedi
2020-08-26 16:09 ` Vladimir Oltean
2020-08-26 17:02 ` Mark Brown
2020-08-26 18:30 ` Vladimir Oltean
2020-08-26 18:36 ` Mark Brown [this message]
2020-08-26 16:55 ` Mark Brown
2020-08-26 18:33 ` Vladimir Oltean
2020-08-26 18:42 ` Mark Brown
2020-08-21 16:49 ` kernel test robot
2020-08-21 16:49 ` kernel test robot
2020-08-22 18:33 ` Vladimir Oltean
2020-08-26 19:34 ` Andy Shevchenko
2020-08-26 19:36 ` Andy Shevchenko
2020-08-26 19:56 ` Vladimir Oltean
2020-08-26 20:41 ` Mark Brown
2020-08-26 20:41 ` Vladimir Oltean
2020-08-26 20:45 ` Mark Brown
2020-08-26 21:06 ` Vladimir Oltean
2020-08-27 11:32 ` Mark Brown
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=20200826183603.GP4965@sirena.org.uk \
--to=broonie@kernel.org \
--cc=V.Sethi@nxp.com \
--cc=kuldip.dwivedi@puresoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pankaj.bansal@nxp.com \
--cc=qiang.zhao@nxp.com \
--cc=tanveer.alam@puresoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.