All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <frank.li@nxp.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "M.H. Lian" <minghuan.lian@nxp.com>,
	"Mingkai Hu" <mingkai.hu@nxp.com>, "Roy Zang" <roy.zang@nxp.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linuxppc-dev@lists.ozlabs.org>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-pci@vger.kernel.org>,
	"moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: RE: [EXT] Re: [PATCH 1/1] PCI: layerscape: Add the workaround for A-010305
Date: Fri, 17 Mar 2023 15:58:13 +0000	[thread overview]
Message-ID: <AM6PR04MB4838BBCA8E49EE13C9545F4388BD9@AM6PR04MB4838.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20230314203249.GA1673140@bhelgaas>

> >       pci->ep.ops = &ls_pcie_ep_ops;
> >
> > +     pcie->big_endian = of_property_read_bool(dev->of_node, "big-
> endian");
> 
> Somewhat surprising that 6c389328c985 ("dt-bindings: pci:
> layerscape-pci: Add a optional property big-endian") added this
> property a year ago, but it has been unused until now?
> 

No, it also for pci host part. Zhiqiang send patch 
https://lore.kernel.org/lkml/20210407030948.3845-1-Zhiqiang.Hou@nxp.com/

Not sure why bind-doc accepted, but driver code patch have not accepted. 

The same case happen at https://lore.kernel.org/imx/20230209151050.233973-1-Frank.Li@nxp.com/T/#t

I tried repost the missed part. But no any response over months.  The above one is just one line change. 

> > --
> > 2.34.1
> >

WARNING: multiple messages have this Message-ID (diff)
From: Frank Li <frank.li@nxp.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"Rob Herring" <robh@kernel.org>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-pci@vger.kernel.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"M.H. Lian" <minghuan.lian@nxp.com>,
	"moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-arm-kernel@lists.infradead.org>,
	"Roy Zang" <roy.zang@nxp.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linuxppc-dev@lists.ozlabs.org>,
	"Mingkai Hu" <mingkai.hu@nxp.com>
Subject: RE: [EXT] Re: [PATCH 1/1] PCI: layerscape: Add the workaround for A-010305
Date: Fri, 17 Mar 2023 15:58:13 +0000	[thread overview]
Message-ID: <AM6PR04MB4838BBCA8E49EE13C9545F4388BD9@AM6PR04MB4838.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20230314203249.GA1673140@bhelgaas>

> >       pci->ep.ops = &ls_pcie_ep_ops;
> >
> > +     pcie->big_endian = of_property_read_bool(dev->of_node, "big-
> endian");
> 
> Somewhat surprising that 6c389328c985 ("dt-bindings: pci:
> layerscape-pci: Add a optional property big-endian") added this
> property a year ago, but it has been unused until now?
> 

No, it also for pci host part. Zhiqiang send patch 
https://lore.kernel.org/lkml/20210407030948.3845-1-Zhiqiang.Hou@nxp.com/

Not sure why bind-doc accepted, but driver code patch have not accepted. 

The same case happen at https://lore.kernel.org/imx/20230209151050.233973-1-Frank.Li@nxp.com/T/#t

I tried repost the missed part. But no any response over months.  The above one is just one line change. 

> > --
> > 2.34.1
> >

WARNING: multiple messages have this Message-ID (diff)
From: Frank Li <frank.li@nxp.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "M.H. Lian" <minghuan.lian@nxp.com>,
	"Mingkai Hu" <mingkai.hu@nxp.com>, "Roy Zang" <roy.zang@nxp.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linuxppc-dev@lists.ozlabs.org>,
	"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-pci@vger.kernel.org>,
	"moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: RE: [EXT] Re: [PATCH 1/1] PCI: layerscape: Add the workaround for A-010305
Date: Fri, 17 Mar 2023 15:58:13 +0000	[thread overview]
Message-ID: <AM6PR04MB4838BBCA8E49EE13C9545F4388BD9@AM6PR04MB4838.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20230314203249.GA1673140@bhelgaas>

> >       pci->ep.ops = &ls_pcie_ep_ops;
> >
> > +     pcie->big_endian = of_property_read_bool(dev->of_node, "big-
> endian");
> 
> Somewhat surprising that 6c389328c985 ("dt-bindings: pci:
> layerscape-pci: Add a optional property big-endian") added this
> property a year ago, but it has been unused until now?
> 

No, it also for pci host part. Zhiqiang send patch 
https://lore.kernel.org/lkml/20210407030948.3845-1-Zhiqiang.Hou@nxp.com/

Not sure why bind-doc accepted, but driver code patch have not accepted. 

The same case happen at https://lore.kernel.org/imx/20230209151050.233973-1-Frank.Li@nxp.com/T/#t

I tried repost the missed part. But no any response over months.  The above one is just one line change. 

> > --
> > 2.34.1
> >

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-03-17 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:44 [PATCH 1/1] PCI: layerscape: Add the workaround for A-010305 Frank Li
2023-01-12 19:44 ` Frank Li
2023-02-02 17:43 ` Frank Li
2023-02-02 17:43   ` Frank Li
2023-02-14 17:33   ` Frank Li
2023-02-14 17:33     ` Frank Li
2023-03-14 19:57     ` Frank Li
2023-03-14 19:57       ` Frank Li
2023-03-14 20:32 ` Bjorn Helgaas
2023-03-14 20:32   ` Bjorn Helgaas
2023-03-14 20:32   ` Bjorn Helgaas
2023-03-17 15:58   ` Frank Li [this message]
2023-03-17 15:58     ` [EXT] " Frank Li
2023-03-17 15:58     ` Frank Li

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=AM6PR04MB4838BBCA8E49EE13C9545F4388BD9@AM6PR04MB4838.eurprd04.prod.outlook.com \
    --to=frank.li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lpieralisi@kernel.org \
    --cc=minghuan.lian@nxp.com \
    --cc=mingkai.hu@nxp.com \
    --cc=robh@kernel.org \
    --cc=roy.zang@nxp.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.