From: Pratyush Anand <pratyush.anand@st.com>
To: Arnd Bergmann <arnd@arndb.de>, Jingoo Han <jg1.han@samsung.com>
Cc: 'Kukjin Kim' <kgene.kim@samsung.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
'Grant Likely' <grant.likely@secretlab.ca>,
'Andrew Murray' <andrew.murray@arm.com>,
'Thomas Petazzoni' <thomas.petazzoni@free-electrons.com>,
'Thierry Reding' <thierry.reding@avionic-design.de>,
'Jason Gunthorpe' <jgunthorpe@obsidianresearch.com>,
'Surendranath Gurivireddy Balla' <suren.reddy@samsung.com>,
'Siva Reddy Kallam' <siva.kallam@samsung.com>,
'Thomas Abraham' <thomas.abraham@linaro.org>,
Mohit KUMAR <Mohit.KUMAR@st.com>
Subject: Re: [PATCH V4 1/3] pci: Add PCIe driver for Samsung Exynos
Date: Thu, 20 Jun 2013 15:28:56 +0530 [thread overview]
Message-ID: <51C2D260.6000303@st.com> (raw)
In-Reply-To: <28355406.ThqqvnG0Yj@wuerfel>
On 6/13/2013 7:48 PM, Arnd Bergmann wrote:
> On Thursday 13 June 2013 22:18:50 Jingoo Han wrote:
>> >On Wednesday, June 12, 2013 8:23 PM, Arnd Bergmann wrote:
>>> > >On Wednesday 12 June 2013 19:19:05 Jingoo Han wrote:
>>>> > > >+
>>>> > > >+/* synopsis specific PCIE configuration registers*/
>>>> > > >+#define PCIE_PORT_LINK_CONTROL 0x710
>>>> > > >+#define PORT_LINK_MODE_MASK (0x3f << 16)
>>>> > > >+#define PORT_LINK_MODE_4_LANES (0x7 << 16)
>>> > >
>>> > >Do you mean this is a "Synopsys" designware part? In that case it
>>> > >should really not be called "exynos-pcie" but "designware-pcie"
>>> > >and you should make sure that the driver makes no assumptions about
>>> > >the platform. A lot of other platforms also use designware
>>> > >parts and should be able to reuse this driver.
>> >
>> >Sorry, I don't think so.
>> >Only core block is a "Synopsys" designware part IP block,
>> >other parts are Exynos-specific.
>> >So, it is hard to share with other PCIe IPs using synopsis core.
> Just call it synopsys anyway and put a comment in to explain this.
> That should be enough for the next person with a synopsys PCI core
> to reuse your code and split out the exynos specific parts into a
> separate file.
>
I agree to Arnd that this patch should be split. I had worked in past
with SPEAr PCIe which also had designware PCIe IP. I see some code which
will fit both in SPEAr as well as in exynos. Unfortunately, I was not
able to get SPEAr driver pushed to mainline, as I moved to some other
project and got heavily occupied.
Last patch is here:
https://patchwork.kernel.org/patch/1661441/
Infact, these functions should be common to all arm platforms.
sys_to_pcie
cfg_read
cfg_write
Following functions should be common to all designware based driver (at
least they are same in SPEAr)
exynos_pcie_prog_viewport_cfg0
exynos_pcie_prog_viewport_cfg1
exynos_pcie_rd_other_conf
exynos_pcie_wr_other_conf
exynos_pcie_setup
exynos_pcie_valid_config
exynos_pcie_rd_conf
exynos_pcie_wd_conf
exynos_pcie_scan_bus
exynos_pcie_map_irq
add_pcie_port (after a bit of generalization)
exynos_pcie_probe
exynos_pcie_remove
Following should be specific to exynos:
exynos_pcie_rd_own_conf
exynos_pcie_wr_own_conf
exynos_pcie_link_up
exynos_pcie_setup_rc
exynos_pcie_assert_core_reset
exynos_pcie_deassert_core_reset
exynos_pcie_assert_phy_reset
exynos_pcie_deassert_phy_reset
exynos_pcie_init_phy
exynos_pcie_assert_reset
exynos_pcie_establish_link
exynos_pcie_host_init
struct pcie_port_info and struct pcie_port can also be standardized.
Regards
Pratyush
WARNING: multiple messages have this Message-ID (diff)
From: Pratyush Anand <pratyush.anand@st.com>
To: Arnd Bergmann <arnd@arndb.de>, Jingoo Han <jg1.han@samsung.com>
Cc: 'Thomas Petazzoni' <thomas.petazzoni@free-electrons.com>,
'Jason Gunthorpe' <jgunthorpe@obsidianresearch.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
'Siva Reddy Kallam' <siva.kallam@samsung.com>,
'Surendranath Gurivireddy Balla' <suren.reddy@samsung.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
'Thierry Reding' <thierry.reding@avionic-design.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
'Grant Likely' <grant.likely@secretlab.ca>,
'Kukjin Kim' <kgene.kim@samsung.com>,
'Thomas Abraham' <thomas.abraham@linaro.org>,
Mohit KUMAR <Mohit.KUMAR@st.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
'Andrew Murray' <andrew.murray@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V4 1/3] pci: Add PCIe driver for Samsung Exynos
Date: Thu, 20 Jun 2013 15:28:56 +0530 [thread overview]
Message-ID: <51C2D260.6000303@st.com> (raw)
In-Reply-To: <28355406.ThqqvnG0Yj@wuerfel>
On 6/13/2013 7:48 PM, Arnd Bergmann wrote:
> On Thursday 13 June 2013 22:18:50 Jingoo Han wrote:
>> >On Wednesday, June 12, 2013 8:23 PM, Arnd Bergmann wrote:
>>> > >On Wednesday 12 June 2013 19:19:05 Jingoo Han wrote:
>>>> > > >+
>>>> > > >+/* synopsis specific PCIE configuration registers*/
>>>> > > >+#define PCIE_PORT_LINK_CONTROL 0x710
>>>> > > >+#define PORT_LINK_MODE_MASK (0x3f << 16)
>>>> > > >+#define PORT_LINK_MODE_4_LANES (0x7 << 16)
>>> > >
>>> > >Do you mean this is a "Synopsys" designware part? In that case it
>>> > >should really not be called "exynos-pcie" but "designware-pcie"
>>> > >and you should make sure that the driver makes no assumptions about
>>> > >the platform. A lot of other platforms also use designware
>>> > >parts and should be able to reuse this driver.
>> >
>> >Sorry, I don't think so.
>> >Only core block is a "Synopsys" designware part IP block,
>> >other parts are Exynos-specific.
>> >So, it is hard to share with other PCIe IPs using synopsis core.
> Just call it synopsys anyway and put a comment in to explain this.
> That should be enough for the next person with a synopsys PCI core
> to reuse your code and split out the exynos specific parts into a
> separate file.
>
I agree to Arnd that this patch should be split. I had worked in past
with SPEAr PCIe which also had designware PCIe IP. I see some code which
will fit both in SPEAr as well as in exynos. Unfortunately, I was not
able to get SPEAr driver pushed to mainline, as I moved to some other
project and got heavily occupied.
Last patch is here:
https://patchwork.kernel.org/patch/1661441/
Infact, these functions should be common to all arm platforms.
sys_to_pcie
cfg_read
cfg_write
Following functions should be common to all designware based driver (at
least they are same in SPEAr)
exynos_pcie_prog_viewport_cfg0
exynos_pcie_prog_viewport_cfg1
exynos_pcie_rd_other_conf
exynos_pcie_wr_other_conf
exynos_pcie_setup
exynos_pcie_valid_config
exynos_pcie_rd_conf
exynos_pcie_wd_conf
exynos_pcie_scan_bus
exynos_pcie_map_irq
add_pcie_port (after a bit of generalization)
exynos_pcie_probe
exynos_pcie_remove
Following should be specific to exynos:
exynos_pcie_rd_own_conf
exynos_pcie_wr_own_conf
exynos_pcie_link_up
exynos_pcie_setup_rc
exynos_pcie_assert_core_reset
exynos_pcie_deassert_core_reset
exynos_pcie_assert_phy_reset
exynos_pcie_deassert_phy_reset
exynos_pcie_init_phy
exynos_pcie_assert_reset
exynos_pcie_establish_link
exynos_pcie_host_init
struct pcie_port_info and struct pcie_port can also be standardized.
Regards
Pratyush
WARNING: multiple messages have this Message-ID (diff)
From: pratyush.anand@st.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/3] pci: Add PCIe driver for Samsung Exynos
Date: Thu, 20 Jun 2013 15:28:56 +0530 [thread overview]
Message-ID: <51C2D260.6000303@st.com> (raw)
In-Reply-To: <28355406.ThqqvnG0Yj@wuerfel>
On 6/13/2013 7:48 PM, Arnd Bergmann wrote:
> On Thursday 13 June 2013 22:18:50 Jingoo Han wrote:
>> >On Wednesday, June 12, 2013 8:23 PM, Arnd Bergmann wrote:
>>> > >On Wednesday 12 June 2013 19:19:05 Jingoo Han wrote:
>>>> > > >+
>>>> > > >+/* synopsis specific PCIE configuration registers*/
>>>> > > >+#define PCIE_PORT_LINK_CONTROL 0x710
>>>> > > >+#define PORT_LINK_MODE_MASK (0x3f << 16)
>>>> > > >+#define PORT_LINK_MODE_4_LANES (0x7 << 16)
>>> > >
>>> > >Do you mean this is a "Synopsys" designware part? In that case it
>>> > >should really not be called "exynos-pcie" but "designware-pcie"
>>> > >and you should make sure that the driver makes no assumptions about
>>> > >the platform. A lot of other platforms also use designware
>>> > >parts and should be able to reuse this driver.
>> >
>> >Sorry, I don't think so.
>> >Only core block is a "Synopsys" designware part IP block,
>> >other parts are Exynos-specific.
>> >So, it is hard to share with other PCIe IPs using synopsis core.
> Just call it synopsys anyway and put a comment in to explain this.
> That should be enough for the next person with a synopsys PCI core
> to reuse your code and split out the exynos specific parts into a
> separate file.
>
I agree to Arnd that this patch should be split. I had worked in past
with SPEAr PCIe which also had designware PCIe IP. I see some code which
will fit both in SPEAr as well as in exynos. Unfortunately, I was not
able to get SPEAr driver pushed to mainline, as I moved to some other
project and got heavily occupied.
Last patch is here:
https://patchwork.kernel.org/patch/1661441/
Infact, these functions should be common to all arm platforms.
sys_to_pcie
cfg_read
cfg_write
Following functions should be common to all designware based driver (at
least they are same in SPEAr)
exynos_pcie_prog_viewport_cfg0
exynos_pcie_prog_viewport_cfg1
exynos_pcie_rd_other_conf
exynos_pcie_wr_other_conf
exynos_pcie_setup
exynos_pcie_valid_config
exynos_pcie_rd_conf
exynos_pcie_wd_conf
exynos_pcie_scan_bus
exynos_pcie_map_irq
add_pcie_port (after a bit of generalization)
exynos_pcie_probe
exynos_pcie_remove
Following should be specific to exynos:
exynos_pcie_rd_own_conf
exynos_pcie_wr_own_conf
exynos_pcie_link_up
exynos_pcie_setup_rc
exynos_pcie_assert_core_reset
exynos_pcie_deassert_core_reset
exynos_pcie_assert_phy_reset
exynos_pcie_deassert_phy_reset
exynos_pcie_init_phy
exynos_pcie_assert_reset
exynos_pcie_establish_link
exynos_pcie_host_init
struct pcie_port_info and struct pcie_port can also be standardized.
Regards
Pratyush
next prev parent reply other threads:[~2013-06-20 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 10:19 [PATCH V4 1/3] pci: Add PCIe driver for Samsung Exynos Jingoo Han
2013-06-12 10:19 ` Jingoo Han
2013-06-12 11:23 ` Arnd Bergmann
2013-06-12 11:23 ` Arnd Bergmann
2013-06-13 13:18 ` Jingoo Han
2013-06-13 13:18 ` Jingoo Han
2013-06-13 14:18 ` Arnd Bergmann
2013-06-13 14:18 ` Arnd Bergmann
2013-06-20 9:58 ` Pratyush Anand [this message]
2013-06-20 9:58 ` Pratyush Anand
2013-06-20 9:58 ` Pratyush Anand
2013-06-20 10:58 ` Jingoo Han
2013-06-20 10:58 ` Jingoo Han
2013-06-20 11:26 ` Pratyush Anand
2013-06-20 11:26 ` Pratyush Anand
2013-06-20 11:36 ` Jingoo Han
2013-06-20 11:36 ` Jingoo Han
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=51C2D260.6000303@st.com \
--to=pratyush.anand@st.com \
--cc=Mohit.KUMAR@st.com \
--cc=andrew.murray@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=siva.kallam@samsung.com \
--cc=suren.reddy@samsung.com \
--cc=thierry.reding@avionic-design.de \
--cc=thomas.abraham@linaro.org \
--cc=thomas.petazzoni@free-electrons.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.