From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rahul Tanwar <rtanwar@maxlinear.com>
Cc: "bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"robh@kernel.org" <robh@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-lgm-soc <linux-lgm-soc@maxlinear.com>
Subject: Re: [PATCH RESEND 1/1] x86/of: Add support for boot time interrupt mode config
Date: Mon, 14 Nov 2022 12:24:16 +0200 [thread overview]
Message-ID: <Y3IXUN5ETBfrSXRW@smile.fi.intel.com> (raw)
In-Reply-To: <00ce811f-2ec8-802d-d032-8ac2c65d06ff@maxlinear.com>
On Mon, Nov 14, 2022 at 10:00:02AM +0000, Rahul Tanwar wrote:
> On 14/11/2022 5:45 pm, Andy Shevchenko wrote:
> > On Mon, Nov 14, 2022 at 05:20:06PM +0800, Rahul Tanwar wrote:
...
> >> + if (of_property_read_bool(dn, "intel,no-imcr")) {
> >
> > I can't find this property in the Documentation/devicetree/bindings.
> >
> > Moreover, I prefer to see positive one, something like:
> >
> > intel,virtual-wire-bla-bla-bla
> >
> > Please consult with DT people on how properly name it.
>
>
> Yes, agree. Need to add it in bindings doc after finalizing the property
> name. I chose "intel,no-imcr" to have a direct correlation with the MPS
> spec defined data field for the same purpose.
The problems with it are:
- it's negative
- it's too cryptic to one who doesn't know area well enough
> It reads below bit in
> mpparse code to detect PIC mode or virtual wire mode.
>
> Bit 7: IMCRP. When the IMCR presence bit is set, the IMCR is present and
> PIC Mode is implemented; otherwise, Virtual Wire Mode is implemented.
>
> Please refer [1]
>
> [1] https://www.manualslib.com/manual/77733/Intel
> Multiprocessor.html?page=40#manual
This is good reference for DT people to suggest you a better name.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-14 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:20 [PATCH RESEND 0/1] x86/of: Fix a bug in x86 arch OF support Rahul Tanwar
2022-11-14 9:20 ` [PATCH RESEND 1/1] x86/of: Add support for boot time interrupt mode config Rahul Tanwar
2022-11-14 9:44 ` Andy Shevchenko
2022-11-14 10:00 ` Rahul Tanwar
2022-11-14 10:24 ` Andy Shevchenko [this message]
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=Y3IXUN5ETBfrSXRW@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lgm-soc@maxlinear.com \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=rtanwar@maxlinear.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.